➜

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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, Arfrever, belopolsky, loewis, pitrou, vstinner
Date 2012-01-27.22:25:22
SpamBayes Score 1.6161578e-06
Marked as misclassified No
Message-id <CAP7h-xb-CTui-cWVj=BUdugeBZpj97L1DcdkRsyPEduE2qnR9g@mail.gmail.com>
In-reply-to <1327702626.58.0.87491170958.issue13882@psf.upfronthosting.co.za>
Content 
On Fri, Jan 27, 2012 at 5:17 PM, Antoine Pitrou <report@bugs.python.org> wrote:
> Well, creating a separate module is an anti-pattern in itself. calendar vs. time vs. datetime, anyone?

Are you serious? Since the invention of structural programming,
creating a separate module for distinct functionality has been one of
the most powerful design techniques.  If I recall correctly, most of
the original GoF patterns were about separating functionality into a
separate module or a separate class.  The calendar module is indeed a
historical odd-ball, but what is wrong with time and datetime?
History
Date User Action Args
2012-01-27 22:25:23Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, loewis, belopolsky, pitrou, vstinner, Arfrever
2012-01-27 22:25:22Alexander.Belopolskylinkissue13882 messages
2012-01-27 22:25:22Alexander.Belopolskycreate