Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #48299 > unrolled thread
| Started by | peter@psantoro.net |
|---|---|
| First post | 2013-06-15 07:17 -0700 |
| Last post | 2013-06-15 10:08 -0700 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.lang.python
Potential Python 3.3.2 pyvenv bug on Windows peter@psantoro.net - 2013-06-15 07:17 -0700
Re: Potential Python 3.3.2 pyvenv bug on Windows Fábio Santos <fabiosantosart@gmail.com> - 2013-06-15 15:32 +0100
Re: Potential Python 3.3.2 pyvenv bug on Windows peter@psantoro.net - 2013-06-15 10:08 -0700
| From | peter@psantoro.net |
|---|---|
| Date | 2013-06-15 07:17 -0700 |
| Subject | Potential Python 3.3.2 pyvenv bug on Windows |
| Message-ID | <28b472c8-969c-4f32-82e9-5772656ffe5b@googlegroups.com> |
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
[toc] | [next] | [standalone]
| From | Fábio Santos <fabiosantosart@gmail.com> |
|---|---|
| Date | 2013-06-15 15:32 +0100 |
| Message-ID | <mailman.3378.1371306779.3114.python-list@python.org> |
| In reply to | #48299 |
On Sat, Jun 15, 2013 at 3:17 PM, <peter@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
[toc] | [prev] | [next] | [standalone]
| From | peter@psantoro.net |
|---|---|
| Date | 2013-06-15 10:08 -0700 |
| Message-ID | <7546931c-ebd5-43f3-8fd1-cb2e10b7fde1@googlegroups.com> |
| In reply to | #48302 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web