[Python-Dev] Status on PEP-431 Timezones

Mark Lawrence breamoreboy at yahoo.co.uk
Mon Jul 27 19:06:02 CEST 2015

On 27/07/2015 15:45, Nick Coghlan wrote:
> On 28 July 2015 at 00:27, Steve Dower <Steve.Dower at microsoft.com> wrote:
>> Am I the only one feeling like this entire thread should be moved to
>> python-ideas at this point?
> Since this is an area where the discussion of implementation details
> and the discussion of the developer experience can easily end up at
> cross purposes, I'm wondering if there may be value in actually
> splitting those two discussions into different venues by creating a
> datetime-sig, and specifically inviting the pytz and dateutil
> developers to participate in the SIG as well.
> The traffic on a similarly niche group like import-sig is only
> intermittent, but it means that by the time we bring suggestions to
> python-ideas or python-dev, we've already thrashed out the low level
> arcana and know that whatever we're proposing *can* be made to work,
> leaving the core lists to focus on the question of whether or not the
> change *should* be made.
> Whether or not to do that would be up to the folks with a specific
> interest in working with dates and times, though.
> Cheers,
> Nick.

Would it be worth doing a straw poll to gauge how many people really 
need this, from my perspective anyway, level of complexity?  I've used 
datetimes a lot, but I don't even need naive timezones, completely dumb 
suits me.

Alternatively just go ahead, knowing that if the proposal isn't accepted 
into the stdlib it can at least go on pypi.

My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

More information about the Python-Dev mailing list