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 it.
> Okay, now i can refer to my apps from any project without copying the
> files. Great and a lot better than before.
>
> So now i start to create different branches for an app, i create a
> development branch an change stuff.
> As the app is on my path my projects initially refer to the state/
> branch of an app that ist currently checked out, right?
> That's what i refered to by "switching branches" (= changing the
> branch of my app in my libs-dir)
>
> Another (better?) idea i had looking at pip's docs was to take my libs-
> dir off the python path, put them in a git-repo and use pip to install
> my app.
> Pip's option to refer to certain tags and branches (http://
> pip.openplans.org/requirement-format.html#version-control) seems
> pretty ideal in this situation.
> The only drawback i see is that i have to install and uninstall quite
> often if i want to test different branches/states of my app in a
> project.
>
> And now i am not sure which route is more promising or if there's even
> an easier way i don't regard at the moment.
> Hope that's more clear.
>
> Thanks fpr you patience,
> Andreas
In this case, I'm sorry, I'm not sure. I don't use pip, given the arguments
I've seen for it, I've never had a reason to really investigate it myself.
Setuputils/distribute/easy_install are 'good enough' for me. A long time ago
james bennet posted a big why you want to use pip on this list, I can't
remember much more about it, but you might want to search for that posting.
I do things manually with checkouts. If I want to work on a branch, this is
checked out to a new location (since it's a radical change/fork of a project),
i.e. same lib dir, different package name to let me know it's a branch. Tags
are there for historical reasons, really I just use them to mark completion
points and they are considered part of the main tree (usually). It's just
easier to know how far back to go when searching for a revision that
introduced a bug (usually). Or if I completely messed up the current branch, I
can just go get the last tag.
Mike.
--
mixed emotions:
Watching your mother-in-law back off a cliff...
in your brand new Mercedes.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
