I think it can be the same repository, but that's an implementation matter. By "Single source base" I mean single branch.
I may not have my terms correct, so I'll elaborate: One strategy, which I believe is the current strategy, is to use and improve the Master branch such that it can be used by python2 & python3. The source contains helpers/conditional code so that any differences between python2 and python3 are managed. Patches / enhancements going forward are pulled to the single branch and tested against python2 & 3. The other strategy is to (logically) fork the code: whether that is different repository (i.e, *really* fork the code), or simply different branch is based on overall deployment and maintenance issues. The result is patches and enhancements are pulled into python2 or python3 independently, and tested only against python2 or python3. One would expect that (hope that...) new development would be on python3 and eventually, the feature set between webpy and webpy3 would diverge. I see there is a python3 branch, with lots of pull requests from warmwaver, but no further action. His (her?) changes appear to support only python3 which may be why Anand hasn't pulled them into main. In any case, the effort seems to have stalled and I'd like to move forward. -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/webpy. For more options, visit https://groups.google.com/d/optout.
