matplotlib-devel Mailing List for matplotlib (Page 5)

On Thursday 06 April 2006 17:47, Christopher Barker wrote:
> Darren Dale wrote:
> > On Wednesday 05 April 2006 18:42, Christopher Barker wrote:
> >> Why not have a TexTempDir attribute stored somewhere, and write
> >> everything there?
> >
> > That's exactly what I'm trying to do. Or maybe I dont understand what you
> > are suggesting.
>
> I'm confused about what "working directory" you're talking about. I
>
> thought you meant Python's working directory:
> >>> os.getcwd()
>
> However, if you mean a sub-process's working directory:
>
> os.system("cd temp; ls")
Thank you for that suggestion, it turned out to be an acceptable solution. 
Changes in svn 2274.
I hope the recent lack of bug reports concerning the usetex option is an 
indication that the current implementation is approaching stability. I dont 
know if I have mentioned it here, but I think I worked out the clipping 
problems we were having with ghostscript-7.07. At any rate, I would 
appreciate some testing now, since I changed the way subprocesses are handled 
and where temporary files are created.
Darren

As a follow-up to my message on the users list dated 23 March, here are 
some patches for one of you keen developers. Here's the message to save 
you looking it up:
> I've found the source of this figimage problem. In _backend_agg.cpp
> RendererAgg::draw_image is expecting 4 arguments and is being passed
> 5 by the FigureImage draw method in image.py The offending line is:
> 
> renderer.draw_image(self.ox, self.oy, im, self.origin,
> self.figure.bbox)
> 
> Changing this to
> 
> renderer.draw_image(self.ox, self.oy, im, self.figure.bbox)
> 
> solved the problem for me.
> 
> I checked and found that the RendererAgg draw_image() virtual method
> has 5 arguments, which seems to be the source of the problem, so
> either this needs changing or the backend code does.
> 
> _draw_image() in backend_agg.py makes the call with 3 arguments, so
> this needs fixing too.
> 
> The draw_image() method in backend_emf.py has a stub override with 5
> arguments, so this may need changing too, although it isn't causing
> harm yet. I'm not sure all of these are real problems because I
> didn't try too hard to understand how the backends work.
I don't really know what to exercise to test these out. I'm not familiar 
enough with all the interactions. The patches deal directly with my 
above findings, but could well break something. With those caveats, here 
are the patches (also attached). The one which absolutely needs fixing 
is image.py. The others are what I'm guessing needs to be done to clean 
up the slight messiness I found.
Gary R.
--- image.py	2006年04月07日 22:02:08.000000000 +1000
+++ new_image.py	2006年04月07日 23:02:36.000000000 +1000
@@ -422,7 +422,7 @@
 def draw(self, renderer, *args, **kwargs):
 if not self.get_visible(): return
 im = self.make_image()
- renderer.draw_image(self.ox, self.oy, im, self.origin, 
self.figure.bbox)
+ renderer.draw_image(self.ox, self.oy, im, self.figure.bbox)
 def write_png(self, fname):
 """Write the image to png file with fname"""
--- backend_emf.py	2006年04月07日 22:51:12.000000000 +1000
+++ new_backend_emf.py	2006年04月07日 23:18:02.000000000 +1000
@@ -179,15 +179,11 @@
 
self.emf.Arc(int(x-hw),int(self.height-(y-hh)),int(x+hw),int(self.height-(y+hh)),int(x+math.cos(angle1*math.pi/180.0)*hw),int(self.height-(y+math.sin(angle1*math.pi/180.0)*hh)),int(x+math.cos(angle2*math.pi/180.0)*hw),int(self.height-(y+math.sin(angle2*math.pi/180.0)*hh)))
- def draw_image(self, x, y, im, origin, bbox):
+ def draw_image(self, x, y, im, bbox):
 """
 Draw the Image instance into the current axes; x is the
 distance in pixels from the left hand side of the canvas. y is
- the distance from the origin. That is, if origin is upper, y
- is the distance from top. If origin is lower, y is the
- distance from bottom
-
- origin is 'upper' or 'lower'
+ the distance from the origin.
 bbox is a matplotlib.transforms.BBox instance for clipping, or
 None
--- backend_agg.py	2006年04月07日 22:51:38.000000000 +1000
+++ new_backend_agg.py	2006年04月07日 23:04:00.000000000 +1000
@@ -155,14 +155,14 @@
 gcEdge, rgbFace, x, y, width/2, height/2) # ellipse takes 
radius
- def _draw_image(self, x, y, im):
+ def _draw_image(self, x, y, im, bbox):
 """
 Draw the Image instance into the current axes; x, y is the
 upper left hand corner of the image
 """
 if __debug__: verbose.report('RendererAgg.draw_image', 
'debug-annoying')
 #self._renderer.draw_image(int(x), int(self.height-y), im)
- self._renderer.draw_image(int(x), int(y), im)
+ self._renderer.draw_image(int(x), int(y), im, bbox)
 def draw_line(self, gc, x1, y1, x2, y2):
 """
