>> For the second issue, I have added 'pytrainer.upgrade' to the list of >> packages in setup.py. I am not sure if this is enough to entirely fix >> this problem. > > It seems enough at least for installing sources and executing pytrainer ;) > >> Can you explain how you setup Pytrainer as a Python Egg >> so I can test this? > > Basically it should be an standard way to distribute python based > software regardless target platforms. The idea behind it is widely > explained at http://docs.python.org/library/distutils.html. >
I ran "python setup.py install --prefix=~" and then tried launching pytrainer from ~/bin. This did not work because the migrate repository could not be found. This was due to two problems: the migrate repository was missing from setup.py and at runtime it was being loaded from the working directory instead of the python path. I suspect you did not experience this issue because your working directory was the pytrainer source when you executed pytrainer built from distutils. In revision 829 I have committed a fix for these two issues so the data migration should work for a properly installed pytrainer. Some thorough testing would be appreciated. - Nathan ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
