Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Thomas Güttler
Am 26.05.2016 um 20:28 schrieb Daniel Holth: Maybe there could be a way to say "the most recent release that has a wheel for my platform". That would help with the problem of binaries not being available concurrently with a new source distribution. I don't get what you want to say. If you ar

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Ionel Cristian Mărieș via Distutils-SIG
On Fri, May 27, 2016 at 2:25 PM, Thomas Güttler < guettl...@thomas-guettler.de> wrote: > I don't get what you want to say. > > If you are maintainer, then there is no "my platform". There is matrix: > ​Missing the context, but didn't he write that from user perspective? One could argue that​ get

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Daniel Holth
So this was a problem with eggs too. Let's say ZODB 3.0.1 was just released. You are happily using 3.0.0, the next version is a minor upgrade, but there are no precompiled packages for 3.0.1, so your build breaks on Friday morning when you are trying to deploy. Compiling it yourself is not an optio

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Chris Barker
Not that this isn't an issue, but: On Fri, May 27, 2016 at 5:34 AM, Daniel Holth wrote: > So this was a problem with eggs too. Let's say ZODB 3.0.1 was just > released. You are happily using 3.0.0, the next version is a minor upgrade, > but there are no precompiled packages for 3.0.1, so your bu

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Paul Moore
On 27 May 2016 at 17:28, Chris Barker wrote: > So I kind of like the idea of making wheels the default for distributing on > PyPi always -- even for pure python modules. And wheels are trivial to build > from pure python packages -- so why not? It would be *really* nice to have some sort of metad

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Donald Stufft
> On May 27, 2016, at 12:37 PM, Paul Moore wrote: > > On 27 May 2016 at 17:28, Chris Barker wrote: >> So I kind of like the idea of making wheels the default for distributing on >> PyPi always -- even for pure python modules. And wheels are trivial to build >> from pure python packages -- so wh

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Alex Grönholm
This reminds me of something I wanted to ask – how come the "virtualenv" tool installs wheel but the built-in "venv" tool does not? The latter is the currently recommended method of creating a virtualenv, isn't it? 27.05.2016, 19:40, Donald Stufft kirjoitti: On May 27, 2016, at 12:37 PM, Paul

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Paul Moore
On 27 May 2016 at 17:40, Donald Stufft wrote: >> On May 27, 2016, at 12:37 PM, Paul Moore wrote: >> >> On 27 May 2016 at 17:28, Chris Barker wrote: >>> So I kind of like the idea of making wheels the default for distributing on >>> PyPi always -- even for pure python modules. And wheels are triv

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Donald Stufft
> On May 27, 2016, at 12:43 PM, Alex Grönholm wrote: > > This reminds me of something I wanted to ask – how come the "virtualenv" tool > installs wheel but the built-in "venv" tool does not? The latter is the > currently recommended method of creating a virtualenv, isn't it? > virtualenv, by

Re: [Distutils] matrix: python_versions x supported_plattforms, cross-compiling vs VM

2016-05-27 Thread Daniel Holth
On Fri, May 27, 2016 at 12:28 PM Chris Barker wrote: > Not that this isn't an issue, but: > > On Fri, May 27, 2016 at 5:34 AM, Daniel Holth wrote: > >> So this was a problem with eggs too. Let's say ZODB 3.0.1 was just >> released. You are happily using 3.0.0, the next version is a minor upgrade