Fearing second-system-syndrome, I'd vote to continue the legacy interface & just port to python3 (perhaps building off current webpy/python3 branch), and not try to have same code (i.e., same branch) run under both python2 & python3.
There are likely some python3-isms which will cause a small predictable API change: It would not be a new framework, but would allow migration to python3. Then, perhaps, a cleaned-up webpy+ can be designed. My motivation is: a) I know and use webpy, it's simple. b) I want to move up to python3 I don't have an immediate project which requires python3, but I've been using python since the v1.5 days, and figure it's time to move up. -Peter -- 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.
