On Sat, Jun 15, 2013 at 3:17 PM, <pe...@psantoro.net> wrote: > 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 > -- > http://mail.python.org/mailman/listinfo/python-list
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. -- Fábio Santos -- http://mail.python.org/mailman/listinfo/python-list
