Currently Zope has two rules for object ids: 1) they must be str instances, and
2) they must only consist of alphanumerics and a few extra characters. I have
been playing around recently with trying to relax those rules to allow more
flexible object ids, specifically allowing UTF-8 object ids.
On Wed, Feb 20, 2013 at 09:57:52AM +0100, Wichert Akkerman wrote:
I want to propose that we do the following:
Allow arbitrary str object ids in Zope 4 based on Dieter's work.
Configure standard name choosers, normalizers, etc. used to generate
ids for content to create UTF-8 object ids.
On Wed, Feb 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2013-02-18 00:00:00 UTC and 2013-02-19 00:00:00 UTC:
I finally got tired of clicking at the links by hand and wrote a script:
On Wed, Feb 20, 2013 at 04:48:56PM +0200, Marius Gedminas wrote:
On Wed, Feb 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
[10] FAILED winbot / zope.deprecation_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-February/072621.html
Moved to github,
On Feb 20, 2013, at 15:48 , Marius Gedminas mar...@gedmin.as wrote:
On Wed, Feb 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2013-02-18 00:00:00 UTC and 2013-02-19 00:00:00 UTC:
I finally got tired
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2013 09:48 AM, Marius Gedminas wrote:
[5]FAILED Still Failing - zopetoolkit_trunk - Build # 178
https://mail.zope.org/pipermail/zope-tests/2013-February/072600.html
Error: Picked: BTrees = 4.0.5
So now zope.annotation requires
This is the summary for test reports received on the
zope-tests list between 2013-02-19 00:00:00 UTC and 2013-02-20 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 Thu, Feb 21, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2013-02-19 00:00:00 UTC and 2013-02-20 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the
Hi,
I've tried
from ZPublisher.Iterators import filestream_iterator
return filestream_iterator('/home/chrism/bigfile.xls', 'r')
in a method to return a big file to users; however, it doesn't work, are
there alternative ways to serve large files to users, serving files that
are lying somewhere
