On 02/12/2013 08:58 AM, Marius Gedminas wrote:
On Tue, Feb 12, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
Non-OK results
--
[1]FAILED winbot / zope.security_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072239.html
Bootstrap failed:
On Tue, Feb 12, 2013 at 09:15:22AM +0100, Adam GROSZER wrote:
On 02/12/2013 08:58 AM, Marius Gedminas wrote:
I'd update the boostrap, if I could figure out where in svn is the thing
called ztk_1_1. Buildbot makes it unreasonably hard to figure this
stuff out (this is why I publish the
On 02/11/2013 03:36 PM, Stephan Richter wrote:
Hi Tres (and everyone else reading along),
as you are probably aware, zope.security is a package that blocks a
lot of other packages from being ported. I just checked out the
coverage on Github and it looks like you are making good
On Mon, Feb 04, 2013 at 09:59:37PM +0200, Marius Gedminas wrote:
You need:
- svn-all-fast-export (from the Debian/Ubuntu package of the same name;
upstream homepage is http://gitorious.org/svn2git, not related to a
Ruby tool of the same name)
- a copy of the Subversion repository
On Tue, Feb 12, 2013 at 12:35 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
Hi Jim,
can you give me access to zc.lockfile, so I can upload a new release?
PyPI id?
Jim
--
Jim Fulton
http://www.linkedin.com/in/jimfulton
Jerky is better than bacon! http://zo.pe/Kqm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/12/2013 12:23 PM, GitHub wrote:
Branch: refs/heads/master Home:
https://github.com/zopefoundation/zope.security Commit:
390d1258382d5473388fb6d2fc80f392d4991cf8
On Tue, Feb 12, 2013 at 3:35 PM, Stephan Richter
stephan.rich...@gmail.com wrote:
On Tuesday, February 12, 2013 01:29:43 PM Jim Fulton wrote:
can you give me access to zc.lockfile, so I can upload a new release?
PyPI id?
srichter
Done.
Jim
--
Jim Fulton
At one point, we had a style guide that recommended simple import
module import
statements for Zope code:
http://wiki.zope.org/zope3/ZopePythonStyleGuide
Today, I'm noticing a lot of commits with the change note Normalize
imports that
change all imports to from module import whatever, like
This is the summary for test reports received on the
zope-tests list between 2013-02-11 00:00:00 UTC and 2013-02-12 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:
On Tue, Feb 12, 2013 at 05:20:14PM -0500, Fred Drake wrote:
At one point, we had a style guide that recommended simple import
module import statements for Zope code:
http://wiki.zope.org/zope3/ZopePythonStyleGuide
That page only mentions 'from whatever import *' which everyone will
agree
10 matches
Mail list logo