Re: egg-info
On Nov 27, 2007, at 5:00 PM, Mike Orr wrote: Is it necessary to put the egg-info directory in version control? Every time i run python setup.py develop it updates those files, which I have to keep checking in. Are they necessary for a production system given that python setup.py develop seems to recreate them fine if they're missing? The production ini template currently resides in the .egg-info directory, and it needs to be versioned controlled. This is sucky: the template should just reside in the root directory of the project, so folks don't have to worry about revision controlling the egg-info dir. IIRC PasteScript hardcodes the template location there. There's also a paster_plugins.txt in there that can break things if it's not maintained. But this is really a bug (of a different nature) -- the file belongs there, but rerunning setup.py egg_info should recreate it. There's an open ticket about it: http://pylonshq.com/project/pylonshq/ticket/282 -- Philip Jenvey --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: egg-info
On Nov 29, 2007, at 3:41 PM, Philip Jenvey wrote: This is sucky: the template should just reside in the root directory of the project, so folks don't have to worry about revision controlling the egg-info dir. IIRC PasteScript hardcodes the template location there. Oh, but of course the problem with having the production template in the root directory is running paster setup-app project on an installed project wouldn't have the template on hand -- it needs to be installed along with the project. Hmm.. -- Philip Jenvey --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
Re: egg-info
On Nov 29, 2007 10:16 PM, Philip Jenvey [EMAIL PROTECTED] wrote: On Nov 29, 2007, at 3:41 PM, Philip Jenvey wrote: This is sucky: the template should just reside in the root directory of the project, so folks don't have to worry about revision controlling the egg-info dir. IIRC PasteScript hardcodes the template location there. Oh, but of course the problem with having the production template in the root directory is running paster setup-app project on an installed project wouldn't have the template on hand -- it needs to be installed along with the project. Hmm.. All these issues are what make me question the wisdom of installing apps as eggs and using paster setup-app at all. Just copy development.ini to production.ini and make any necessary changes (you do want to version control production.ini, right?), copy the application directory to the server, run python setup.py develop, dump/restore your databases and empty them if necessary, and you're done. No need to install a zipped egg into site-packages and then wonder where to put your .ini file and data directory. No need to write a setup-app script that prepares the environment for *one* before-and-after scenario that may not quite fit the current situation, especially if you have existing data or are modifying the database. You had to create the database long ago to build the application, right? So why recreate it when you can just copy a database that works? No need to run make-config and merge all your custom settings from development.ini. Just copy it and change the debug variable and email address. Installing Python apps as eggs makes sense if you're distributing a public egg or managing a large server farm, but what percentage of Python applications will ever be deployed this way anyway? -- Mike Orr [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
egg-info
Is it necessary to put the egg-info directory in version control? Every time i run python setup.py develop it updates those files, which I have to keep checking in. Are they necessary for a production system given that python setup.py develop seems to recreate them fine if they're missing? -- Mike Orr [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups pylons-discuss group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~--~~~~--~~--~--~---
