Am 19.09.2012 18:13, schrieb NoRaGen: > It would be nice to have the option to upgrade to a python3.x Version > of Webware for later purpose.
Definitely, that has also been one of my goals for a new version. > Compatiblity should be given so, that API remains the same, but > using python3.x capability. This should be possible, I think. API > changes would very bad at all. The problem here is that Webware development started even before Python 2, so the old API is very old-fashioned concerning naming conventions, use of getters and setters etc. My idea was to add a tool like py2to3 that can convert an old style Webware app to a new style app. Another idea would be to allow both styles. E.g. request could become a property, but if you call the request object, then it returns self, so if you use request as a getter function, it would still work. We already discussed this in the past. Method names could be changed from camelCase to PEP8 style, but the old names could be kept as aliases. > However we use many modules where still no python3 port is existing. > For now, switching to higher python version, would still not > effective for us. Yes, e.g. ReportLab is still one of the roadblockers. -- Chris ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
