Hi folks, I'm running tg1 with python 2.6 and noticed that cherrypy 2.3.0 splits out some deprecation warnings that are specific to python 2.6 and did not happen with python versions < 2.6. These are all md5/sha related and are easy to fix.
I wrote to both the cherrypy-users and cherrypy-devel lists suggesting that I would be more than happy to supply patches against cherrypy 2.3.0 that would fix these deprecation warnings, but got absolutely no reply. Which brings me to my real question: what is the tg 1 devel team's plan for handling abandoned core components (such as cherrpy 2.x)? Should these projects be forked and should they start living in svn.turbogears.org and be part of tg 1? I'd think this is the only way, if indeed cherrpy 2.x (or other tg 1 core component) is abandonware, since it would be a shame if tg 1 as a stack would be stuck just because some almost trivial fixes can not be applied to a code base beyond the tg 1 team's control. Another example where moving abandoned core components into tg 1 proper would be a good idea is python 3 compatibility. My impression is that there is absolutely no way of getting the cherrypy team to port 2.3.0 to python 3 (I might be wrong). Forking and moving it to tg 1 proper would facilitate this porting, I think. For example I would be happy to help with this effort. Any ideas? Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