--- backend_agg2.py	2006年04月07日 22:56:56.000000000 +1000
+++ new_backend_agg2.py	2006年04月07日 23:04:20.000000000 +1000
@@ -90,7 +90,7 @@
 def draw_arc(self, gcEdge, rgbFace, x, y, width, height, angle1, 
angle2):
 pass
- def draw_image(self, x, y, im, origin, bbox):
+ def draw_image(self, x, y, im, bbox):
 pass
 def draw_line(self, gc, x1, y1, x2, y2):

John Hunter wrote:
>A colleague is trying to build an sdist from his svn repository.
>He doesn't have any of Numeric, numarray or numpy installed and gets
>
> % python setup.py sdist
> Traceback (most recent call last):
> File "setup.py", line 133, in <module>
> raise RuntimeError("You must install one or more of numpy,
> Numeric, and numarray to build matplotlib")
> RuntimeError: You must install one or more of numpy, Numeric, and
> numarray to build matplotlib
>
>
>We should not be checking for these dependencies when making a bdist
>or sdist. Does anyone know the right distutils calls to check for the
>command passed to setup.py, eg 'build', 'install', or 'sdist' ...?
> 
>
An alternative might be to have an appropriate MANIFEST.in file and a 
very simple setup_sdist.py file...

On Thursday 06 April 2006 17:47, Christopher Barker wrote:
> Darren Dale wrote:
> > On Wednesday 05 April 2006 18:42, Christopher Barker wrote:
> >> Why not have a TexTempDir attribute stored somewhere, and write
> >> everything there?
> >
> > That's exactly what I'm trying to do. Or maybe I dont understand what you
> > are suggesting.
>
> I'm confused about what "working directory" you're talking about. I
>
> thought you meant Python's working directory:
> >>> os.getcwd()
>
> However, if you mean a sub-process's working directory:
>
> os.system("cd temp; ls")
>
> Then I don't have a problem with that. It won't screw up anything else.
There's a thought. I'll have a look at it when I can, but I'm swamped at the 
moment. Maybe next week.

John Hunter wrote:
> A colleague is trying to build an sdist from his svn repository.
> He doesn't have any of Numeric, numarray or numpy installed and gets
> 
> % python setup.py sdist
> Traceback (most recent call last):
> File "setup.py", line 133, in <module>
> raise RuntimeError("You must install one or more of numpy,
> Numeric, and numarray to build matplotlib")
> RuntimeError: You must install one or more of numpy, Numeric, and
> numarray to build matplotlib
> 
> We should not be checking for these dependencies when making a bdist
> or sdist. 
Actually, I'm pretty sure we should be checking for them when making a bdist
since bdists require a build.
> Does anyone know the right distutils calls to check for the
> command passed to setup.py, eg 'build', 'install', or 'sdist' ...?
There aren't any reliable ways because the commands don't get processed until
setup() is called. The checks for numpy et al. happen specifically to determine
what information to pass to setup().
You could check sys.argv, but it would be at the expense of making everyone's
build processes very, very fragile. It probably wouldn't work very well, either.
-- 
Robert Kern
rob...@gm...
"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
 -- Umberto Eco

Darren Dale wrote:
> On Wednesday 05 April 2006 18:42, Christopher Barker wrote:
>> Why not have a TexTempDir attribute stored somewhere, and write
>> everything there?
> 
> That's exactly what I'm trying to do. Or maybe I dont understand what you are 
> suggesting.
I'm confused about what "working directory" you're talking about. I 
thought you meant Python's working directory:
 >>> os.getcwd()
However, if you mean a sub-process's working directory:
os.system("cd temp; ls")
Then I don't have a problem with that. It won't screw up anything else.
Could you use a standard temp directory instead? Maybe by using 
something from the tempfile module.
It would be nice if TeX/LaTeX gave you a way to specify directories to 
use, but I guess it doesn't, at least not consistently across systems.
Darn.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

A colleague is trying to build an sdist from his svn repository.
He doesn't have any of Numeric, numarray or numpy installed and gets
 % python setup.py sdist
 Traceback (most recent call last):
 File "setup.py", line 133, in <module>
 raise RuntimeError("You must install one or more of numpy,
 Numeric, and numarray to build matplotlib")
 RuntimeError: You must install one or more of numpy, Numeric, and
 numarray to build matplotlib
We should not be checking for these dependencies when making a bdist
or sdist. Does anyone know the right distutils calls to check for the
command passed to setup.py, eg 'build', 'install', or 'sdist' ...?
Thanks,
JDH

I encountered a type error for the following script:
from matplotlib import *
from pylab import *
colours =3D ['lemonchiffon', 'lightskyblue', 'indianred']
x =3D [170.804, 186.838, 217.725]
y =3D arange(3)+.5 # the bar centers on the y axis
barh(x,y, color=3Dcolours)
yticks(y, ('A', 'B', 'C'))
show()
 File "C:\Python24\Lib\site-packages\matplotlib\pylab.py", line 1661, in b=
arh
 ret =3D gca().barh(*args, **kwargs)
 File "C:\Python24\lib\site-packages\matplotlib\axes.py", line 1238, in ba=
rh
 if (is_string_like(color) or
TypeError: len() of unsized object
I added "and iterable(left)" before checking for len(left) to line
1238 in axes.py to make the error go away:
 if (is_string_like(color) or
 (iterable(color) and len(color)=3D=3D3 and iterable(left) and
len(left)!=3D3) or
 not iterable(color)):
 color =3D [color]*len(x)
Is there a better solution?

Jeff Whitaker wrote:
>> Andrew: OK, now I get it. I've implemented your suggestion, except 
>> that instead of adding a new parameter to Basemap.__init__, I've just 
>> skipped the processing of boundary data if the resolution keyword is 
>> set to None.
>
Thanks Jeff, this works great!

Andrew Straw wrote:
> Andrew Straw wrote:
>
> 
>> Anyhow, given that basemap comes with 82 MB
>> of Earth-specific data which I don't need all the time, I think it would
>> be really great if it would be possible to make the inclusion of such
>> data optional.
>>
>> 
> That wasn't particularly clear. What I meant to say was that when
> running basemap, it would be nice if the contents in the data path were
> optionally not loaded if the user knew she was not going to plot
> coastlines, etc. I have no problems with actually installing the data,
> although to be fair the reason I'd like this feature is so that I don't
> have to have a basemap data path at all.
> 
Andrew: OK, now I get it. I've implemented your suggestion, except 
that instead of adding a new parameter to Basemap.__init__, I've just 
skipped the processing of boundary data if the resolution keyword is set 
to None.
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-124
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

I do most of my programming with eric, which has some support for version 
control. But it looks like I have inadvertently added some unnecessary 
directories and files to the svn repository: trunk/matplotlib/trunk (and 
contents), trunk/matplotlib/tags and trunk/matplotlib/branches.
Any eric users out there that know how to prevent this from happening?
I suppose its ok to delete them from the repository, but I figured I should 
check for objections first.
Darren

>>>>> "Eric" == Eric Firing <ef...@ha...> writes:
 Eric> This doesn't sound right. What kind of tex build is ubuntu
 Eric> using? I thought just about everything now (including
 Eric> miktex) was based on tetex with kpathsea. I don't have an
 Eric> ubuntu handy to try, but a little googling shows that tetex
 Eric> is offered. Is it some sort of stripped-down version?
It doesn't look like I have it either on my ubuntu system
peds-pc311:~> uname -a
Linux peds-pc311 2.6.10-5-386 #1 Thu Aug 18 22:23:56 UTC 2005 i686
GNU/Linux
peds-pc311:~> latex --version
e-TeX (Web2C 7.4.5) 3.14159-2.1
kpathsea version 3.4.5
Copyright (C) 1997-2003 The NTS Team.
Kpathsea is copyright (C) 1997-2003 Free Software Foundation, Inc.
There is NO warranty. Redistribution of this software is
covered by the terms of both the e-TeX copyright and
the GNU General Public License.
For more information about these matters, see the files
named COPYING and the e-TeX source.
Primary author of e-TeX: The NTS Team.
Kpathsea written by Karl Berry and others.
peds-pc311:~> latex --help|grep directory
peds-pc311:~> 

I just installed whatever tetex option was shown in the package
manager. Here is what I've got:
ryan@ubuntu:~$ latex -v
e-TeX (Web2C 7.4.5) 3.14159-2.1
kpathsea version 3.4.5
Copyright (C) 1997-2003 The NTS Team.
Kpathsea is copyright (C) 1997-2003 Free Software Foundation, Inc.
There is NO warranty. Redistribution of this software is
covered by the terms of both the e-TeX copyright and
the GNU General Public License.
For more information about these matters, see the files
named COPYING and the e-TeX source.
Primary author of e-TeX: The NTS Team.
Kpathsea written by Karl Berry and others.
ryan@ubuntu:~$ latex --help
Usage: etex [OPTION]... [TEXNAME[.tex]] [COMMANDS]
 or: etex [OPTION]... \FIRST-LINE
 or: etex [OPTION]... &FMT ARGS
 Run e-TeX on TEXNAME, usually creating TEXNAME.dvi.
 Any remaining COMMANDS are processed as e-TeX input, after TEXNAME is rea=
d.
 If the first line of TEXNAME is %&FMT, and FMT is an existing .efmt file,
 use it. Else use `NAME.efmt', where NAME is the program invocation name,
 most commonly `etex'.
 Alternatively, if the first non-option argument begins with a backslash,
 interpret all non-option arguments as a line of e-TeX input.
 Alternatively, if the first non-option argument begins with a &, the
 next word is taken as the FMT to read, overriding all else. Any
 remaining arguments are processed as above.
 If no arguments or options are specified, prompt for input.
-efmt=3DFMTNAME use FMTNAME instead of program name or a %& line
-file-line-error-style print file:line:error style messages
-ini be einitex, for dumping formats; this is implicitl=
y
 true if the program name is `einitex'
-interaction=3DSTRING set interaction mode (STRING=3Dbatchmode/nonstop=
mode/
 scrollmode/errorstopmode)
-ipc send DVI output to a socket as well as the usual
 output file
-ipc-start as -ipc, and also start the server at the other en=
d
-jobname=3DSTRING set the job name to STRING
-kpathsea-debug=3DNUMBER set path searching debugging flags according to
 the bits of NUMBER
[-no]-mktex=3DFMT disable/enable mktexFMT generation (FMT=3Dtex/tf=
m)
-mltex enable MLTeX extensions such as \charsubdef
-output-comment=3DSTRING use STRING for DVI file comment instead of date
-parse-first-line parse of the first line of the input file
-progname=3DSTRING set program (and fmt) name to STRING
-recorder enable filename recorder
-shell-escape enable \write18{SHELL COMMAND}
-src-specials insert source specials into the DVI file
-src-specials=3DWHERE insert source specials in certain places of
 the DVI file. WHERE is a comma-separated value
 list: cr display hbox math par parend vbox
-translate-file=3DTCXNAME use the TCX file TCXNAME
-help display this help and exit
-version output version information and exit
Email bug reports to te...@ma....
Ryan
On 4/5/06, Eric Firing <ef...@ha...> wrote:
> Darren Dale wrote:
> > On Wednesday 05 April 2006 20:03, Ryan Krauss wrote:
> >
> >>I didn't know latex had this capability and I don't see it listed in
> >>the options if I type latex --help. (I am running Ubuntu). Is this
> >>something you only need on windows/miktex or should this option be
> >>cross-platform? I don't have output or aux directory options.
> >>
> >>ryan@ubuntu:~/thesis$ latex -output-directory=3D/home/ryan
> >>rwk_thesis_main.tex latex: unrecognized option
> >>`-output-directory=3D/home/ryan'
> >>Try `latex --help' for more information.
> >
> >
> > Yes, you're right. I guess this option is exclusive to miktek. Ok, so I=
'm back
> > to believing that there is no way to hide all the tex output files, I g=
uess
> > they will just have to temporarily exist in the current working directo=
ry.
> >
> > Damn is that ugly.
>
> This doesn't sound right. What kind of tex build is ubuntu using? I
> thought just about everything now (including miktex) was based on tetex
> with kpathsea. I don't have an ubuntu handy to try, but a little
> googling shows that tetex is offered. Is it some sort of stripped-down
> version?
>
> On Mandriva 2006:
>
> [efiring@manini examples]$ latex --help
> [snip]
> -output-directory=3DDIR use DIR as the directory to write files to
> [snip]
>
> Eric
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Darren Dale wrote:
> On Wednesday 05 April 2006 20:03, Ryan Krauss wrote:
> 
>>I didn't know latex had this capability and I don't see it listed in
>>the options if I type latex --help. (I am running Ubuntu). Is this
>>something you only need on windows/miktex or should this option be
>>cross-platform? I don't have output or aux directory options.
>>
>>ryan@ubuntu:~/thesis$ latex -output-directory=/home/ryan
>>rwk_thesis_main.tex latex: unrecognized option
>>`-output-directory=/home/ryan'
>>Try `latex --help' for more information.
> 
> 
> Yes, you're right. I guess this option is exclusive to miktek. Ok, so I'm back 
> to believing that there is no way to hide all the tex output files, I guess 
> they will just have to temporarily exist in the current working directory.
> 
> Damn is that ugly.
This doesn't sound right. What kind of tex build is ubuntu using? I 
thought just about everything now (including miktex) was based on tetex 
with kpathsea. I don't have an ubuntu handy to try, but a little 
googling shows that tetex is offered. Is it some sort of stripped-down 
version?
On Mandriva 2006:
[efiring@manini examples]$ latex --help
[snip]
-output-directory=DIR use DIR as the directory to write files to
[snip]
Eric

HI Andrew,
Thanks for clearing that up, and sorry for mis-reading your post.
FWIW, I don't keep up to date with the svn builds on Win32.
Anyway, thanks and sorry for butting in....
--Matt Newville

>>>>> "Darren" == Darren Dale <dd...@co...> writes:
 Darren> Yes, we currently do that. But if an error is raised
 Darren> before the cleanup can occur, then several files are left
 Darren> behind. If I happen to be viewing the contents of the
 Darren> current directory with a modern file manager, I see all
 Darren> these temporary files popping up and then disappearing. I
 Darren> guess there is nothing to be done about it.
Can you not try/except the errant code and perform the cleanup in the
except branch?
JDH

On Wednesday 05 April 2006 17:14, Andrew Straw wrote:
> John Hunter wrote:
> >>>>>>"Andrew" == Andrew Straw <str...@as...> writes:
> >
> > Andrew> Darren Dale wrote:
> > >> As soon as I know that matplotlib builds subprocess correctly
> > >> for windows computers with <python-2.4, I will unmask the
> > >> subprocess code again in svn. Any ideas when we might have an
> > >> answer to this question?
> >
> > Andrew> I suspect that there are relatively few Python 2.3 users
> > Andrew> on Windows anymore, so I say unmask it now. (It's not like
> > Andrew> the case in linux where big distros, e.g. Debian, are
> > Andrew> still on Python 2.3. Windows doesn't have "distros", and
> >
> >enthought python is only built for 2.3 currently, as far as I can see:
> >
> > http://code.enthought.com/enthon
> >
> >I think this is a pretty important constituency in the scientific
> >python crowd.
>
> OK, point taken.
>
> But still, given that I think I've fixed the bug, we should unmask it so
> we can see if I actually did.
Done. svn 2259.

On Wednesday 05 April 2006 20:39, you wrote:
> >>>>> "Darren" == Darren Dale <dd...@co...> writes:
>
> Darren> Yes, you're right. I guess this option is exclusive to
> Darren> miktek. Ok, so I'm back to believing that there is no way
> Darren> to hide all the tex output files, I guess they will just
> Darren> have to temporarily exist in the current working
> Darren> directory.
>
> Darren> Damn is that ugly.
>
>
> Can you not remove the temporary files that are not cached? Didn't we
> used to look for miles like PREFIX.log and PREFIX.aux and clean them
> up after each run?
Yes, we currently do that. But if an error is raised before the cleanup can 
occur, then several files are left behind. If I happen to be viewing the 
contents of the current directory with a modern file manager, I see all these 
temporary files popping up and then disappearing. I guess there is nothing to 
be done about it.

> 1) download MPL from svn
> 2) compile and install MPL with Python < 2.4
> 3) spend two days figuring out step 2
> 4) Give up and use linux
 5) Become so enthralled with your newfound power that you become a
 matplotlib developer
At least it worked for you :-)
JDH

>>>>> "Darren" == Darren Dale <dd...@co...> writes:
 Darren> Yes, you're right. I guess this option is exclusive to
 Darren> miktek. Ok, so I'm back to believing that there is no way
 Darren> to hide all the tex output files, I guess they will just
 Darren> have to temporarily exist in the current working
 Darren> directory.
 Darren> Damn is that ugly.
Can you not remove the temporary files that are not cached? Didn't we
used to look for miles like PREFIX.log and PREFIX.aux and clean them
up after each run?
JDH

On Wednesday 05 April 2006 20:03, Ryan Krauss wrote:
> I didn't know latex had this capability and I don't see it listed in
> the options if I type latex --help. (I am running Ubuntu). Is this
> something you only need on windows/miktex or should this option be
> cross-platform? I don't have output or aux directory options.
>
> ryan@ubuntu:~/thesis$ latex -output-directory=/home/ryan
> rwk_thesis_main.tex latex: unrecognized option
> `-output-directory=/home/ryan'
> Try `latex --help' for more information.
Yes, you're right. I guess this option is exclusive to miktek. Ok, so I'm back 
to believing that there is no way to hide all the tex output files, I guess 
they will just have to temporarily exist in the current working directory.
Damn is that ugly.

On Wednesday 05 April 2006 18:46, Darren Dale wrote:
> On Wednesday 05 April 2006 18:42, Christopher Barker wrote:
> > Darren Dale wrote:
> > > Is it ok to change the current directory to .matplotlib/tex.cache,
> > > generate the tex files, and then change back to the original working
> > > directory?
> >
> > I think it's bad practice: it sure seems fragile. I don't like my
> > software to change my working directory.
> >
> > Why not have a TexTempDir attribute stored somewhere, and write
> > everything there?
>
> That's exactly what I'm trying to do. Or maybe I dont understand what you
> are suggesting.
I've looked into this more than once before, but this time around I finally 
found a real solution:
latex -output-directory=C:\texoutput -aux-directory=C:\tobedeleted foo.tex
Ok, moving on.

Ryan Krauss wrote:
> My understanding is that once NumPy is considered "stable", Enthought
> will switch to Python 2.4.
We will be switching to Python 2.4 as soon as our new build machine arrives and
we've tested Enthon on it. That should be in about two weeks.
Including numpy is a separate issue and will occur later, probably next month.
-- 
Robert Kern
rob...@gm...
"I have come to believe that the whole world is an enigma, a harmless enigma
 that is made terrible by our own mad attempt to interpret it as though it had
 an underlying truth."
 -- Umberto Eco

On Wednesday 05 April 2006 18:42, Christopher Barker wrote:
> Darren Dale wrote:
> > Is it ok to change the current directory to .matplotlib/tex.cache,
> > generate the tex files, and then change back to the original working
> > directory?
>
> I think it's bad practice: it sure seems fragile. I don't like my
> software to change my working directory.
>
> Why not have a TexTempDir attribute stored somewhere, and write
> everything there?
That's exactly what I'm trying to do. Or maybe I dont understand what you are 
suggesting.

Darren Dale wrote:
> Is it ok to change the current directory to .matplotlib/tex.cache, generate 
> the tex files, and then change back to the original working directory?
I think it's bad practice: it sure seems fragile. I don't like my 
software to change my working directory.
Why not have a TexTempDir attribute stored somewhere, and write 
everything there?
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...