Re: [PyX-devel] Re: Some comments on PyX

[Andre W. <wo...@us...>]

Jörg,

On 16.10.03, Joerg Lehmann wrote:
> I'm not sure about that. Of course, at the moment an "import pyx"
> doesn't do anything (expect providing access to pyx.__version__ and
> pyx.__all__) and using the code given above it would at least do
> something reasonable. On the other hand, the behaviour seems to
> be rather implicit than explicit to me. So, as I said, I don't know.

Well, same for me. Should we play dice now?

> > 2) I have to address the share/data_files search path issue.
> 
> Maybe also something for a pyxrc?

That's actually a good idea. By that we could even get rid of the
developer search path (this third path possibility explained in my
previous mail). I kind of like the idea. In principle we might be even
able to use libkpathsea ... it's probably possible to feed it with
some additional path search types we read from our configuration and
use that. But on the other hand we already do have some working code
except that we should feed it with some input from pyxrc. And
libkpathsea is not neccessarily linked as a module.

BTW: Have you ever done a /etc/<xxx>rc and ~/.<xxx>rc file before
(e.g. in pytone)? How about the distribution of that via distutils?


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us...
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/