matplotlib-devel Mailing List for matplotlib

Hello,

I will be on Christmas vacation until January 6.
Unfortunately I won't have time to fix the square-root
positioning problem for the PostScript backend before
I leave.

All the best and a merry Christmas,
Jochen
--=20
http://seehuhn.de/

>>>>> "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

On Sun, 2004-12-12 at 15:09 -0600, John Hunter wrote:
> >>>>> "Steve" == Steve Chaplin <ste...@ya...> writes:
> 
>     Steve> I suggest - for optional modules (like dates), only import
>     Steve> them when they are required (when the plot actually has a
>     Steve> date) - for all modules try to minimise the amount of code
>     Steve> that will execute upon import, especially function calls.
> 
>     Steve> What do you think?
> 
> Sounds great.  Thanks for tracking this one down.  A 10% speedup is
> well worth it.  It sounds like the dates module should also cache the
> timezone info.  Do you want to take the lead on this one?  
> 
> JDH
Out of these timezones in dates.py
UTC      = timezone('UTC')
Eastern  = timezone('US/Eastern')
Central  = timezone('US/Central')
Mountain = timezone('US/Mountain')
Pacific  = timezone('US/Pacific')
London   = timezone('Europe/London')
Paris    = timezone('Europe/Paris')
Berlin   = timezone('Europe/Berlin')
Moscow   = timezone('Europe/Moscow')

As far as I can see the only timezones actually used are
UTC - as a function default value, and Pacific - used in __main__
Is it OK to remove all the unused ones, or is there something that
relies on them?

Steve

>>>>> "Norbert" == Norbert Nemec <Nor...@gm...> writes:

    Norbert> Doing the commands: ------------------------------ from
    Norbert> matplotlib.matlab import * plot((1,2),(3,4))
    Norbert> figtext(0.5,0.5,"$\sqrt 2$") savefig("tryout.eps")
    Norbert> ------------------------------

    Norbert> diplays the sqrt sign shifted upwards against the regular
    Norbert> text.

Looks like the dreaded cmex bug.  Paul, any ideas?

JDH