You could do all your work in a virtual environment, but I like to set PYTHONPATH to point to the top of the repo instead. Then Python will find Leo in the repo but all other python packages from their usual places. On my Windows machine:
> > set PYTHONPATH=d:\tom\git\leo-editor > python3 -m leo.core.runLeo > > One advantage of doing it this way is that you can run the ordinary Leo > release simply by unsetting PYTHONPATH. You don't have to try to remember > which venv has got which configuration, or how to get the venv to use the > repo. > > I've learned that it's best to make a new branch for each of your change > projects, no matter how small. Once the PR is closed, you can update from > Leo's *devel* and again branch off it for your next effort, or merge your > branch back into your clone of *devel*. > > Of course, you may be way more experienced at doing the PR dance and if so > just keep doing whatever you have been doing! > Thanks for the python path tips - it’s been about 15 years since developed with python professionally. As far as the PR dance goes, that is pretty much my everyday dance at work ;) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/6f18d6ae-1ae9-4dd2-b8d1-03209428e0bbn%40googlegroups.com.
