On May 6, 5:47 pm, "Edward K. Ream" <[email protected]> wrote: > On Thu, May 6, 2010 at 9:39 AM, zpcspm <[email protected]> wrote: > > Not sure I understand what do you mean here by "inconvenient". > > If you are concerned about having to: > > > 1. commit to local branch py2.x and push changes to launchpad > > 2. sync local branch py3.x by pulling from launchpad > > > then I'm not sure this is mandatory. > > > Since bzr is distributed, one is supposed to be able to sync py3.x > > directly from py2.x locally. In terms of speed that'll be fast. > > However, I would have to remember to do the sync :-)
Oh, now I see what do you mean and I agree this is a problem :-) Automating sync is a double-edged sword, because it might spare you from performing the sync manually, but it would also complicate your workflow, because you'll eventually have to deal additionally with sync logic if it happens to fail. Having only one repo and just using 'bzr export' for making different copies of VCS-free source code to run them with python 2.x/3.x is not better. This approach would only transpose the problem instead of solving it. You might also want to ask on StackOverflow, it's a crowded place visited by some guys who are known in the Python community. The nearest related thing I could find there was http://stackoverflow.com/questions/471928/way-to-have-compiled-python-files-in-a-separate-folder but it has a negative answer, thus it's not valuable as well. -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
