-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2013 11:33 AM, GitHub wrote:
Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy!
Woohoo! Nice work. BTW, how did you break the import cycle due to the
zope.location monkeypatch?
Tres.
- --
On Monday, March 11, 2013 11:56:10 AM Tres Seaver wrote:
Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy!
Woohoo! Nice work. BTW, how did you break the import cycle due to the
zope.location monkeypatch?
I moved the patch to __init__.py. I know, not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2013 02:02 PM, Stephan Richter wrote:
On Monday, March 11, 2013 11:56:10 AM Tres Seaver wrote:
Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy!
Woohoo! Nice work. BTW, how did you break the import cycle due to
the
Hi everyone,
Fred asked about the reasoning behind recent version numbers as we ported
packages to Python 3.
We decided that any package that depends on an alpha or unreleased package
should itself be an alpha release. There are 2 packages that started the
avalanche:
* zope.security: Tres
This is the summary for test reports received on the
zope-tests list between 2013-03-10 00:00:00 UTC and 2013-03-11 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2013 08:40 PM, Stephan Richter wrote:
Fred asked about the reasoning behind recent version numbers as we
ported packages to Python 3.
We decided that any package that depends on an alpha or unreleased
package should itself be an alpha
On Monday, March 11, 2013 02:00:55 PM Tres Seaver wrote:
BTW, I merged the branch to the trunk and made a zope.security 4.0.0b1
release just now.
Yep, saw that. There are some uncovered lines for which I have to add tests
left. Also, I just noticed while prorting zope.publisher to PyPy that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2013 10:29 PM, Stephan Richter wrote:
On Monday, March 11, 2013 02:00:55 PM Tres Seaver wrote:
BTW, I merged the branch to the trunk and made a zope.security
4.0.0b1 release just now.
Yep, saw that. There are some uncovered lines for
Hello Tres,
Thanks for the reply.
On Sun, 2013-03-10 at 23:32 -0400, Tres Seaver wrote:
Method names are not stored in the ZODB at all: only the instance
attributes are stored.
Apologies. I've reported it wrong. I was not able to reproduce the
problem after a fresh start.
--
Joshua
