Charlie Moad wrote:
>> Well, another option is to maintain a sub-directory structure when
>> creating mpl-data in the source package. The downside is that this will
>> introduce code changes all over the code -- for example, code that
>> previously asked for "os.path.join( mpl.get_data_dir(), 'blah.glade' )"
>> would have to be converted to "os.path.join( mpl.get_data_dir(), 'gui',
>> 'blah.glade' )".
> 
> I think we should maintain a clean tree and make the code changes.  I
> bet it would only take one person a diligent hour or two to fix all
> the occurrences as mentioned above.  Maybe we could split up the work?
>  I would be willing to update the "backends" folder.

Although my understanding of setup* is minimal, I agree; I think that 
keeping some organization in the data will be helpful.  It looks like 
get_data_path() is not called in many places, so if that is essentially 
what has to be fixed, it should not be very difficult.  It might be 
facilitated by making _get_data_path() accept *args, a set of 
subdirectories to be appended.

Eric


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to