Re: paster shell not available
I ran into the same problem... Make sure there's a file called paster_plugins.txt inside your egg_info directory with, at least, the following lines: After re-creating paster_plugins.txt, what is recommended?: (a) adding the entire egg_info dir into source control... or (b) just adding paster_plugins.txt? Thanks, Aaaron --~--~-~--~~~---~--~~ 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: paster shell not available
On 5/16/07, Alberto Valverde [EMAIL PROTECTED] wrote: $ paster shell development.ini Command shell not known Make sure there's a file called paster_plugins.txt inside your egg_info directory with, at least, the following lines: Pylons PasteScript That was it, thanks! On a related note, how can I extend paster controller command to use different templates? Max. --~--~-~--~~~---~--~~ 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: paster shell not available
On May 17, 2007, at 1:29 PM, Max Ischenko wrote: On 5/16/07, Alberto Valverde [EMAIL PROTECTED] wrote: $ paster shell development.ini Command shell not known Make sure there's a file called paster_plugins.txt inside your egg_info directory with, at least, the following lines: Pylons PasteScript That was it, thanks! On a related note, how can I extend paster controller command to use different templates? Hmm, not sure since I've never done it... If you want some ideas... I would begin looking up the code at pylons.commands:ControllerCommand (where the controller paste.paster_command entry point points to), copy it in my project (or some utilities egg), add the corresponding entry point to the egg's setup.py (with an alternate name) and add the egg's name at paster_plugins.txt of the app I want the command available at. Once the new command emulates Pylons' I would start tweaking the template to suit my needs. Hope it helps, Alberto --~--~-~--~~~---~--~~ 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: paster shell not available
On May 16, 2007, at 11:09 AM, Max Ischenko wrote: Here is the question: where is paster shell command hooked in? When I attempt to use paster shell in my current project I got this: $ paster shell development.ini Command shell not known Known commands: Newly created Pylons projects have this functionality working so I guess I need to upgrade something in my existing project to get this command. Make sure there's a file called paster_plugins.txt inside your egg_info directory with, at least, the following lines: Pylons PasteScript Alberto --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
