-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/2016 05:35 AM, Marius Gedminas wrote:
> And people who run build Python 2.7 with './configure && make && make
> install'
>
> Why does upstream Python default to UCS-2 builds on Linux anyway?
I don't recall if it had any bearing on the
On 8 February 2016 at 09:07, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/06/2016 05:35 AM, Marius Gedminas wrote:
>
>> And people who run build Python 2.7 with './configure && make && make
>> install'
>>
>> Why does upstream Python default
On 6 February 2016 at 21:26, Marius Gedminas wrote:
> On Sat, Feb 06, 2016 at 09:18:39PM +1000, Nick Coghlan wrote:
>> On 6 February 2016 at 20:35, Marius Gedminas wrote:
>> > FWIW the rationale Pyenv gave when they rejected a bug asking for UCS-4
>> > builds
On Sat, Feb 06, 2016 at 09:18:39PM +1000, Nick Coghlan wrote:
> On 6 February 2016 at 20:35, Marius Gedminas wrote:
> > FWIW the rationale Pyenv gave when they rejected a bug asking for UCS-4
> > builds by default was "we prefer to follow upstream defaults".
>
> In this case,
On 6 February 2016 at 20:35, Marius Gedminas wrote:
> On Sat, Feb 06, 2016 at 03:04:48PM +1000, Nick Coghlan wrote:
>> That means the only folks that seem likely to miss out on pre-built
>> binaries this way would be Python 2.7 pyenv users.
>
> And people who run build Python
On Feb 5, 2016 8:47 AM, "Nate Coraor" wrote:
>
[...]
> - Add SOABI tags to platform-specific wheels built for Python 2.X (Pull
Request
> #55, Issue #63, Issue #101)
I can't quite untangle all the documents linked from this PR, so let me ask
here :-). Does this mean that python
On Feb 5, 2016 9:54 AM, "Nate Coraor" wrote:
>
> On Fri, Feb 5, 2016 at 12:46 PM, Nathaniel Smith wrote:
>>
>> On Feb 5, 2016 8:47 AM, "Nate Coraor" wrote:
>> >
>> [...]
>> > - Add SOABI tags to platform-specific wheels built for Python 2.X