Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Lennart Regebro
On Thu, Apr 9, 2015 at 1:31 AM, Alexander Belopolsky wrote: > Storing isdst in the datetime object would allow utcoffset(dt) to > distinguish between 1:30AM before clock change and 1:30AM after. Where do > you propose to store the offset? If you store it in dt, why would you need > the tzinfo?

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Alexander Belopolsky
On Wed, Apr 8, 2015 at 8:11 PM, Alex Lord wrote: > Newb question time, what's BoF > http://en.wikipedia.org/wiki/Birds_of_a_feather_%28computing%29 ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Un

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Alex Lord
Newb question time, what's BoF On Wed, Apr 8, 2015 at 7:31 PM, Alexander Belopolsky < alexander.belopol...@gmail.com> wrote: > > On Wed, Apr 8, 2015 at 6:52 PM, Isaac Schwabacher > wrote: > > > > > So "storing the offset" and "storing a flag" are not two alternative > solutions to the same probl

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Alexander Belopolsky
On Wed, Apr 8, 2015 at 7:32 PM, Chris Angelico wrote: > On Thu, Apr 9, 2015 at 8:32 AM, Alexander Belopolsky > wrote: > > A "named offset" is an abbreviation such as UTC, EST, MSK, MSD which (at > any > > given time) > > corresponds to a fixed offset from UTC. > > That assumes the abbreviations

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Chris Angelico
On Thu, Apr 9, 2015 at 8:32 AM, Alexander Belopolsky wrote: > A "named offset" is an abbreviation such as UTC, EST, MSK, MSD which (at any > given time) > corresponds to a fixed offset from UTC. That assumes the abbreviations are unique. They're not. Just this morning I had to explain to a new st

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Alexander Belopolsky
On Wed, Apr 8, 2015 at 6:52 PM, Isaac Schwabacher wrote: > > > So "storing the offset" and "storing a flag" are not two alternative solutions to the same problem- these > > are two solutions to two different problems. > > I'm viewing a time zone as a map from UTC to local time; for example, Americ

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Isaac Schwabacher
On 15-04-08, Alexander Belopolsky wrote: > > On Wed, Apr 8, 2015 at 3:57 PM, Isaac Schwabacher > wrote: > > > > On 15-04-08, Lennart Regebro wrote: > > > === Stdlib option 2: A datetime _is_dst flag === > > > > > > By having a flag on the datetime instance that says "this is in DST or > > > not

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Alexander Belopolsky
On Wed, Apr 8, 2015 at 3:57 PM, Isaac Schwabacher wrote: > > On 15-04-08, Lennart Regebro wrote: > > === Stdlib option 2: A datetime _is_dst flag === > > > > By having a flag on the datetime instance that says "this is in DST or not" > > the timezone implementation can be kept simpler. > > Storing

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Lennart Regebro
On Wed, Apr 8, 2015 at 9:57 PM, Isaac Schwabacher wrote: > On 15-04-08, Lennart Regebro wrote: >> === Stdlib option 2: A datetime _is_dst flag === >> >> By having a flag on the datetime instance that says "this is in DST or not" >> the timezone implementation can be kept simpler. > > Storing the o

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Lennart Regebro
On Wed, Apr 8, 2015 at 7:37 PM, Carl Meyer wrote: > Hi Lennart, > > On 04/08/2015 09:18 AM, Lennart Regebro wrote: >> I wrote PEP-431 two years ago, and never got around to implement it. >> This year I got some renewed motivation after Berker Peksağ made an >> effort of implementing it. >> I'm pla

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Isaac Schwabacher
On 15-04-08, Lennart Regebro wrote: > === Stdlib option 2: A datetime _is_dst flag === > > By having a flag on the datetime instance that says "this is in DST or not" > the timezone implementation can be kept simpler. Storing the offset itself instead of a flag makes things conceptually cleaner.

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Ryan Hiebert
On Apr 8, 2015, at 12:37, Carl Meyer wrote: >> Anyone interested in a session on this, mail me and we'll set up a >> time and place! > > I'm interested in the topic, and would probably attend a BoF at PyCon. I'm of a similar mind. ___ Python-Dev maili

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Carl Meyer
Hi Lennart, On 04/08/2015 09:18 AM, Lennart Regebro wrote: > I wrote PEP-431 two years ago, and never got around to implement it. > This year I got some renewed motivation after Berker Peksağ made an > effort of implementing it. > I'm planning to work more on this during the PyCon sprints, and als

Re: [Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Alexander Belopolsky
On Wed, Apr 8, 2015 at 11:18 AM, Lennart Regebro wrote: > === Stdlib option 2: A datetime _is_dst flag === > > By having a flag on the datetime instance that says "this is in DST or not" > the timezone implementation can be kept simpler. > I floated this idea [1] back in the days when we discuss

[Python-Dev] Status on PEP-431 Timezones

2015-04-08 Thread Lennart Regebro
Hi! I wrote PEP-431 two years ago, and never got around to implement it. This year I got some renewed motivation after Berker Peksağ made an effort of implementing it. I'm planning to work more on this during the PyCon sprints, and also have a BoF session or similar during the conference. Anyone

Re: [Python-Dev] ctypes module

2015-04-08 Thread Cristi Fati
Hi all, thank you for your responses. Apparently i was wrong in my previous email, ctypes (1.0.1 or 1.0.2) didn't have support for WinIA64 (libffi), there was an in-house implementation. However we are using the IA64 module extensively (including to successfully call LsaLogonUser). a much simpler

Re: [Python-Dev] ctypes module

2015-04-08 Thread Maciej Fijalkowski
for the record libffi supports itanium officially (but as usual I'm very skeptical how well it works on less used platforms) https://sourceware.org/libffi/ On Wed, Apr 8, 2015 at 1:32 PM, Nick Coghlan wrote: > On 8 April 2015 at 20:36, Maciej Fijalkowski wrote: >> I presume the reason was that n

Re: [Python-Dev] ctypes module

2015-04-08 Thread Nick Coghlan
On 8 April 2015 at 20:36, Maciej Fijalkowski wrote: > I presume the reason was that noone wants to maintain code for the > case where there are no buildbots available and there is no > development time available. You are free to put back in the files and > see if they work (they might not), but su

Re: [Python-Dev] ctypes module

2015-04-08 Thread Maciej Fijalkowski
I presume the reason was that noone wants to maintain code for the case where there are no buildbots available and there is no development time available. You are free to put back in the files and see if they work (they might not), but such things are usually removed if they're a maintenance burden