[pydotorg-www] Python 3.4 many problems, no ability to register and report bugs

[Thomas Wouters]

On Thu, Apr 24, 2014 at 2:39 PM, Bill Bergmann <wfbergmann at gmail.com> wrote:

> Along with doing my own work in python I lead a couple user groups in
> python in Albuquerque, NM. After some perl programmers in one group asked
> me about whether python 3 is proving to be perl 6, I decided to take on a
> serious project with python 3.4 to find out for myself. I have discovered
> many problems and few documented solutions or workarounds for the problems
> I am finding.
>
> Along the way, I have found the installation of python 3.4 to have created
> various problems with python 2.7. For example: bcrypt is currently
> inoperable within python 2.7 despite several attempted workarounds. Yes, I
> am familiar with virtualenv, but the problem seems to be beyond the ability
> of virtualenv to insulate it.
>
> I decided to do my part and file some bug reports. I am not able to
> register at the python bug tracker. I'm not too naive a programmer. I've
> programmed in python over ten years, and I am concerned. These problems
> have not been characteristic of my experiences with python, and the current
> state of disarray makes advocating for python problematic. If I am
> experiencing these problems, I think it safe to say that there are many
> others. Programmers from other programming languages will meet these
> problems and simply walk away from python.
>
>
How did you try to register on bugs.python.org? How did it fail?



> What is going on? Any suggestions?
>
> Bill Bergmann
>
>
> The example code from the Python Standard Library 17.4.2.1 run on python
> 3.4:
>
> $ python3 17_4_2.py
> Traceback (most recent call last):
>   File "<frozen importlib._bootstrap>", line 2195, in
> _find_and_load_unlocked
> AttributeError: 'module' object has no attribute '__path__'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "17_4_2.py", line 1, in <module>
>     import concurrent.futures
> ImportError: No module named 'concurrent.futures'; 'concurrent' is not a
> package
>
>
> I am running this on OS X 10.6:
> $env
>
> PATH=/Library/Frameworks/Python.framework/Versions/3.4/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:
> ...
>
>
> PYTHONPATH=/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/:/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/:/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/:/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/:
>

Don't set PYTHONPATH. Certainly don't set it to the site-packages
directories of different Python versions. Don't set it to the empty string
(the last item) either, as that will mean 'the current working directory'.
I suspect your problems will be solved if you unset this.


>
> _______________________________________________
> pydotorg-www mailing list
> pydotorg-www at python.org
> https://mail.python.org/mailman/listinfo/pydotorg-www
>



-- 
Thomas Wouters <thomas at python.org>

Hi! I'm an email virus! Think twice before sending your email to help me
spread!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pydotorg-www/attachments/20140424/27e737da/attachment.html>