Before I do it, you do know that there will be no folder
> heirarchy: e.g. fonts/ttf/*, images... All files will be
> in lib/matplotlib/mpl-data/. I honestly don't think
> there are terribly many files, so shouldn't be a huge
> deal.
Is this the only way to do it (no folder hierarchy?). If so, I don't
see it as a show stopper. But if it's possible, some form of
organization would be cleaner...
JDH
http://www.python.org/doc/current/dist/node11.html
From this my impression is that the package data files will be placed
in the same way they are in the package. I will look for a way to get
around this, and if anyone on the list knows how, please speak up. As
I said previously, my attempts to use "../../images/*" seemed not to
work.
On 12/14/05, John Hunter <jdhunter@...5...> wrote:
> Before I do it, you do know that there will be no folder
> heirarchy: e.g. fonts/ttf/*, images... All files will be
> in lib/matplotlib/mpl-data/. I honestly don't think
> there are terribly many files, so shouldn't be a huge
> deal.Is this the only way to do it (no folder hierarchy?). If so, I don't
see it as a show stopper. But if it's possible, some form of
organization would be cleaner...JDH
I missed the "New in version 2.4." note in the link I posted. With
this I would say the current state is probably worth keeping. Sorry
for the DoS attack of emails on the mailing list this morning. 
- Charlie
On 12/14/05, Charlie Moad <cwmoad@...149...> wrote:
http://www.python.org/doc/current/dist/node11.html
From this my impression is that the package data files will be placed
in the same way they are in the package. I will look for a way to get
around this, and if anyone on the list knows how, please speak up. As
I said previously, my attempts to use "../../images/*" seemed not to
work.On 12/14/05, John Hunter <jdhunter@...5...> wrote:
>
> > Before I do it, you do know that there will be no folder
> > heirarchy: e.g. fonts/ttf/*, images... All files will be
> > in lib/matplotlib/mpl-data/. I honestly don't think
> > there are terribly many files, so shouldn't be a huge
> > deal.
>
> Is this the only way to do it (no folder hierarchy?). If so, I don't
> see it as a show stopper. But if it's possible, some form of
> organization would be cleaner...
>
> JDH
>
Attached is a script which I wrote to make setup.py's more declarative and to make using setuptools/py2exe/etc from one file less of a pain. The important part is that it also backports "package_data" to Python 2.3, which could be ripped out and dropped into matplotlib's setup.py without too much trouble.
Ken
metasetup.py (14.1 KB)
On Dec 14, 2005, at 9:23 AM, Charlie Moad wrote:
I missed the "New in version 2.4." note in the link I posted. With
this I would say the current state is probably worth keeping.