On Tue, Feb 26, 2013 at 4:45 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
Hi everyone,
We are about 5-6 packages away from porting ZTK to Python 3
That's awesome!
//Lennart
___
Zope-Dev maillist - Zope-Dev@zope.org
Hi,
On 2/26/13 5:04 PM, Hanno Schlichting wrote:
Hi.
The process for a ZTK 2.0 release isn't really well defined. I'm not
sure if Jan-Wijbrand and Christophe are still interested in working on
ZTK releases.
I'm personally and from a business-perspective still interested in the
ZTK and to
Hi,
On 2/26/13 7:26 PM, Hanno Schlichting wrote:
snip
Our rule for inclusion in the ZTK is: Whatever library is used by at
least two out of the three frameworks (BlueBream, Grok, Zope).
Given that BlueBream hasn't seen any release beyond a 1.0 about two
years back, I'm not sure it's active
On Tue, Feb 26, 2013 at 12:12 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
Is anyone here willing to start a buildbot using Python 3.3 to test the ZTK?
I created a buildbot (the 1.1 branch) two months ago[1]:
http://buildbot.afpy.org/ztk1.1dev/builders/Python3.3.0%20Linux%2064bit
Ready
On Wed, Feb 27, 2013 at 11:04:46AM -0500, Sebastien Douche wrote:
2. z3c.recipe.compattest and zc.recipe.testrunner doesn't work with Buildout
2.
The latter has been fixed in zc.recipe.testrunner 2.0.0.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Wed, Feb 27, 2013 at 5:04 PM, Sebastien Douche sdou...@gmail.com wrote:
2. z3c.recipe.compattest and zc.recipe.testrunner doesn't work with Buildout
2.
Both do now. You currently need z3c.recipe.compattest from trunk though.
I updated the ZTK trunk in the last days, and most of it should
Hi.
The process for a ZTK 2.0 release isn't really well defined. I'm not
sure if Jan-Wijbrand and Christophe are still interested in working on
ZTK releases.
Contrary to wait I said before I'd be willing to work on a ZTK 2.0
release (knowing the tools and procedure).
My goals for a 2.0 release
On Tuesday, February 26, 2013 05:04:26 PM Hanno Schlichting wrote:
Contrary to wait I said before I'd be willing to work on a ZTK 2.0
release (knowing the tools and procedure).
Could you outline what the first step would be to create an alpha release list
for 2.0? We could manually include an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2013 11:04 AM, Hanno Schlichting wrote:
My goals for a 2.0 release would be (comparing to
http://docs.zope.org/zopetoolkit/releases/overview-1.1.html):
- Drop support for Python 2.5 (ZTK 1.1 still supports that)
+1.
- Add support for
On Tue, Feb 26, 2013 at 6:12 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
Could you outline what the first step would be to create an alpha release list
for 2.0? We could manually include an sdist of the ZODB 4 py3 branch to make
the tests pass under Python 3.
I'll have to look at the
10 matches
Mail list logo
