Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 22, 2016, at 11:15 PM, Nick Coghlan wrote: > > On 22 December 2016 at 09:08, Chris Barker > wrote: > And there are utilities that let you run a script in a given environment: > >

Re: [Distutils] Maintaining a curated set of Python packages

On 22 December 2016 at 09:08, Chris Barker wrote: > And there are utilities that let you run a script in a given environment: > > https://github.com/pelson/conda-execute > > (and maybe others) > https://pypi.python.org/pypi/pipsi (pip Script Installer) creates a dedicated

Re: [Distutils] Maintaining a curated set of Python packages

On Fri, Dec 16, 2016 at 5:51 AM, Daniel Holth wrote: > One possibility to consider is that virtualenv itself is a bad idea. Why > should the Python interpreter executable, rather than the program being > run, determine the set of packages that is available for import? > well,

Re: [Distutils] Maintaining a curated set of Python packages

On Thu, Dec 15, 2016 at 8:29 PM, Glyph Lefkowitz wrote: > At the beginning of your story you mentioned the GUI client - *that* is > the missing piece ;). I've been saying for years that we need a Python.app > that lets you easily bootstrap all this stuff: walk you

Re: [Distutils] Maintaining a curated set of Python packages

On 17 December 2016 at 06:40, Glyph Lefkowitz wrote: > On Dec 16, 2016, at 5:51 AM, Daniel Holth wrote: > > One possibility to consider is that virtualenv itself is a bad idea. Why > should the Python interpreter executable, rather than the program

Re: [Distutils] Maintaining a curated set of Python packages

Glyph Lefkowitz wrote: "New Project" could just create a requirements.txt and a setup.py for you, alongside a git repo and a virtualenv for that project. Or, the UI could be geared towards setting up a tox.ini rather than a virtualenv, and run everything through tox so it's in an isolated

Re: [Distutils] Maintaining a curated set of Python packages

On Fri, Dec 16, 2016 at 3:40 PM Glyph Lefkowitz wrote: > On Dec 16, 2016, at 5:51 AM, Daniel Holth wrote: > > I'm also a visual studio code fan. It is the first editor I've tried that > feels lightweight like Vim but has the power of many plugins.

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 16, 2016, at 5:07 AM, Nick Coghlan wrote: > > On 16 December 2016 at 20:57, Glyph Lefkowitz > wrote: > > Anyhow, Xcode is far from perfect - many of the places it touches the UNIX > pipeline are extremely

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 16, 2016, at 5:51 AM, Daniel Holth wrote: > > I'm also a visual studio code fan. It is the first editor I've tried that > feels lightweight like Vim but has the power of many plugins. That, and the > text rendering is excellent. > >

Re: [Distutils] Maintaining a curated set of Python packages

If people are serious about trying to prototype this stuff then the easiest way might be coming up with shell scripts that do the prompting if it's faster to iterate that way than doing a full-blown GUI. Now that WIndows 10 has WSL/Bash it means for the first time all 3 major OSs have a common

Re: [Distutils] Maintaining a curated set of Python packages

z" <gl...@twistedmatrix.com> Cc: "Barry Warsaw" <ba...@python.org>; "DistUtils mailing list" <Distutils-Sig@python.org> Subject: Re: [Distutils] Maintaining a curated set of Python packages On 16 December 2016 at 20:57, Glyph Lefkowitz <gl...@twiste

Re: [Distutils] Maintaining a curated set of Python packages

I'm also a visual studio code fan. It is the first editor I've tried that feels lightweight like Vim but has the power of many plugins. That, and the text rendering is excellent. https://pypi.python.org/pypi/Stallion is a lovely GUI package manager. One possibility to consider is that virtualenv

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 20:57, Glyph Lefkowitz wrote: > > Anyhow, Xcode is far from perfect - many of the places it touches the UNIX > pipeline are extremely sharp edges you can easily impale yourself on (and > don't get me started about codesigning) - but it nevertheless

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 9:23 PM, Nick Coghlan wrote: > > On 16 December 2016 at 14:29, Glyph Lefkowitz > wrote: >> On Dec 15, 2016, at 8:18 PM, Nick Coghlan > > wrote:

Re: [Distutils] Maintaining a curated set of Python packages

On Saturday, December 10, 2016, Wes Turner wrote: > Here are some standardized (conda) package versions: https://github.com/ > jupyter/docker-stacks/blob/master/scipy-notebook/Dockerfile > > IDK how they choose packages - what "criteria for inclusion" - for the

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 14:29, Glyph Lefkowitz wrote: > On Dec 15, 2016, at 8:18 PM, Nick Coghlan wrote: > > At the beginning of your story you mentioned the GUI client - *that* is > the missing piece ;). I've been saying for years that we need a

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Nick Coghlan wrote: > On 16 December 2016 at 05:50, Paul Moore > wrote: > > On 15 December 2016 at 19:13, Wes Turner > wrote: > >>> Just to add my POV, I also find your

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 8:33 PM, Donald Stufft wrote: > > >> On Dec 15, 2016, at 11:29 PM, Glyph Lefkowitz > > wrote: >> >> User-curated package sets strikes me as the _lowest_ priority feature out of >> all of those

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 11:29 PM, Glyph Lefkowitz wrote: > > User-curated package sets strikes me as the _lowest_ priority feature out of > all of those I don’t think anyone in the PyPA is planning on working on this currently. It was a possible idea that was spawned

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 8:18 PM, Nick Coghlan wrote: > > On 16 December 2016 at 07:14, Glyph Lefkowitz > wrote: >> On Dec 15, 2016, at 6:39 AM, Donald Stufft > > wrote: >>

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 07:14, Glyph Lefkowitz wrote: > On Dec 15, 2016, at 6:39 AM, Donald Stufft wrote: > Theoretically we could allow people to not just select packages, but also > package specifiers for their “curated package set”, so instead of

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 05:50, Paul Moore wrote: > On 15 December 2016 at 19:13, Wes Turner wrote: >>> Just to add my POV, I also find your posts unhelpful, Wes. There's not >>> enough information for me to evaluate what you say, and you offer no >>>

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 6:39 AM, Donald Stufft wrote: > > >> On Dec 15, 2016, at 9:35 AM, Steve Dower > > wrote: >> >> The "curated package sets" on PyPI idea sounds a bit like Steam's curator >> lists, which I like to

