Re: App authoring: setup

2012-07-11 Thread Demian Brecht
Perhaps I wasn't clear.. When I mentioned installing, I meant installing the Django app in a virtualenv through a setup script so that the project has visibility to it (not installing the example project itself). Was just curious if there was another method I was unaware of is all really. Thanks

Re: App authoring: setup

2012-07-11 Thread Russell Keith-Magee
On Thu, Jul 12, 2012 at 9:00 AM, Demian Brecht wrote: > Only a couple small problems with that: > > * No sample code for people utilizing the app in their own projects Really? You can't do what every other popular Django app on github does, and put an examples directory in your repository that is

Re: App authoring: setup

2012-07-11 Thread Demian Brecht
Only a couple small problems with that: * No sample code for people utilizing the app in their own projects * Unit testing environment is a little more unorthodox to set up - rather than just using the example project's settings (and manage.py test app_name), I'd have to do the configuration manua

Re: App authoring: setup

2012-07-11 Thread Russell Keith-Magee
On Wed, Jul 11, 2012 at 10:39 PM, Demian Brecht wrote: > Hi all, > > Is there a preferred method to create an app such that the app is the focal > point and not the project? The app root is SCM root and it intended to be > published on PyPI. I see one of two way to go about this: > > First method

App authoring: setup

2012-07-11 Thread Demian Brecht
Hi all, Is there a preferred method to create an app such that the app is the focal point and not the project? The app root is SCM root and it intended to be published on PyPI. I see one of two way to go about this: First method (my preferred): * Create an app at the root level of a project, us