Re: [pypy-dev] __pycache__ folders

Hi Ronny (2012.07.31_17:12:15_+0200) > i would dare to say that Distributions that manage semi-compatible, > but distro specific "forks" of open source projects > instead of aiming for a distro compatible upstream > create quite some grief for developers. Weighed up against making grief for users.

Re: [pypy-dev] __pycache__ folders

Hi, i would dare to say that Distributions that manage semi-compatible, but distro specific "forks" of open source projects instead of aiming for a distro compatible upstream create quite some grief for developers. after all users don't tend to notice those incompatibilities, but it breaks the

Re: [pypy-dev] __pycache__ folders

Hi Armin (2012.07.31_16:26:50_+0200) > My point of view is that this goes in the same pack of > incompatibilities introduced by some distributions as splitting the > install path (which we recommend to install as one block in > /opt/pypy-1.9). Most distros won't use /opt. We tend to follow the FHS

Re: [pypy-dev] __pycache__ folders

Hi Stefano, On Tue, Jul 31, 2012 at 1:34 PM, Stefano Rivera wrote: > And I do my best to minimize that. In this case, I thought it was worth > the delta. My point of view is that this goes in the same pack of incompatibilities introduced by some distributions as splitting the install path (which

Re: [pypy-dev] __pycache__ folders

Hi Christian (2012.07.31_13:05:48_+0200) > >vaguely inline Hrm, I never finished that sentance, because I went back and made the point earlier in the mail. > Your backport makes sense, but the reasoning should be identical > between cpython and pypy. > If cpython does not do it, pypy does not do

Re: [pypy-dev] __pycache__ folders

On 31.07.12 12:35, Stefano Rivera wrote: Hi Armin (2012.07.31_12:10:01_+0200) I think that PyPy shouldn't do that, because CPython doesn't. If Debian/Ubuntu also hacked CPython to do that, then fine; we are then free to point users to them (blame them?) for issues :-) We did seriously consider

Re: [pypy-dev] __pycache__ folders

On Tue, Jul 31, 2012 at 12:35 PM, Stefano Rivera wrote: > Hi Armin (2012.07.31_12:10:01_+0200) >> I think that PyPy shouldn't do that, because CPython doesn't. If >> Debian/Ubuntu also hacked CPython to do that, then fine; we are then >> free to point users to them (blame them?) for issues :-) >

Re: [pypy-dev] __pycache__ folders

Hi Armin (2012.07.31_12:10:01_+0200) > I think that PyPy shouldn't do that, because CPython doesn't. If > Debian/Ubuntu also hacked CPython to do that, then fine; we are then > free to point users to them (blame them?) for issues :-) We did seriously consider hacking cpython to do that, before in

Re: [pypy-dev] __pycache__ folders

Hi Stefano, On Tue, Jul 31, 2012 at 11:44 AM, Stefano Rivera wrote: >> PyPy contains no logic to create or search for __pycache__. A grep >> tells me that neither does CPython 2.7. > > A Debian/Ubuntu pypy does, though. I think that PyPy shouldn't do that, because CPython doesn't. If Debian/Ub

Re: [pypy-dev] __pycache__ folders

Hi Armin (2012.07.31_09:25:08_+0200) > PyPy contains no logic to create or search for __pycache__. A grep > tells me that neither does CPython 2.7. You are probably confused by > py.test creating them. A Debian/Ubuntu pypy does, though. And IIRC, that's what travis CI is using. It's the pep3147

Re: [pypy-dev] __pycache__ folders

Hi Marcus, Armin, On Tue, Jul 31, 2012 at 09:25 +0200, Armin Rigo wrote: > Hi Marcus, > > PyPy contains no logic to create or search for __pycache__. A grep > tells me that neither does CPython 2.7. You are probably confused by > py.test creating them. ... creating them during a pypy test run

Re: [pypy-dev] __pycache__ folders

Hi Marcus, PyPy contains no logic to create or search for __pycache__. A grep tells me that neither does CPython 2.7. You are probably confused by py.test creating them. A bientôt, Armin. ___ pypy-dev mailing list pypy-dev@python.org http://mail.pyt

Re: [pypy-dev] __pycache__ folders

let me explain some more. I have may have thrown people with my use of "distribution". I just meant installed packages that you get from pypi or wherever, not the pypy distribution itself. e.g. one of our nose test cases installs and then uninstalls INITools (from pypi) it's not expecting to find

Re: [pypy-dev] __pycache__ folders

IMHO, *.pyc files should not be distributed with a binary pypy. This is probably an issue for the team who supply the pypy for travis-ci.org (since the __pycache__ files do not appear in the nightly or release builds on pypy.org) - I think they live at https://launchpad.net/~pypy

Re: [pypy-dev] __pycache__ folders

2012/7/30 Marcus Smith : > Hello: > > I'm working on trying to get the pip test suite passing for pypy. > I need to figure out the mechanism that turns on/off the use of > __pycache__ folders. > locally in my pypy v1.9 install, I only see normal *.pyc files for installed > distributions. > In Trav