Potential Python 3.3.2 pyvenv bug on Windows

[peter]

I've recently hit an issue with pyvenv that is causing AttributeErrors in other packages on Windows (see https://groups.google.com/forum/?fromgroups#!topic/pylons-discuss/FpOSMDpdvy4). Here's what I believe is going on:

On Windows, the pyvenv pydoc script has a .py extension - so import finds it instead of the system's pydoc module. On Linux, the pyvenv pydoc script doesn't have an extension - so import finds the system's pydoc module.

I believe the Windows pyvenv pydoc.py script should be renamed to pydocs.py.

Has anyone else hit this issue?

Peter

 

[Fábio Santos]

I've recently hit an issue with pyvenv that is causing AttributeErrors inother packages on Windows (see https://groups.google.com/forum/?fromgroups#!topic/pylons-discuss/FpOSMDpdvy4). Here's what I believe is going on:

On Windows, the pyvenv pydoc script has a .py extension - so import findsit instead of the system's pydoc module. On Linux, the pyvenv pydoc script doesn't have an extension - so import finds the system's pydoc module.

I believe the Windows pyvenv pydoc.py script should be renamed to pydocs.py.

Has anyone else hit this issue?

Peter

Don't think that's so good of a fix. Following documentation for
open-source software is already hard enough on windows, people will
not be able to use pydoc.py because it was renamed.

It would be slightly better to use pydoc.bat (which could then call
pydocs.py), but even so it would be pretty bad.

 

[peter]

Agreed. I did submit a bug report. If the core developers fix this, I suspect they will do so in a manner that does not break existing docs. However, my workaround (rename the pyvenv created scripts\pydoc.py file) should suffice for those who need the problem solved now.

Take care,

Peter