Guido van Rossum <guido@python.org> writes: > Otherwise you could set up your own SF project "pythonce" and do a > vendor branch checkin of Python. I've never used vendor branches > myself, but Kurt Kaiser uses them in the idlefork CVS, which deals > with a similar issue. I would recommend this strategy. Supposedly, you will rarely need to perform imports from PythonLabs Python: the CE changes should be largely independent of how PythonLabs Python develops. Imports might be needed only when a chunk of your changes is accepted into CVS Python. You don't need a separate SF project, perhaps: A CVS module on the python project might be sufficient. We can ask SF to remove the tree when/if CE incorporation is complete. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4