Hi all,
I've been running a test-setup using ZPublisher/WSGIPublisher.py
mongrel2 -> wsgid -> zope2
I'm running into some minor, some larger issues. Most importantly,
transactions are not committed. You know better than I do what that
means. For me, I can't create Plone sites, or even DTMLDocuments. And
when I create then using ZServer, I can't delete them any more through
the wsgi route.
I have a small patch against WSGIPublisher.py (branch 2.13) that fixes
above behaviour (attached).
After applying it creating and deleting content works ok, but when using
the sunburst theme, the created site looks completely unstyled, whereas
using the classic plone theme everything looks much better.
The plot thickens however because when I enable debug-mode, everything
works great!
Maybe someone with better understanding of the mechanics involved now
has an epiphany.
FYI, I'm using the following buildout:
https://github.com/pjstevns/plone.mongrel2
thanks.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/info@nfg.nl/+31.85.877.99.97
________________________________________________________________
Hi,
I created a patch for a package zope.intid that almost completely
solves the problem with the zope.keyreference.interfaces.NotYet
exception.
I implemented a deferred indexing of objects added to the container
which is not connected to the ZODB.
As soon as the container is added to the ZODB - all deferred objects
will be indexed.
I also added a marker IIntIdsDisabled for marking objects that must
not be indexed.
I would be grateful if someone could look at my changes and merge them
into the main branch.
My fork of zope.intid - https://bitbucket.org/cykooz/zope.intid/src
PS: Sorry for my English.
-------------------
Cykooz (Kirill Kuzminykh)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/14/2012 08:13 AM, Michael Howitz wrote:
> Log message for revision 125861: In version 3.7.2 msgids and default
> values where forced to be unicodes. This was too strict because at
> least the TAL extractor returns UTF-8 encoded default values. Fixed
> this by allowing the default value to be a string again.
<snip>
> --- zope.app.locales/trunk/src/zope/app/locales/extract.py 2012-05-14
> 08:50:08 UTC (rev 125860) +++
> zope.app.locales/trunk/src/zope/app/locales/extract.py 2012-05-14
> 12:13:47 UTC (rev 125861) @@ -97,7 +97,7 @@ msgstr "" <BLANKLINE>
>
> - Unicode can be used in msgids and default values + Unicode can
> be used in msgids and default values:
>
>>>> entry = POTEntry(Message(u"\u263B", default=u"\u253A"))
>>>> entry.write(FakeFile())
> @@ -106,6 +106,16 @@ msgstr "" <BLANKLINE>
>
> + But msgid might be an ascii encoded string and `default` might be
> a + string with the DEFAULT_ENCODING, too: + + >>> entry =
> POTEntry(Message("Oe", default="\xd6")) + >>>
> entry.write(FakeFile()) + #. Default: "\326" + msgid "Oe" +
> msgstr "" + <BLANKLINE> + """
Hmm, I'm running into a test failure where the Message constructor blows
up with a decode error for the 'default' value here. Does that ring any
bells for anyone? I know we can't be depending on a
sys.setdefaultencoding hack.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/t6b4ACgkQ+gerLs4ltQ4OAwCeK2Cm+Xm/OLy+adZGfOkQx/hk
CakAoLQFXbtqQU9Jlm1ZfgtD58RwJ7wE
=kFK2
-----END PGP SIGNATURE-----
This is the summary for test reports received on the
zope-tests list between 2012-06-25 00:00:00 UTC and 2012-06-26 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:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
Zope 3.4 Known Good Set / py2.4-32bit-linux
Zope 3.4 Known Good Set / py2.4-64bit-linux
Zope 3.4 Known Good Set / py2.5-32bit-linux
Zope 3.4 Known Good Set / py2.5-64bit-linux
Zope-2.10 Python-2.4.6 : Linux
Zope-2.11 Python-2.4.6 : Linux
Zope-2.12 Python-2.6.8 : Linux
Zope-2.13 Python-2.6.8 : Linux
Zope-2.13 Python-2.7.3 : Linux
Zope-trunk Python-2.6.8 : Linux
Zope-trunk Python-2.7.3 : Linux
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_254_win32
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64
Non-OK results
--------------
This is the summary for test reports received on the
zope-tests list between 2012-06-28 00:00:00 UTC and 2012-06-29 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:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
Zope 3.4 Known Good Set / py2.4-32bit-linux
Zope 3.4 Known Good Set / py2.4-64bit-linux
Zope 3.4 Known Good Set / py2.5-32bit-linux
Zope 3.4 Known Good Set / py2.5-64bit-linux
Zope-2.10 Python-2.4.6 : Linux
Zope-2.11 Python-2.4.6 : Linux
Zope-2.12 Python-2.6.8 : Linux
Zope-2.13 Python-2.6.8 : Linux
Zope-2.13 Python-2.7.3 : Linux
Zope-trunk Python-2.6.8 : Linux
Zope-trunk Python-2.7.3 : Linux
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
[1] winbot / zope.app.container_py_265_32
winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_254_win32
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64
Non-OK results
--------------
[1] FAILED winbot / zope.app.container_py_265_32
https://mail.zope.org/pipermail/zope-tests/2012-June/064902.html
This is the summary for test reports received on the
zope-tests list between 2012-06-27 00:00:00 UTC and 2012-06-28 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:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
Zope 3.4 Known Good Set / py2.4-32bit-linux
Zope 3.4 Known Good Set / py2.4-64bit-linux
Zope 3.4 Known Good Set / py2.5-32bit-linux
Zope 3.4 Known Good Set / py2.5-64bit-linux
Zope-2.10 Python-2.4.6 : Linux
Zope-2.11 Python-2.4.6 : Linux
Zope-2.12 Python-2.6.8 : Linux
Zope-2.13 Python-2.6.8 : Linux
Zope-2.13 Python-2.7.3 : Linux
Zope-trunk Python-2.6.8 : Linux
Zope-trunk Python-2.7.3 : Linux
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_254_win32
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64
Non-OK results
--------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've done with the porting / test cleanup effort on this branch:
svn+ssh://svn.zope.org/repos/main/zope.component/tseaver-test_cleanup
Highlights of the changes in this branch, targeting a 4.0 release:
- - Added PyPy and Python 3.2 support (tested by tox):
- Security support omitted until ``zope.security`` ported.
- Persistent registry support omitted until ``ZODB`` / ``persistent``
ported.
- - 100% unit test coverage.
- - Removed the long-deprecated ``layer`` argument to the
``zope.component.zcml.view`` and ``zope.component.zcml.resource``
ZCML directives.
- - Added support for continuous integration using ``tox`` and ``jenkins``.
- - Got tests to run using ``setup.py test``.
- - Added ``Sphinx`` documentation (converting existing doctests to both
narrative and API docs).
- - Added ``setup.py docs`` alias (installs ``Sphinx`` and dependencies).
- - Added ``setup.py dev`` alias (runs ``setup.py develop`` plus installs
``nose`` and ``coverage``).
Unless there are strong objections, I plan to merge this to the trunk
this week, and make a 4.0.0 release.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/rg1oACgkQ+gerLs4ltQ55XQCghkhOvOG4TkNYPSAetaWbkisd
jMkAoNtNatyp+XMg4gU2d+tjkE1OSZX8
=HrsS
-----END PGP SIGNATURE-----
This is the summary for test reports received on the
zope-tests list between 2012-06-26 00:00:00 UTC and 2012-06-27 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:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
Zope 3.4 Known Good Set / py2.4-32bit-linux
Zope 3.4 Known Good Set / py2.4-64bit-linux
Zope 3.4 Known Good Set / py2.5-32bit-linux
Zope 3.4 Known Good Set / py2.5-64bit-linux
Zope-2.10 Python-2.4.6 : Linux
Zope-2.11 Python-2.4.6 : Linux
Zope-2.12 Python-2.6.8 : Linux
Zope-2.13 Python-2.6.8 : Linux
Zope-2.13 Python-2.7.3 : Linux
Zope-trunk Python-2.6.8 : Linux
Zope-trunk Python-2.7.3 : Linux
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_254_win32
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64
Non-OK results
--------------
This is the summary for test reports received on the
zope-tests list between 2012-06-24 00:00:00 UTC and 2012-06-25 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:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds
Reports received
----------------
Zope 3.4 Known Good Set / py2.4-32bit-linux
Zope 3.4 Known Good Set / py2.4-64bit-linux
Zope 3.4 Known Good Set / py2.5-32bit-linux
Zope 3.4 Known Good Set / py2.5-64bit-linux
Zope-2.10 Python-2.4.6 : Linux
Zope-2.11 Python-2.4.6 : Linux
Zope-2.12 Python-2.6.8 : Linux
Zope-2.13 Python-2.6.8 : Linux
Zope-2.13 Python-2.7.3 : Linux
Zope-trunk Python-2.6.8 : Linux
Zope-trunk Python-2.7.3 : Linux
winbot / ZODB_dev py_265_win32
winbot / ZODB_dev py_265_win64
winbot / ZODB_dev py_270_win32
winbot / ZODB_dev py_270_win64
winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_254_win32
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64
Non-OK results
--------------