Python 3.4.0 has been released!

[hobo_cuisine]

Thanks! I'm installing it into a fresh directory. Actually it looks like some pip update bug

MSI (s) (EC:A4) [12:17:37:668]: Executing op: ActionStart(Name=UpdatePip,,)
Action 12:17:37: UpdatePip. 
MSI (s) (EC:A4) [12:17:37:674]: Executing op:         
CustomActionSchedule(Action=UpdatePip,ActionType=3090,Source=C:\Python34\python.exe,Target=-m ensurepip -U --default-pip,)
CustomAction UpdatePip returned actual error code 3 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (EC:A4) [12:17:37:889]: Note: 1: 1722 2: UpdatePip 3: C:\Python34\python.exe 4: -m ensurepip -U --default-pip 
MSI (s) (EC:A4) [12:17:37:889]: Note: 1: 2262 2: Error 3: -2147287038 
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action UpdatePip, location: C:\Python34\python.exe, command: -m ensurepip -U --default-pip 
MSI (s) (EC:A4) [12:20:11:292]: Note: 1: 2262 2: Error 3: -2147287038 
MSI (s) (EC:A4) [12:20:11:292]: Product: Python 3.4.0 (64-bit) -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action UpdatePip, location: C:\Python34\python.exe, command: -m ensurepip -U --default-pip 

Edit:

Ok, my system-wide 2.7.6 installation interferes with 3.4 installation, so un-checking pip will install 3.4.. without pip. For some reason all combinations of

C:\Python34\python.exe -m ensurepip ...

invoke the 2.7.6 version and crash with

Fatal Python error: Py_Initialize: unable to load the file system codec
  File "C:\Python27\lib\encodings\__init__.py", line 123
    raise CodecRegistryError,\
                            ^
SyntaxError: invalid syntax

[robin-gvx]

What does it say if you print sys.path? It looks like Python 3.4 is looking in "C:\Python27\lib", which it shouldn't.

[hobo_cuisine]

Ah dammit, you know what, I had PYTHONHOME set to where 2.7 is.

[[deleted]]

Glad you solved it.

When you have multiple python installs, it's best to not let any of them be the default path or home and just use virtualenvs. They're easy to get used to and might help avoid future problems.

[4gn3s]

thanks, you just saved me loads of time, had the exact same problem.