On Jan 26, 12:23 am, Noah Kantrowitz <[EMAIL PROTECTED]> wrote: > > Can you elaborate on this point? What kind of problems have you > > encountered with namespace packages? > > Anyone accidently putting code in the __init__.py in the namespace > folder (or anything else at level) may be confused at first if they > don't read up on how the namespace system works. Ditto for if the > forget to call the declare_namespace() function. For someone not used > to working Python, which is the case for many new plugin developers, > this all might be a bit much.
Well, I've been thinking it'd be nice to work on a nice "quickstart" tool for plugins, probably based on the PasteScript package generator. This could put a big warning in the namespace __init__.py that it should not be edited. I don't think people need to fully understand the workings of namespacing here as long as they have a good starting point. However, if the namespace stuff is still controversial we could put that aside temporarilly, but I'd like to see the setuptools stuff merged soon[1]. So, are there any other issues that need resolved before this is merged? -- Matt Good [1] for ticket #4382 I'd like to use simplejson to handle the encoding of Python datastructures to JavaScript, so I'd like to add it as a setuptools requirement --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
