Re: About some problem

From	Ned Batchelder <ned@nedbatchelder.com>
Subject	Re: About some problem
Date	2014-01-02 12:36 -0500
References	<CAN5p5FV7=RKK0cmE_=n+te07CEt678OX1Wwj+96T9eAuDujpfA@mail.gmail.com> <CAPM-O+wAZFmde2bVhqqs4==a-jy3AXfv3f9JNQwcNmTJHCak+Q@mail.gmail.com> <CAJ+Teoc0f3S2FRPwrtHuao+7aKiA=57Nn1UVpoH0-3WRTNQbgg@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.4798.1388684233.18130.python-list@python.org> (permalink)

Show all headers | View raw

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 comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: About some problem Ned Batchelder <ned@nedbatchelder.com> - 2014-01-02 12:36 -0500

csiph-web