Re: [Distutils] Maintaining a curated set of Python packages

On 15 December 2016 at 19:13, Wes Turner wrote: >> Just to add my POV, I also find your posts unhelpful, Wes. There's not >> enough information for me to evaluate what you say, and you offer no >> actual solutions to what's being discussed. > > > I could quote myself

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Paul Moore wrote: > On 15 December 2016 at 15:58, Nick Coghlan > wrote: > > On 16 December 2016 at 01:38, Wes Turner > wrote: > >> On Thursday, December 15, 2016, Nick

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Nick Coghlan wrote: > On 16 December 2016 at 01:38, Wes Turner > wrote: > > On Thursday, December 15, 2016, Nick Coghlan > wrote: > >> This answer hasn't changed the last

Re: [Distutils] Maintaining a curated set of Python packages

On 15 December 2016 at 15:58, Nick Coghlan wrote: > On 16 December 2016 at 01:38, Wes Turner wrote: >> On Thursday, December 15, 2016, Nick Coghlan wrote: >>> This answer hasn't changed the last dozen times you've brought up >>>

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 01:38, Wes Turner wrote: > On Thursday, December 15, 2016, Nick Coghlan wrote: >> This answer hasn't changed the last dozen times you've brought up >> JSON-LD. It isn't *going* to change. So please stop bringing it up. > > > No,

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Wes Turner wrote: > > > On Thursday, December 15, 2016, Nick Coghlan > wrote: > >> On 16 December 2016 at 00:39, Donald Stufft wrote: >> >

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Nick Coghlan wrote: > On 16 December 2016 at 00:57, Wes Turner > wrote: > > This would be a graph. JSONLD? > > #PEP426JSONLD: > > - https://www.google.com/search?q=pep426jsonld > > -

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Nick Coghlan wrote: > On 16 December 2016 at 00:39, Donald Stufft > wrote: > > Theoretically we could allow people to not just select packages, but also > > package specifiers for their “curated package set”,

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 00:57, Wes Turner wrote: > This would be a graph. JSONLD? > #PEP426JSONLD: > - https://www.google.com/search?q=pep426jsonld > - https://github.com/pypa/interoperability-peps/issues/31 > > With JSONLD, we could merge SoftwarePackage metadata with >

Re: [Distutils] Maintaining a curated set of Python packages

> Theoretically we could allow people to not just select packages, but also package specifiers for their “curated package set”, so instead of saying “requests”, you could say “requests~=2.12” or “requests==2.12.2”. If we really wanted to get slick we could even provide a requirements.txt file

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Wes Turner wrote: > > > On Thursday, December 15, 2016, Donald Stufft > wrote: > >> >> On Dec 15, 2016, at 9:35 AM, Steve Dower wrote: >> >> The

Re: [Distutils] Maintaining a curated set of Python packages

On 16 December 2016 at 00:39, Donald Stufft wrote: > Theoretically we could allow people to not just select packages, but also > package specifiers for their “curated package set”, so instead of saying > “requests”, you could say “requests~=2.12” or “requests==2.12.2”. If we >

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 15, 2016, Donald Stufft wrote: > > On Dec 15, 2016, at 9:35 AM, Steve Dower > wrote: > > The "curated package sets" on PyPI idea sounds a bit like Steam's curator > lists,

Re: [Distutils] Maintaining a curated set of Python packages

ld Stufft" <don...@stufft.io> Sent: ‎12/‎15/‎2016 4:21 To: "Freddy Rietdijk" <freddyrietd...@fridh.nl> Cc: "DistUtils mailing list" <Distutils-Sig@python.org>; "Barry Warsaw" <ba...@python.org> Subject: Re: [Distutils] Maintaining a cura

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 9:35 AM, Steve Dower wrote: > > The "curated package sets" on PyPI idea sounds a bit like Steam's curator > lists, which I like to think of as Twitter for game reviews. You can follow a > curator to see their comments on particular games, and the

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 15, 2016, at 7:13 AM, Freddy Rietdijk wrote: > > > Putting the conclusion first, I do see value in better publicising > > "Recommended libraries" based on some automated criteria like: > > Yes, we should recommend third-party libraries in a trusted place like

