SourceForge logo
SourceForge logo
Menu

Re: [matplotlib-devel] Performance and dates

From: John H. <jdh...@ac...> - 2004年12月13日 15:14:02
>>>>> "Steve" == Steve Chaplin <ste...@ya...> writes:
 Steve> Out of these timezones in dates.py UTC = timezone('UTC')
 Steve> Eastern = timezone('US/Eastern') Central =
 Steve> timezone('US/Central') Mountain = timezone('US/Mountain')
 Steve> Pacific = timezone('US/Pacific') London =
 Steve> timezone('Europe/London') Paris = timezone('Europe/Paris')
 Steve> Berlin = timezone('Europe/Berlin') Moscow =
 Steve> timezone('Europe/Moscow')
 Steve> As far as I can see the only timezones actually used are
 Steve> UTC - as a function default value, and Pacific - used in
 Steve> __main__ Is it OK to remove all the unused ones, or is
 Steve> there something that relies on them?
Well, I provided these for convenience for people to import from the
dates module. It never occurred to me that simply instantiating 7
objects would carry such a performance hit. However, it doesn't
appear that I documented this anywhere, so it should be safe to remove
them - just make a note in the API_CHANGES file that they are gone and
I'll mention it in the release notes.
JDH

View entire thread

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /