Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On Tue, Feb 16, 2016 at 4:10 PM, Glyph Lefkowitz wrote: > > This whole section is about a tool to automatically identify possible > issues with these wheels - > https://www.python.org/dev/peps/pep-0513/#auditwheel - so I don't even > really know what you mean by this

Re: [Distutils] Alternative build system abstraction PEP

> ... The ideal would be that there would be a single static pypackage.cfg that could be dropped into any "version 0" VCS checkout to convert I think you mean "pypackage.json" here, not .cfg? -Robert On Tue, Feb 16, 2016 at 8:43 PM, Robert Collins wrote: > Cool.

Re: [Distutils] abstract build system PEP update

On Tue, Feb 16, 2016 at 04:10:43PM +1300, Robert Collins wrote: > diff --git a/build-system-abstraction.rst b/build-system-abstraction.rst > index a6e4712..56464f1 100644 > --- a/build-system-abstraction.rst > +++ b/build-system-abstraction.rst > @@ -68,12 +68,15 @@ modelled on pip's existing use

Re: [Distutils] Alternative build system abstraction PEP

Cool. I've replied on the PR as well, but my understanding from Donald was that from pip's perspective, the spawn interface being the contract was preferred; the other two differences are I think mostly cosmetic - except that I'm very worried about the injection possibilities of the calling code

[Distutils] Alternative build system abstraction PEP

Hi all, Finally found the time to sit down and take the various drafts I've sent of this to the list before, add a more detailed rationale section, and turn it into a pull request: https://github.com/pypa/interoperability-peps/pull/63 I've also included the text below for reference, in case

Re: [Distutils] Don't Use `sudo pip install´ (was Re: [final version?] PEP 513…)

> On Feb 16, 2016, at 6:12 PM, Glyph Lefkowitz wrote: > >> >> On Feb 16, 2016, at 5:00 PM, Noah Kantrowitz wrote: >> >> >>> On Feb 16, 2016, at 4:46 PM, Glyph Lefkowitz >>> wrote: >>> On Feb 16, 2016, at

Re: [Distutils] Don't Use `sudo pip install´ (was Re: [final version?] PEP 513…)

> On Feb 16, 2016, at 5:00 PM, Noah Kantrowitz > wrote: > > >> On Feb 16, 2016, at 4:46 PM, Glyph Lefkowitz > > wrote: >> >>> >>> On Feb 16, 2016, at 4:33 PM, Noah Kantrowitz

Re: [Distutils] Don't Use `sudo pip install´ (was Re: [final version?] PEP 513…)

> On Feb 16, 2016, at 4:46 PM, Glyph Lefkowitz wrote: > >> >> On Feb 16, 2016, at 4:33 PM, Noah Kantrowitz wrote: >> >> >>> On Feb 16, 2016, at 4:27 PM, Glyph Lefkowitz >>> wrote: >>> >>> On Feb 16, 2016, at

Re: [Distutils] Don't Use `sudo pip install´ (was Re: [final version?] PEP 513…)

> On Feb 16, 2016, at 4:33 PM, Noah Kantrowitz > wrote: > > >> On Feb 16, 2016, at 4:27 PM, Glyph Lefkowitz > > wrote: >> >> >>> On Feb 16, 2016, at 4:13 PM, Noah Kantrowitz

Re: [Distutils] Don't Use `sudo pip install´ (was Re: [final version?] PEP 513…)

> On Feb 16, 2016, at 4:27 PM, Glyph Lefkowitz wrote: > > >> On Feb 16, 2016, at 4:13 PM, Noah Kantrowitz wrote: >> >> As someone that handles the tooling side, I don't care how it works as long >> as there is an override for tooling a la

[Distutils] Don't Use `sudo pip install´ (was Re: [final version?] PEP 513…)

> On Feb 16, 2016, at 4:13 PM, Noah Kantrowitz wrote: > > As someone that handles the tooling side, I don't care how it works as long > as there is an override for tooling a la Chef/Puppet. For stuff like > Supervisord, it is usually the least broken path to install the

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

> On Feb 16, 2016, at 4:10 PM, Glyph Lefkowitz wrote: > >> >> On Feb 16, 2016, at 3:05 AM, Matthias Klose wrote: >> >> On 02.02.2016 02:35, Glyph Lefkowitz wrote: >>> On Feb 1, 2016, at 3:37 PM, Matthias Klose wrote:

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

> On Feb 16, 2016, at 3:05 AM, Matthias Klose wrote: > > On 02.02.2016 02:35, Glyph Lefkowitz wrote: >> >>> On Feb 1, 2016, at 3:37 PM, Matthias Klose wrote: >>> >>> On 30.01.2016 00:29, Nathaniel Smith wrote: Hi all, I think this is ready

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On 02/16/2016 03:20 PM, Paul Moore wrote: > On 16 February 2016 at 14:14, Wayne Werner wrote: >> I've learned that *usually* linux distro repos lag way behind in updating >> their Python packages, so unless I *can't* install the package via pip, >> that's what I do. > >

