➜

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, barry, belopolsky, cameron, catlee, davidfraser, eric.araujo, erik.stephens, guettli, hodgestar, jamesh, jribbens, loewis, mark.dickinson, ncoghlan, pboddie, pitrou, python-dev, r.david.murray, rhettinger, steve.roberts, techtonik, tim.peters, tomster, vstinner, werneck
Date 2012-06-19.03:22:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340076163.08.0.0781505118171.issue9527@psf.upfronthosting.co.za>
In-reply-to
Content 
> ... is a well-defined problem which does not have an adequate solution.

I meant to say "does not have an adequate solution *in the current datetime module*".  I think the enhanced datetime.astimezone() method will  solve this problem.
History
Date User Action Args
2012-06-19 03:22:43belopolskysetrecipients: + belopolsky, tim.peters, loewis, barry, jribbens, rhettinger, pboddie, jamesh, guettli, amaury.forgeotdarc, mark.dickinson, ncoghlan, davidfraser, pitrou, andersjm, catlee, vstinner, techtonik, tomster, werneck, hodgestar, Neil Muller, cameron, eric.araujo, erik.stephens, steve.roberts, r.david.murray, python-dev
2012-06-19 03:22:43belopolskysetmessageid: <1340076163.08.0.0781505118171.issue9527@psf.upfronthosting.co.za>
2012-06-19 03:22:42belopolskylinkissue9527 messages
2012-06-19 03:22:42belopolskycreate