On Mon, Oct 15, 2012 at 9:34 AM, sk78 <[email protected]> wrote: > Thanks for your reply. > Yes, I had already generated the test-0.1dev-py2.6.egg file by typing sudo > python setup.py bdist_egg and then copied the generated egg file from the > project/dist/ folder to the other computer where I want to deploy. I had > installed easy_install on the computer. But when I tried: sudo easy_install > test-0.1dev-py2.6.egg I got the error message I mentioned. > Do I need to copy anything else other than the egg file onto the deployment > computer to make it work? > Many thanks again.
Using the "bdist_egg" to install is usually going to be problematic. The reason for this is that the egg is built in a binary mode. This means that if, for any reason, the remote system is unable use the egg (different Python version, for one example), easy_install will try to find the egg of PyPI. Since your egg doesn't exist there yet, it fails. The better solution, in my opinion, is to use "python setup.py sdist" which will build a source .tar.gz file which is portable across environments. That will result in something you can safely install on the remote site. -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
