Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!goblin1!goblin.stu.neva.ru!uio.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'that?': 0.05; 'paths': 0.07; 'python3': 0.07; 'sys': 0.07; 'think,': 0.07; 'mixed': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; 'jan': 0.12; 'assume': 0.14; '2.7': 0.14; '>>': 0.16; '__future__': 0.16; 'args,': 0.16; 'args.': 0.16; 'isnt': 0.16; 'sys.path': 0.16; 'wrongly': 0.16; 'prevent': 0.16; 'wrote:': 0.18; 'module': 0.19; 'mechanism': 0.19; 'normally': 0.19; 'properly': 0.19; "python's": 0.19; "skip:' 30": 0.19; 'thu,': 0.19; 'seems': 0.21; '>>>': 0.22; 'import': 0.22; 'email addr:gmail.com>': 0.22; 'cc:addr:python.org': 0.22; 'install': 0.23; '>>>': 0.24; 'package.': 0.24; 'recognize': 0.24; 'subject:problem': 0.24; "haven't": 0.24; 'looks': 0.24; 'cc:2**0': 0.24; '>': 0.26; 'second': 0.26; 'header:In-Reply-To:1': 0.27; 'dec': 0.30; 'message-id:@mail.gmail.com': 0.30; "i'm": 0.30; 'url:mailman': 0.30; '(on': 0.31; 'dawn': 0.31; 'idea,': 0.31; 'seemingly': 0.31; "skip:' 40": 0.31; 'subject:About': 0.31; 'subject:some': 0.31; 'run': 0.32; 'linux': 0.33; 'url:python': 0.33; 'but': 0.35; 'received:google.com': 0.35; 'version': 0.36; 'installing': 0.36; 'url:listinfo': 0.36; 'url:org': 0.36; 'list': 0.37; 'being': 0.38; 'skip:& 10': 0.38; 'pm,': 0.38; 'skip:& 20': 0.39; 'sure': 0.39; 'url:mail': 0.40; 'full': 0.61; 'first': 0.61; 'more': 0.64; 'different': 0.65; 'to:addr:gmail.com': 0.65; 'dont': 0.67; '2-3': 0.68; 'system)': 0.69; 'apart': 0.72; 'batchelder': 0.84; 'installer': 0.84; 'malicious': 0.84; 'saying:': 0.84; '2013,': 0.91; '<>*': 0.95 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TFJj3wscvE9SOX7763/9N9d223KpCWIpVxGB5QdiGVU=; b=ztj6cs45tCF8t2Kxxq1gqzl9kV1Ve0KqCFOdPliNzPibofBVHhejj1RE0XDSTYmUzu 6/1cJyDRliYBR2QVneNv2jrz1/B5pQW5ixGvJrXJFD1oLVX+0hHlRK2MWC+z+d3oJF9s Eaw/nZWu22dWoaMNSeJitT6DK4I9yPuSQxn1JRlk5pskraM2KSi3jtfti1LumQHVZfmb rhPRCLQeUghtFwVK1O2B2lba5XpcGDkptQbczchhWLtiKeswy9FNB+GrXw3aNHGZH+pK mHKj9lAhV6YFdi4xKkfqcLrJUn0DziZGdZ6n+fUFOqGUv060dU7QMSDvLszyMNSGVL6j iynw== MIME-Version: 1.0 X-Received: by 10.49.71.34 with SMTP id r2mr144896542qeu.69.1388686809635; Thu, 02 Jan 2014 10:20:09 -0800 (PST) In-Reply-To: References: Date: Thu, 2 Jan 2014 13:20:09 -0500 Subject: Re: About some problem From: David Hutto To: Rustom Mody Content-Type: multipart/alternative; boundary=047d7b5d5a42fe1e9f04ef00d7f6 Cc: python-list X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 209 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1388686817 news.xs4all.nl 2886 [2001:888:2000:d::a6]:59698 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:62993 --047d7b5d5a42fe1e9f04ef00d7f6 Content-Type: text/plain; charset=ISO-8859-1 Looks like you have a a list of 2.7 dependencies in the path args. The first you seem to have 3.3 args, and the second a longer list of 2.7 args....I would assume the second is the full list...correct? On Thu, Jan 2, 2014 at 1:07 PM, David Hutto wrote: > I think, but haven't tried, and this would be 2-3 from __future__ import > > > On Thu, Jan 2, 2014 at 12:46 PM, Rustom Mody wrote: > >> On Thu, Jan 2, 2014 at 11:06 PM, Ned Batchelder >> wrote: >> > 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. >> >> $ python3 >> Python 3.3.3 (default, Dec 8 2013, 16:34:29) >> [GCC 4.8.2] on linux >> Type "help", "copyright", "credits" or "license" for more information. >> >>> from sys import path >> >>> path >> ['', '/usr/lib/python3.3', '/usr/lib/python3.3/plat-i386-linux-gnu', >> '/usr/lib/python3.3/lib-dynload', >> '/usr/local/lib/python3.3/dist-packages', >> '/usr/lib/python3/dist-packages'] >> >> >> $ python >> Python 2.7.6 (default, Dec 6 2013, 21:56:56) >> [GCC 4.8.2] on linux2 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> from sys import path >> >>> path >> ['', '/usr/local/lib/python2.7/dist-packages/pip-1.0-py2.7.egg', >> '/usr/lib/python2.7', '/usr/lib/python2.7/plat-i386-linux-gnu', >> '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', >> '/usr/lib/python2.7/lib-dynload', >> '/usr/local/lib/python2.7/dist-packages', >> '/usr/lib/python2.7/dist-packages', >> '/usr/lib/python2.7/dist-packages/PILcompat', >> '/usr/lib/python2.7/dist-packages/gst-0.10', >> '/usr/lib/python2.7/dist-packages/gtk-2.0', >> '/usr/lib/pymodules/python2.7', >> '/usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode'] >> >> >> So as far as I can see (on a debian linux system) the paths are >> clearly 2.7-prefixed or 3.3-prefixed. >> >> So apart from being stupid and/or malicious to munge sys.path to tread >> on the other python's toes...??? >> >> Oh ok I get what you are saying: python3 will not recognize a python2 >> package and install it seemingly correctly but actually wrongly >> -- >> https://mail.python.org/mailman/listinfo/python-list >> > > > > -- > Best Regards, > David Hutto > *CEO:* *http://www.hitwebdevelopment.com > * > -- Best Regards, David Hutto *CEO:* *http://www.hitwebdevelopment.com * --047d7b5d5a42fe1e9f04ef00d7f6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Looks like you have a a list of 2.7 dependencies= in the path
=A0args.

