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 lemburg
Recipients alanjds, amaury.forgeotdarc, belopolsky, brett.cannon, brian.curtin, daniel.urban, davidfraser, eric.araujo, giampaolo.rodola, lemburg, mark.dickinson, pitrou, r.david.murray, rhettinger, techtonik, tim.peters, vstinner
Date 2011-08-10.17:39:52
SpamBayes Score 6.49405e-05
Marked as misclassified No
Message-id <4E42C262.5020608@egenix.com>
In-reply-to <1312997390.95.0.573390430663.issue9528@psf.upfronthosting.co.za>
Content
Alan Justino wrote:
> 
> I am getting a hard time trying to do some BDD with c-based datetime because I cannot mock it easily to force datetime.datetime.now() to return a desired value, making almost impossible to test time-based code, like the accounting system that I am refactoring right now.

It's usually better to use a central helper get_current_time() in
the application, than to use datetime.now() and others
directly.
History
Date User Action Args
2011-08-10 17:39:52lemburgsetrecipients: + lemburg, tim.peters, brett.cannon, rhettinger, amaury.forgeotdarc, mark.dickinson, davidfraser, belopolsky, pitrou, vstinner, techtonik, giampaolo.rodola, eric.araujo, r.david.murray, brian.curtin, daniel.urban, alanjds
2011-08-10 17:39:52lemburglinkissue9528 messages
2011-08-10 17:39:52lemburgcreate