From: "Barry Scott"
Sent: 7/28/2016 10:19
To: "Steve Dower"
Cc: "Python Dev"
Subject: Re: [Python-Dev] PEP 514: Python registration in the Windows registry
Why do you need SysArchitecture? Surely the 32bit pythons are registered in the
32bit registry and the 64
On 28 July 2016 at 17:51, Barry Scott wrote:
> Why do you need SysArchitecture? Surely the 32bit pythons are registered in
> the 32bit registry and the 64 bit pythons in the 64 bit registry.
Per-user installs go in HKEY_CURRENT_USER, which is not
architecture-specific. So you either need SysArch
Why do you need SysArchitecture? Surely the 32bit pythons are registered in the
32bit registry and the 64 bit pythons in the 64 bit registry.
you can side by side install python 3.4 but only if you install 64 bit first
then 32 bit second.
Barry
> On 15 Jul 2016, at 23:20, Steve Dower wrote:
Thanks Paul.
I'll update the headers on the PEP later today.
Top-posted from my Windows Phone
-Original Message-
From: "Paul Moore"
Sent: 7/24/2016 0:45
To: "Guido van Rossum"
Cc: "Steve Dower" ; "Python Dev"
Subject: Re: [Python-Dev
On 07/24/2016 12:45 AM, Paul Moore wrote:
This PEP is now accepted. Congratulations, Steve!
And more congratulations! :)
--
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
This PEP is now accepted. Congratulations, Steve! And thanks for
putting up with all of my last-minute questions :-)
Paul
On 23 July 2016 at 21:20, Guido van Rossum wrote:
> I'll let Paul pronounce. But you should probably have a BDFL-Delegate:
> ... header.
>
> On Sat, Jul 23, 2016 at 12:16 PM,
On 23Jul2016 1320, Guido van Rossum wrote:
I'll let Paul pronounce. But you should probably have a BDFL-Delegate:
... header.
Yeah, my headers are a bit outdated... I'm not even sure the $Revision$
and $Date$ variables are going to be substituted anymore (unless it's a
pep2html thing rather t
I'll let Paul pronounce. But you should probably have a BDFL-Delegate:
... header.
On Sat, Jul 23, 2016 at 12:16 PM, Steve Dower wrote:
> PEP 514 is now ready for pronouncement, so this is the last chance for any
> feedback (BDFL-delegate Paul has been active on the github PR, so I don't
> expect
PEP 514 is now ready for pronouncement, so this is the last chance for
any feedback (BDFL-delegate Paul has been active on the github PR, so I
don't expect he has a lot of feedback left).
The most major change from the previous post is the addition of some
code examples at the end. Honestly, I
On 19 July 2016 at 10:49, Paul Moore wrote:
> On 18 July 2016 at 18:01, Paul Moore wrote:
>> On 18 July 2016 at 17:33, Steve Dower wrote:
Some comments below.
>>>
>>> Awesome, thanks! Posted a pull request at
>>> https://github.com/python/peps/pull/59 for ease of diff reading, and some
>>>
On 18 July 2016 at 18:01, Paul Moore wrote:
> On 18 July 2016 at 17:33, Steve Dower wrote:
>>> Some comments below.
>>
>> Awesome, thanks! Posted a pull request at
>> https://github.com/python/peps/pull/59 for ease of diff reading, and some
>> commentary below (with aggressive snipping).
>
> Than
On 18 July 2016 at 17:33, Steve Dower wrote:
>> Some comments below.
>
> Awesome, thanks! Posted a pull request at
> https://github.com/python/peps/pull/59 for ease of diff reading, and some
> commentary below (with aggressive snipping).
Thanks - I'll do a proper review of that, but just wanted t
On 16Jul2016 1254, Paul Moore wrote:
On 15 July 2016 at 23:20, Steve Dower wrote:
Hi all
I'd like to get this PEP approved (status changed to Active, IIUC).
Some comments below.
Awesome, thanks! Posted a pull request at
https://github.com/python/peps/pull/59 for ease of diff reading, and
On 16 July 2016 at 18:59, Guido van Rossum wrote:
> Yup! Paul is now officially the BDFL-delegate for PEP 514.
OK. I've just been reviewing the PEP and have posted some comments.
There's a lot of words(!), but I don't think there's a huge amount of
substantive change, mostly it's just confirmatio
On 15 July 2016 at 23:20, Steve Dower wrote:
> Hi all
>
> I'd like to get this PEP approved (status changed to Active, IIUC).
Some comments below.
> So far (to my knowledge), Anaconda is writing out the new metadata and
> Visual Studio is reading it. Any changes to the schema now will require
>
Yup! Paul is now officially the BDFL-delegate for PEP 514.
On Sat, Jul 16, 2016 at 2:44 AM, Paul Moore wrote:
> On 15 July 2016 at 23:39, Steve Dower wrote:
>> On 15Jul2016 1526, Guido van Rossum wrote:
>>>
>>> I was going to delegate to our resident Windows expert, but that's you.
>>> :-(
>>>
>
Good catch, thanks.
Top-posted from my Windows Phone
-Original Message-
From: "Nick Coghlan"
Sent: 7/15/2016 23:53
To: "Steve Dower"
Cc: "Python Dev"
Subject: Re: [Python-Dev] PEP 514: Python registration in the Windows registry
On 16 July 201
On 15 July 2016 at 23:39, Steve Dower wrote:
> On 15Jul2016 1526, Guido van Rossum wrote:
>>
>> I was going to delegate to our resident Windows expert, but that's you.
>> :-(
>>
>> Can you suggest someone else? I really don't want to swap in what I
>> once knew about the Windows registry...
>
>
>
On 16 July 2016 at 08:20, Steve Dower wrote:
> Backwards Compatibility
> ---
>
> Python 3.4 and earlier did not distinguish between 32-bit and 64-bit builds
> in
> ``sys.winver``. As a result, it is possible to have valid side-by-side
> installations of both 32-bit and 64-bit i
On 15Jul2016 1526, Guido van Rossum wrote:
I was going to delegate to our resident Windows expert, but that's you. :-(
Can you suggest someone else? I really don't want to swap in what I
once knew about the Windows registry...
He might not be pleased at the nomination, but Paul Moore would be
I was going to delegate to our resident Windows expert, but that's you. :-(
Can you suggest someone else? I really don't want to swap in what I
once knew about the Windows registry...
On Fri, Jul 15, 2016 at 3:20 PM, Steve Dower wrote:
> Hi all
>
> I'd like to get this PEP approved (status chang
Hi all
I'd like to get this PEP approved (status changed to Active, IIUC).
So far (to my knowledge), Anaconda is writing out the new metadata and
Visual Studio is reading it. Any changes to the schema now will require
somewhat public review anyway, so I don't see any harm in approving the
PEP
22 matches
Mail list logo