The first you seem to have 3.3 = args, and the second a longer list of 2.7 args....I would assume the second= is the full list...correct?



On = Thu, Jan 2, 2014 at 1:07 PM, David Hutto <dwightdhutto@gmail.com&= gt; wrote:
I think, but haven't tr= ied, and this would be 2-3=A0 from __future__ import


On Thu, Jan 2, 20= 14 at 12:46 PM, Rustom Mody <rustompmody@gmail.com> wrot= e:
On Thu, Jan 2, 2014 at 11:06 PM, Ned Ba= tchelder <ned= @nedbatchelder.com> wrote:
> On 1/2/14 12:05 PM, Rustom Mody wrote:
>
>>
>> i'm not sure about this but isnt it normally the case that dif= ferent
>> 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. =A0A mechanism to prevent this seems like a good idea, b= ut since
> it wasn't in place at the dawn of Python 3, it would be difficult = to put in
> place now.

$ python3
Python 3.3.3 (default, Dec =A08 2013, 16:34:29)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "= license" for more information.
>>> from sys import path
>>> path
['', '/usr/lib/python3.3', '/usr/lib/python3.3/plat-i38= 6-linux-gnu',
'/usr/lib/python3.3/lib-dynload',
'/usr/local/lib/python3.3/dist-packages',
'/usr/lib/python3/dist-packages']


$ python
Python 2.7.6 (default, Dec =A06 2013, 21:56:56)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "= license" for more information.
>>> from sys import path
>>> path
['', '/usr/local/lib/python2.7/dist-packages/pip-1.0-py2.7.egg&= #39;,
'/usr/lib/python2.7', '/usr/lib/python2.7/plat-i386-linux-gnu&#= 39;,
'/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old',<= br> '/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages/PILcompat',
'/usr/lib/python2.7/dist-packages/gst-0.10',
'/usr/lib/python2.7/dist-packages/gtk-2.0',
'/usr/lib/pymodules/python2.7',
'/usr/lib/python2.7/dist-packages/wx-2.8-gtk2-unicode']


So as far as I can see (on a debian linux system) the paths are
clearly 2.7-prefixed or 3.3-prefixed.

So apart from being stupid and/or malicious to munge sys.path to tread
on the other python's toes...???

Oh ok I get what you are saying: python3 will not recognize a python2
package and install it seemingly correctly but actually wrongly
--
https://mail.python.org/mailman/listinfo/python-list



--
Best Regards,
David Hutto
= CEO: http://www.hitwebdevelopment.com



--
Best Regards,
David Hutto
<= b>CEO: http://www.hitwebdevelopment.com
--047d7b5d5a42fe1e9f04ef00d7f6--