search

damonwang / xraylarch

X-ray Analysis Applications with Larch and Python
http://cars.uchicago.edu/ifeffit/Larch
1 stars 0 forks source link

no easy way to import a dev copy of larch #7

Closed damonwang closed 14 years ago

damonwang commented 14 years ago

the executable script that runs a CLI interpreter is called larch, so the source is in a directory called lib, which means to get the dev copy you need to import lib instead of import larch. This is bad because we'll have to change the import statements every time we package a new release up for production.

damonwang commented 14 years ago

moved things around so that the working copy could be used as the source for imports. Now if you put the working copy's path into PYTHONPATH env. variable, calling "import larch" will get you the working copy instead of the site-wide production copy. Closed by 786d55e06e6f1a429d519e1f3ce81c9fcd9742d2.