➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients Neil Muller, amaury.forgeotdarc, andersjm, belopolsky, catlee, davidfraser, eric.araujo, erik.stephens, guettli, hodgestar, jamesh, jribbens, loewis, mark.dickinson, pboddie, pitrou, rhettinger, steve.roberts, tebeka, techtonik, tim.peters, tomster, vstinner, werneck
Date 2011-01-30.05:52:55
SpamBayes Score 7.03134e-06
Marked as misclassified No
Message-id <AANLkTi=SVtH=HKSkRyAkd1N++mFbhTt7Dz45=CMWSPzQ@mail.gmail.com>
In-reply-to <1296363383.09.0.963872226996.issue9527@psf.upfronthosting.co.za>
Content 
On Sat, Jan 29, 2011 at 11:56 PM, Raymond Hettinger
<report@bugs.python.org> wrote:
..
> Also, I question whether the proposed API is correct.  ISTM that any code that sets the *dst*
> parameter is guaranteed to be wrong (hardwiring-in a value that will change every few months).

Can you elaborate on this?  ISTM that your argument would equally
apply to C/POSIX mktime() API.  It won't be the first time C/POSIX got
time handling wrong, but I doubt it is the case in this instance.
History
Date User Action Args
2011-01-30 05:52:56belopolskysetrecipients: + belopolsky, tim.peters, loewis, jribbens, rhettinger, pboddie, jamesh, guettli, amaury.forgeotdarc, tebeka, mark.dickinson, davidfraser, pitrou, andersjm, catlee, vstinner, techtonik, tomster, werneck, hodgestar, Neil Muller, eric.araujo, erik.stephens, steve.roberts
2011-01-30 05:52:55belopolskylinkissue9527 messages
2011-01-30 05:52:55belopolskycreate