Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #62989 > unrolled thread
| Started by | Ned Batchelder <ned@nedbatchelder.com> |
|---|---|
| First post | 2014-01-02 12:36 -0500 |
| Last post | 2014-01-02 12:36 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: About some problem Ned Batchelder <ned@nedbatchelder.com> - 2014-01-02 12:36 -0500
| From | Ned Batchelder <ned@nedbatchelder.com> |
|---|---|
| Date | 2014-01-02 12:36 -0500 |
| Subject | Re: About some problem |
| Message-ID | <mailman.4798.1388684233.18130.python-list@python.org> |
On 1/2/14 12:05 PM, Rustom Mody wrote: > > i'm not sure about this but isnt it normally the case that different > version modules dont get mixed up like that? > IOW if pytesser was a properly packaged 2.7 module would python 3 be > able to get at it ?? > If you use a Python 3 installer it can succeed at installing a Python 2 package. Then you won't find out until you try to run the package that it is incompatible. A mechanism to prevent this seems like a good idea, but since it wasn't in place at the dawn of Python 3, it would be difficult to put in place now. -- Ned Batchelder, http://nedbatchelder.com
Back to top | Article view | comp.lang.python
csiph-web