On Sep 7, 3:08 pm, Graham Higgins <[EMAIL PROTECTED]> wrote: > On Sep 5, 11:55 am, Bartosz R <[EMAIL PROTECTED]> wrote: > > > I found a little correction in the section about adding commands to > > paster:http://docs.pylonshq.com/advanced_pylons/paster_commands.html > > > it says: > > > >Modify the entry_points argument in setup.py to contain: > > > >[paste.paster_command] > > >my-command = myapp.commands.my_command:MyCommand > > The accompanying text in the document sets a context: "Create a module > myapp/commands/my_command.py" > > In this context, the module path listed in the Pylons docs is correct: > > ++ my-command = myapp.commands.my_command:MyCommand
As stated before, it is not that the text doesn't match the filesystem - the commands dir in myapp overrides the builtin commands module from pylons. It should be given some other name than commands (like local_commands). And of course it should also be changed in setup.py. Anyway, thanks for the replies. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
