Re: Packaging and development workflow for decoupled apps.

2011-03-11 Thread Tom Evans
On Fri, Mar 11, 2011 at 3:52 PM, DaleB wrote: > I guess i wasn't clear enough. I am not so much concerned with when to > use tags and when to use branches. > I am still looking for a smooth development workflow. > I created a libs-dir which i put on my python path an put my different > apps in it.

Re: Packaging and development workflow for decoupled apps.

2011-03-11 Thread Bill Freeman
On Fri, Mar 11, 2011 at 3:41 AM, DaleB wrote: > One last point. > Now, how do i deal best with different versions/branches of my app? Do > you just switch branches while developing or do you use pip in project > env to refer and switch to different tags/branches in your sourcecode. > The first ap

Re: Packaging and development workflow for decoupled apps.

2011-03-11 Thread Mike Ramirez
On Friday, March 11, 2011 07:52:22 am DaleB wrote: > I guess i wasn't clear enough. I am not so much concerned with when to > use tags and when to use branches. > I am still looking for a smooth development workflow. > I created a libs-dir which i put on my python path an put my different > apps in

Re: Packaging and development workflow for decoupled apps.

2011-03-11 Thread DaleB
I guess i wasn't clear enough. I am not so much concerned with when to use tags and when to use branches. I am still looking for a smooth development workflow. I created a libs-dir which i put on my python path an put my different apps in it. Okay, now i can refer to my apps from any project withou

Re: Packaging and development workflow for decoupled apps.

2011-03-11 Thread Mike Ramirez
On Friday, March 11, 2011 12:41:52 am DaleB wrote: > One last point. > Now, how do i deal best with different versions/branches of my app? Do > you just switch branches while developing or do you use pip in project > env to refer and switch to different tags/branches in your sourcecode. > The firs

Re: Packaging and development workflow for decoupled apps.

2011-03-11 Thread DaleB
Thank you for all your insights. > I think you are stuck in the monolithic point of view.  I'm also not sure if > you understand that django apps are python modules and the same rules apply.   > > The apps location within the PYTHONPATH is immaterial to a project, as long as > the project can find

Re: Packaging and development workflow for decoupled apps.

2011-03-10 Thread Tom Evans
On Thu, Mar 10, 2011 at 5:57 PM, DaleB wrote: > Hi all, > > i could use some advice for a good packaging workflow. > > So far i used to put an "apps"-folder in my project root and i stored > all individual apps in a sub-folder. > This works, but i thought: "Okay, try to decouple things a bit more

Re: Packaging and development workflow for decoupled apps.

2011-03-10 Thread Mike Ramirez
On Thursday, March 10, 2011 09:57:29 am DaleB wrote: > I see that this is really great for the distribution of an app. > But what about development and "continuous packaging"? > I mean, my project consists of more than five apps. One side of me > would rather turn them all into installable package

Re: Packaging and development workflow for decoupled apps.

2011-03-10 Thread Bill Freeman
On Thu, Mar 10, 2011 at 12:57 PM, DaleB wrote: > Hi all, > > i could use some advice for a good packaging workflow. > > So far i used to put an "apps"-folder in my project root and i stored > all individual apps in a sub-folder. > This works, but i thought: "Okay, try to decouple things a bit more

Packaging and development workflow for decoupled apps.

2011-03-10 Thread DaleB
Hi all, i could use some advice for a good packaging workflow. So far i used to put an "apps"-folder in my project root and i stored all individual apps in a sub-folder. This works, but i thought: "Okay, try to decouple things a bit more and try to create some 'real' reusable apps." So i followe