Re: [Distutils] Maintaining a curated set of Python packages

It's interesting to read about how other distributions upgrade their package sets. In Nixpkgs most packages are updated manually. Some frameworks/languages provide their dependencies declarative, in which case it becomes 'straightforward' to include whole package sets, like in the case of Haskell.

Re: [Distutils] Maintaining a curated set of Python packages

On 15 December 2016 at 03:41, Chris Barker wrote: [Barry wrote] >> Ubuntu has an elaborate automated system for testing some dimension of >> compatibility issues between packages, not just Python packages. Debian >> has >> the same system but isn't gated on the results. >

Re: [Distutils] Maintaining a curated set of Python packages

> > > I think it's unfair to describe these efforts as a "kludge"; I was specifically referring to using wheels to deliver C libs-- pip+wheel were not designed for that. But I don't mean to offend, there has been a lot of great work done, and yes, the situation has much improved as a result.

Re: [Distutils] Maintaining a curated set of Python packages

> On Dec 14, 2016, at 9:41 AM, Chris Barker wrote: > > As pointed out by others, there are external groups doing "curating". > conda-forge is one such project, so I'll comment from that perspective: > > > It's difficult because the definition of compatibility is highly

Re: [Distutils] Maintaining a curated set of Python packages

As pointed out by others, there are external groups doing "curating". conda-forge is one such project, so I'll comment from that perspective: It's difficult because the definition of compatibility is highly dependent on > > the consumer's environment. For example, C extension compatibility will

Re: [Distutils] Maintaining a curated set of Python packages

Here are some standardized (conda) package versions: https://github.com/jupyter/docker-stacks/blob/master/scipy-notebook/Dockerfile On Thursday, December 8, 2016, Wes Turner wrote: > > > On Thursday, December 8, 2016, Nick Coghlan

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 8, 2016, Nick Coghlan wrote: > Putting the conclusion first, I do see value in better publicising > "Recommended libraries" based on some automated criteria like: > > - recommended in the standard library documentation > - available via 1 or more

Re: [Distutils] Maintaining a curated set of Python packages

Putting the conclusion first, I do see value in better publicising "Recommended libraries" based on some automated criteria like: - recommended in the standard library documentation - available via 1 or more cross-platform commercial Python redistributors - available via 1 or more Linux distro

Re: [Distutils] Maintaining a curated set of Python packages

On 2016-12-08 10:05:47 -0600 (-0600), Wes Turner wrote: [...] > http://docs.openstack.org/developer/pbr/ > > - pbr does away with setup.py and install_requires in favor of just > requirements.txt [...] It doesn't entirely "do away with setup.py" (it still relies on a relatively minimal

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 8, 2016, Wes Turner wrote: > > > On Thursday, December 1, 2016, Freddy Rietdijk > wrote: > >> Hi, >> >> I would like to propose that, as a community, we jointly

Re: [Distutils] Maintaining a curated set of Python packages

On Thursday, December 1, 2016, Freddy Rietdijk wrote: > Hi, > > I would like to propose that, as a community, we jointly maintain a > curated set of Python packages that are known to work together. These > packages would receive security updates for some time and every

Re: [Distutils] Maintaining a curated set of Python packages

On Dec 01, 2016, at 10:45 AM, Freddy Rietdijk wrote: >Having a compatible set of packages is not only interesting for developers, >but also for downstream distributions. All distributions try to find a set >of packages that are working together and release them. This is a lot of >work, and I

Re: [Distutils] Maintaining a curated set of Python packages

On 3 December 2016 at 03:34, Freddy Rietdijk wrote: > > On Fri, Dec 2, 2016 at 4:33 PM, Robert T. McGibbon > wrote: >> >> Isn't this issue already solved by (and the raison d'être of) the multiple >> third-party Python redistributors, like the various

Re: [Distutils] Maintaining a curated set of Python packages

On Fri, Dec 2, 2016 at 4:33 PM, Robert T. McGibbon wrote: > Isn't this issue already solved by (and the raison d'être of) the multiple > third-party Python redistributors, like the various OS package maintainers, > Continuum's Anaconda, Enthought Canopy, ActiveState Python,

Re: [Distutils] Maintaining a curated set of Python packages

Isn't this issue already solved by (and the raison d'être of) the multiple third-party Python redistributors, like the various OS package maintainers, Continuum's Anaconda, Enthought Canopy, ActiveState Python, WinPython, etc? [image: Inline image 1] -Robert On Thu, Dec 1, 2016 at 4:45 AM,

[Distutils] Maintaining a curated set of Python packages

Hi, I would like to propose that, as a community, we jointly maintain a curated set of Python packages that are known to work together. These packages would receive security updates for some time and every couple of months a new major release of the curated set comes available. The idea of this