Thanks for that link to the web3py code, that looks much neater, but I guess not all the functionality is there yet which might help. It looks like the From initialisation and process methods skip the HTML generation completely and the various style_xxxxx methods create the HTML version as per the various needs, is that correct?
I guess web3py is in it's early stages yet, but from what I've read about it it looks like a good step forward. What is the expected timescale for web3py being ready for general use? I guess I shouldn't expect a stable release in the next year or so. What is the plan for getting to a stable release of web3py? Would it begin as a limited feature set compared to web2py and then get more complete over time or would it wait until it is more or less complete before it would be considered stable and ready for general use? As I am only just beginning to seriously use web2py I should probably be keeping an eye on web3py as I won't have much in the way of legacy systems to adapt. Also I probably don't use a very extensive range of web2py features at the moment either. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
