Btw, the best approach would to specify the data as
> package-data (since that is what it is), and it would be
> the most compatible. Unfortunately my attempt to use
> parent directory relative paths failed. Taking this
> approach would actually require moving all the mpl data
> into the lib/matplotlib/mpl-data directory in cvs. I
> thought you might be opposed to that, hence I have the
> logic in the setup file.
I'm happy to do it in the cleanest and best way so feel free to
reorganize as necessary, as long as we continue to test on the various
platforms as you have been doing. You'll need to submit an admin
request to the sf developers to flush the unused CVS directories after
the reorganization.
JDH
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.
- Charlie
···
On 12/14/05, John Hunter <jdhunter@...5...> wrote:
> Btw, the best approach would to specify the data as
> package-data (since that is what it is), and it would be
> the most compatible. Unfortunately my attempt to use
> parent directory relative paths failed. Taking this
> approach would actually require moving all the mpl data
> into the lib/matplotlib/mpl-data directory in cvs. I
> thought you might be opposed to that, hence I have the
> logic in the setup file.
I'm happy to do it in the cleanest and best way so feel free to
reorganize as necessary, as long as we continue to test on the various
platforms as you have been doing. You'll need to submit an admin
request to the sf developers to flush the unused CVS directories after
the reorganization.
JDH