On Thu, Dec 20, 2012 at 05:13:37PM +0200, Marius Gedminas wrote:
On Wed, Dec 19, 2012 at 02:42:35PM -0500, Tres Seaver wrote:
On 12/19/2012 01:57 PM, Marius Gedminas wrote:
Would it be possible to release zope.security 4.0.0 any time soonish? Then new buildouts would get new zope.proxy and new zope.security, while old buildouts would happily continue to use old ones.
I had hoped that the 4.0.0 marker would signal Py3k compatibilty, but don't have gumption to finish that port today.
Whoops. I think I accidentally stepped on your toes by releasing zope.pagetemplate 4.0.0 without first checking if the Py3k port was complete. I just assumed it was, after noticing the 4.0.0 version number in CHANGES.txt.
I added a tox.ini and 'setup.py test' support to zope.pagetemplate trunk and saw that Py3k porting is blocked by zope.security not working with Py3k yet. No pressure ;-)
Maybe a 3.9.0 release, made by branching from 3.8.3 and just bumping the zope.proxy dependency?
That sounds reasonable.
Call that a +0.5 vote, because I don't trust my judgment. Marius Gedminas -- Software programmers should not think that they have to write multi-threaded programs. It's too hard, and the payoff is too little. And it absolutely isn't where the industry is even going. -- Linus Torvalds