On Dec 14, 2006, at 5:47 PM, [EMAIL PROTECTED] wrote:
> > Just a little background about myself first... > > Hello, my name is Carlo. I have only joined this list and a new > Python/Pylons programmer. My experience has been mostly in UNIX > systems > programming in C/C++ and have recently landed myself a new job that > involves some Python development. I'm new to Pylons and web > applications in general so please bear with me. > No worries =] > Python isn't difficult to learn and I have been able to play around > with Pylons easily. But while I can make my own projects from > scratch I > am having some difficulties with a Pylons project that I took over. > First of all, the command "paster controller apg" doesn't seem to > work. > I reckon the project was made with an older version of Pylons so > creating controllers involves some other odd command. This is the > error > I get: > > $ paster controller apg > Command controller not known > You would see this if your current working directory wasn't a Pylons project, or if it lacked a .egg-info directory. The controller command is a plugin for paster: Pylons projects should have it automatically 'plugged in' via their .egg-info directories. That .egg- info dir is searched for in the current working dir and scanned when paster searches for its plugins. An incredibly old version of Pylons might also do this, but doubtful. -- 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