Re: [Distutils] multiple backports of ipaddress and a world of pain

Code that uses py2-ipaddress will break upon migrating to Python 3, and potentially in really subtle ways. For instance, import py2_ipaddress as ipaddress ipaddress.ip_address(b'\x3a\x3a\x31\x32') ipaddress.ip_address(open('file', 'rb').read(4)) has different semantics in Python 2 and Python 3.

Re: [Distutils] deprecating pip install --target

On 13 February 2016 at 03:54, Steve Dower wrote: > I was also planning to use it in an upcoming project that has to "do its > own" package management. The aim was to install different versions of > packages in different directories and use sys.path modifications to

Re: [Distutils] deprecating pip install --target

On 13 February 2016 at 04:12, Daniel Holth wrote: > My setup-requires wrapper, adding pre-setup.py dependency installation to > setup.py, relies on this feature. It needs to install something in a > directory that is only added to PYTHONPATH during the installation and does >

Re: [Distutils] abstract build system PEP update

On 16 February 2016 at 22:40, Paul Moore wrote: > On 16 February 2016 at 03:10, Robert Collins > wrote: >> -The file ``pypa.json`` acts as neutron configuration file for pip and other >> +The file ``pypa.json`` acts as neutral configuration file

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On Feb 16, 2016 3:05 AM, "Matthias Klose" wrote: [...] > > You may call this sour grapes, but in the light of people installing > these wheels to replace/upgrade system installed eggs, it becomes an issue. It's fine to use such wheels in a virtual environment, however people tell

[Distutils] multiple backports of ipaddress and a world of pain

Hi All, (Apologies for copying in the maintainers of the two backports and django-netfields directly, I'm not sure you're on this distutils list...) This is painful and horrible, and I wish pip would prevent modules/packages with the same name being installed by different distributions at

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On Feb 16, 2016, at 06:01 PM, Matthias Klose wrote: >I know we had such an issue where pip accidentally modified system installed >files, maybe Barry still remembers the details ... I don't, but I hope that should not be a problem these days, with modern pip on modern Debian/Ubuntu systems. We

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On 16.02.2016 15:43, David Cournapeau wrote: On Tue, Feb 16, 2016 at 11:05 AM, Matthias Klose wrote: On 02.02.2016 02:35, Glyph Lefkowitz wrote: On Feb 1, 2016, at 3:37 PM, Matthias Klose wrote: On 30.01.2016 00:29, Nathaniel Smith wrote: Hi all, I

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On 16.02.2016 15:20, Paul Moore wrote: On 16 February 2016 at 14:14, Wayne Werner wrote: I've learned that *usually* linux distro repos lag way behind in updating their Python packages, so unless I *can't* install the package via pip, that's what I do. that's how

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On Tue, Feb 16, 2016 at 11:05 AM, Matthias Klose wrote: > On 02.02.2016 02:35, Glyph Lefkowitz wrote: > >> >> On Feb 1, 2016, at 3:37 PM, Matthias Klose wrote: >>> >>> On 30.01.2016 00:29, Nathaniel Smith wrote: >>> Hi all, I think this is ready

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On 16 February 2016 at 14:14, Wayne Werner wrote: > I've learned that *usually* linux distro repos lag way behind in updating > their Python packages, so unless I *can't* install the package via pip, > that's what I do. Yeah, and that's what I'd count as an issue between

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On Tue, 16 Feb 2016, Paul Moore wrote: On 16 February 2016 at 11:05, Matthias Klose wrote: You may call this sour grapes, but in the light of people installing these wheels to replace/upgrade system installed eggs, it becomes an issue. It's fine to use such wheels in a

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On 16 February 2016 at 11:05, Matthias Klose wrote: > You may call this sour grapes, but in the light of people installing > these wheels to replace/upgrade system installed eggs, it becomes an issue. > It's fine to use such wheels in a virtual environment, however people tell >

Re: [Distutils] [final version?] PEP 513 - A Platform Tag for Portable Linux Built Distributions

On 02.02.2016 02:35, Glyph Lefkowitz wrote: On Feb 1, 2016, at 3:37 PM, Matthias Klose wrote: On 30.01.2016 00:29, Nathaniel Smith wrote: Hi all, I think this is ready for pronouncement now -- thanks to everyone for all their feedback over the last few weeks! I don't

Re: [Distutils] abstract build system PEP update

On 16 February 2016 at 03:10, Robert Collins wrote: > -The file ``pypa.json`` acts as neutron configuration file for pip and other > +The file ``pypa.json`` acts as neutral configuration file for pip and other Aw, I was looking forward to controlling my nuclear power