On May 6, 5:25 pm, "Edward K. Ream" <[email protected]> wrote: > On Thu, May 6, 2010 at 9:21 AM, zpcspm <[email protected]> wrote: > > On May 6, 5:11 pm, "Edward K. Ream" <[email protected]> wrote: > >> On Windows 7, at least, switching back and forth between Python 3.1 > >> and 2.6 is quite slow, presumably because all .pyc or .pyo files must > >> be regenerated for all the .py files in the leo directory and > >> subdirectories. I doubt there is much remedy for this. > > > Why not running two source code trees? > > Not a bad idea--I hadn't thought of that. Otoh, I would have to > commit from one branch and update the other branch whenever I made a > change that had to be tested on both platforms. That would likely be > even more inconvenient than regenerating bytecode. > > EKR
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. -- 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.
