Re: [Zope-dev] how to help Martijn (how can we have better discussions?)
Martin Aspeli wrote: Martijn Faassen wrote: Instead, we had endless debates about whether it was a legitimate concern for the ZTK maintainers. I'm of course still right that it is. I have wonderful and coherent reasons to support my position just like everybody else does who disagrees with me. It's not really very important anyway. We're here together on this list to work together beyond the ZTK itself. I think one problem is that we speak about abstract groups of people, the ZTK maintainers, or the Zope 3 maintainers and now The ZopeApp maintainers. These groups don't really exist in any cultural sense. They don't have an identity in the same way that, say, the Plone maintainers or the Grok maintainers (and possibly, the Zope 2 maintainers) do. It's hard for any one group to make their voice heard when no-one knows if they're part of that group or not. :) Agreed that this is a problem, though it's hard to find a balance here. It's useful to speak of roles that are a bit more abstract than me and my apps. So, in that sense Zope 3 maintainers is a useful concept instead of just mentioning, say, me, and Marius and others who have to deal with Zope 3 applications on various occasions. It's also useful to speak about such groups if you want to actually change the focus of energy in this community. That's where the idea of ZTK maintainers come from. It's a convenient way to say: we are going to care about zope.app. stuff less together, and focus on something else. But in the end this mailing list is just the community of people who talk and work together here, no matter what roles they have. I think in general, it's more useful to talk about the Zope community until such time that these groups actually self-organise, if indeed they ever do. You still need to be able to talk about groups with various concerns. We do have some organizational structure in place for ZTK, for instance. That was one of the points: having a decision making infrastructure at all. I know we have had a lot of problems reaching conclusions in such discussions in the past, but we can't learn how to do better at that if we don't. And we are going to do better if I can help it. I think we normally do reach conclusions, thanks often to people like you tirelessly summarising and soliciting input. I don't think that part is broken. Big discussion threads usually mean people are either passionate about or highly dependent on Zope as a framework, or both. I'd take that over apathy any day. We definitely have problems. It takes a lot of energy, too much, to get bigger changes through. A bit of a slow-down for big changes isn't necessarily a bad thing, but all too often it makes people feel they have to work around zope-dev and just do things somewhere else (or anyway). In the past, we frequently blocked on issues that just never reached a conclusion because nobody was there to say yes go ahead at the right time. We also regularly forgot conclusions. We've improved somewhat over the course of the last year, but we need to improve a lot further in my opinion. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] patterns for using sphinx with the Zope Toolkit?
On Mon, Jan 4, 2010 at 00:43, Chris McDonough chr...@plope.com wrote: Yeah. I haven't thought about this much, so it might be bollocks, but I think something like this is what I'm after: .. code-block-setup:: ... .. code-block:: python :linenos: .. code-block-teardown:: del sys.modules['models'] You don't actually have a test in that example. Here is my usecases: Numero Uno1 Here I call a method that will print things to the stdout. I need to make sure that it prints the correct thing, but I do not want that thing to be shown in the document. .. testsetup:: import sys sys.argv = ['setup.py', 'build'] .. testcode:: from setuptools import setup, find_packages setup(name='Porting to Python 3 examples', version=1.0, ) .. testoutput:: :hide: running build ... writing manifest file 'Porting_to_Python_3_examples.egg-info/SOURCES.txt' Numero Due Here I call a method that will raise an error. I need to make sure that it raises the correct thing, but I do not want that thing to be shown in the document. .. testsetup:: import sys sys.argv = ['setup.py', 'build'] .. testcode:: from setuptools import setup, find_packages setup(name='Porting to Python 3 examples', version=1.0, ) .. testoutput:: :hide: Traceback (most recent call last): SystemExit: False Trinity = Here I need a from __future__ import, but I want to use the format, because I *do* want to show the result. .. doctest:: from __future__ import division 5/2 2.5 It is of no great importance what the blocks are called, as long as Sphinx recognizes them as code blocks and indents them the same (I don't know Sphinx rules there). I do prefer having a separate setup and teardown (although I don't use that one currently) before just using invisible code blocks as I find it clearer, even though I realize it's just different names for the same thing, really. I'll not that none of the above works with Manuels latest release. Uno et Due works with trunk because I added Sphinx support yesterday (which should have been added to a branch, but I guess I got a temporary attack of Plone Collective disease), and Trinity I have working because I made a custom extension to Manuel where I override the standard doctest support and use a parser that is hacked to special case __future__ imports. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] windows newslines in doctests
Benji York wrote: Manuel uses Python's doctest module for the actual work, but the file reading is done by Manuel itself. I could switch to using universal new line mode, but since I haven't seen an example of a filing test I can't be sure if it'll help or not. Easy way to test: - create a doctest file on linux - run unix2dos on it - try runnng the test Or, better yet, in Manuel's tests, have a file with svn:eol-style *not* set and make sure it has Windows line endings... or even manually write such a file as part of the Manuel tests... cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sun Jan 3 12:00:00 2010 UTC to Mon Jan 4 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jan 3 20:37:53 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013317.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jan 3 20:39:53 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013318.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 3 20:41:53 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013319.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 3 20:43:53 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013320.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 3 20:45:53 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013321.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 3 20:47:53 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013322.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] upload zope.app.exception to pypi
hello, Would any of the pypi owners of zope.app.exception be so kind to upload the 3.6.0 release to the package index? I see this package has been tagged already a while ago. I think this newer version should also be included in the ZTK versions list, as this version will import the correct ISystemErrorView interface from zope.browser. Thank you in advance. kind regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] upload zope.app.exception to pypi
On Mon, Jan 4, 2010 at 6:32 PM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: hello, Would any of the pypi owners of zope.app.exception be so kind to upload the 3.6.0 release to the package index? I see this package has been tagged already a while ago. I think this newer version should also be included in the ZTK versions list, as this version will import the correct ISystemErrorView interface from zope.browser. I have added jw as owner of this package. BTW, I am getting this error from 3.6.0 branch.: $ ./bin/test /opt/baiju/wa/z3hello/eggs/zope.testing-3.8.6-py2.6.egg/zope/testing/testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Test-module import failures: Module: zope.app.exception.browser.tests.test_unauthorized Traceback (most recent call last): File /tmp/zope.app.exception/src/zope/app/exception/browser/tests/test_unauthorized.py, line 20, in module import zope.app.pagetemplate.namedtemplate File /opt/baiju/wa/z3hello/eggs/zope.app.pagetemplate-3.10.0-py2.6.egg/zope/app/pagetemplate/namedtemplate.py, line 20, in module from zope.browerpage.namedtemplate import implementation ImportError: No module named browerpage.namedtemplate Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] upload zope.app.exception to pypi
Baiju M mba...@zeomega.com wrote: On Mon, Jan 4, 2010 at 6:32 PM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: Would any of the pypi owners of zope.app.exception be so kind to upload the 3.6.0 release to the package index? I see this package has been tagged already a while ago. I think this newer version should also be included in the ZTK versions list, as this version will import the correct ISystemErrorView interface from zope.browser. I have added jw as owner of this package. Ok, thank you. BTW, I am getting this error from 3.6.0 branch.: Me too. $ ./bin/test /opt/baiju/wa/z3hello/eggs/zope.testing-3.8.6-py2.6.egg/zope/testing/ testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Test-module import failures: Module: zope.app.exception.browser.tests.test_unauthorized Traceback (most recent call last): File /tmp/zope.app.exception/src/zope/app/exception/browser/tests/ test_unauthorized.py, line 20, in module import zope.app.pagetemplate.namedtemplate File /opt/baiju/wa/z3hello/eggs/zope.app.pagetemplate-3.10.0-py2.6.egg/ zope/app/pagetemplate/namedtemplate.py, line 20, in module from zope.browerpage.namedtemplate import implementation ImportError: No module named browerpage.namedtemplate As it turns out, since the release of zope.app.exception 3.6.0 namedtemplate has again been moved. It is now in zope.browserpage. However, zope.browserpage is not required yet by zope.app.exception. I'll make it require zope.browserpage and release (and upload!) zope.app.exception 3.7.0. Would that be OK? regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] release and upload zope.app.pagetemplate to pypi
hello, Would any of the owners of zope.app.pagetemplate be so kind to upload (or let me upload) a new version of zope.app.pagetemplate? This will allow me to fix and release zope.app.exception. regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] release and upload zope.app.pagetemplate to pypi
On Mon, Jan 4, 2010 at 7:32 PM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: hello, Would any of the owners of zope.app.pagetemplate be so kind to upload (or let me upload) a new version of zope.app.pagetemplate? Added jw as owner. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] upload zope.app.exception to pypi
Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: Baiju M mba...@zeomega.com wrote: $ ./bin/test /opt/baiju/wa/z3hello/eggs/zope.testing-3.8.6-py2.6.egg/zope/testing/ testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Test-module import failures: Module: zope.app.exception.browser.tests.test_unauthorized Traceback (most recent call last): File /tmp/zope.app.exception/src/zope/app/exception/browser/tests/ test_unauthorized.py, line 20, in module import zope.app.pagetemplate.namedtemplate File /opt/baiju/wa/z3hello/eggs/zope.app.pagetemplate-3.10.0-py2.6.egg/ zope/app/pagetemplate/namedtemplate.py, line 20, in module from zope.browerpage.namedtemplate import implementation ImportError: No module named browerpage.namedtemplate As it turns out, since the release of zope.app.exception 3.6.0 namedtemplate has again been moved. It is now in zope.browserpage. However, zope.browserpage is not required yet by zope.app.exception. This has been fixed now, but now I'm stumped at this error: 16:17 jw:~/project/grokdev/z.a.exception $ ./bin/test /home/jw/project/grokdev/z.a.exception/eggs/zope.testing-3.8.6-py2.5.egg/zope/ testing/testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest Running zope.app.exception.testing.AppExceptionLayer tests: Set up zope.app.exception.testing.AppExceptionLayer Traceback (most recent call last): File /home/jw/project/grokdev/z.a.exception/eggs/zope.testing-3.8.6- py2.5.egg/zope/testing/testrunner/runner.py, line 367, in run_layer setup_layer(options, layer, setup_layers) File /home/jw/project/grokdev/z.a.exception/eggs/zope.testing-3.8.6- py2.5.egg/zope/testing/testrunner/runner.py, line 632, in setup_layer layer.setUp() File /home/jw/project/grokdev/z.a.exception/eggs/zope.app.testing-3.7.3- py2.5.egg/zope/app/testing/functional.py, line 337, in setUp self.config_file, product_config=self.product_config) File /home/jw/project/grokdev/z.a.exception/eggs/zope.app.testing-3.7.3- py2.5.egg/zope/app/testing/functional.py, line 226, in __init__ setup.setUpManager() File /home/jw/project/grokdev/z.a.exception/eggs/ zope.app.securitypolicy-3.5.1-py2.5.egg/zope/app/securitypolicy/browser/tests/ functional.py, line 26, in setUpManager functional.HTTPCaller()(grant_request, handle_errors=False) File /home/jw/project/grokdev/z.a.exception/eggs/zope.app.testing-3.7.3- py2.5.egg/zope/app/testing/functional.py, line 743, in __call__ request = publish(request, handle_errors=handle_errors) File /home/jw/project/grokdev/z.a.exception/eggs/zope.publisher-3.12.0- py2.5.egg/zope/publisher/publish.py, line 131, in publish obj = request.traverse(obj) File /home/jw/project/grokdev/z.a.exception/eggs/zope.publisher-3.12.0- py2.5.egg/zope/publisher/browser.py, line 556, in traverse ob, add_steps = publication.getDefaultTraversal(self, ob) File /home/jw/project/grokdev/z.a.exception/eggs/zope.app.publication-3.10.0- py2.5.egg/zope/app/publication/browser.py, line 36, in getDefaultTraversal return ob.browserDefault(request) Unauthorized: (zope.browserpage.simpleviewclass.SimpleViewClass from /home/jw/ project/grokdev/z.a.exception/eggs/zope.app.securitypolicy-3.5.1-py2.5.egg/zope/ app/securitypolicy/browser/granting.pt object at 0xa6e6f8c, 'browserDefault', 'zope.Security') I'm trying to figure out what has changed that could be related to this, but if anyone has a hint for me... regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] release and upload zope.app.pagetemplate to pypi
Baiju M mba...@zeomega.com wrote: On Mon, Jan 4, 2010 at 7:32 PM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: hello, Would any of the owners of zope.app.pagetemplate be so kind to upload (or let me upload) a new version of zope.app.pagetemplate? Added jw as owner. Thank you. 3.10.1 has been released and uploaded. regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Announce] BlueBream: Script to setup a Zope project directory
On Mon, Jan 4, 2010 at 9:01 PM, Stephan Richter srich...@cosmos.phy.tufts.edu wrote: On Sunday 03 January 2010, Baiju M wrote: I started a project named BlueBream to create a script to setup a Zope project directory. BlueBream use ZTK with some additional packages. BlueBream is based on PasteScript's template plugin. Thanks! This is a great first step for the new Zope 3, as you mentioned. With MArtijn's work on the ZTK and the zopeapp extension, I think we we will be soon able to do new reborn Zope 3 projects and releases. Thanks for the encouraging words. We have more things to do. As the next step, I will move the project from sandbox to main area. Also I will try to setup a compatibility test environment using z3c.recipe.compattest recipe. I hope we will be able make a migration path from Zope 3.4 ZTK to the new released packages. The most important thing will be documentation. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] broken zope.publisher because of new content types in zope.contenttype
On Sat, Jan 2, 2010 at 5:17 AM, Roger d...@projekt01.ch wrote:
Hi all
Since aaron added new mimetypes e.g. application/javascript,
the _implicitResult method in zope.publisher.http.py (line 794)
is broken because the method checks for text/* content types
if unicode is given:
def _implicitResult(self, body):
encoding = getCharsetUsingRequest(self._request) or 'utf-8'
content_type = self.getHeader('content-type')
if isinstance(body, unicode):
try:
if not content_type.startswith('text/'):
raise ValueError(
'Unicode results must have a text content type.')
except AttributeError:
raise ValueError(
'Unicode results must have a text content type.')
I changed the mime-type for .js from application/x-javascript to
application/javascript. Since I didn't change any text/* mime-types,
I'm not seeing how my change could be breaking anything that wasn't
already broken. The tests for zope.publisher run fine for me with my
changes, anyway. Can you tell how to reproduce the breakage?
Sould we remove this basic content type check above?
Or enhance the check with the new added unicode valid
content types like application/javascript.
Since whatever code is breaking for you now probably was breaking
before (since it was passing in application/x-javascript, which is
also not a text/* type), I'm inclined to think that your problem is at
a higher level.
btw, the RFC is just Informational which defines
this changes. See: http://www.rfc-editor.org/rfc/rfc4329.txt
According to the link above, the status of the following are:
text/javascript obsolete
application/x-javascript discouraged
application/javascript intended for common use, should be used
Aaron Lehmann
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] patterns for using sphinx with the Zope Toolkit?
Benji York wrote:
On Sun, Jan 3, 2010 at 6:43 PM, Chris McDonough chr...@plope.com wrote:
Yeah. I haven't thought about this much, so it might be bollocks, but I
think something like this is what I'm after:
.. code-block-setup::
import sys
from somepackage.testing import DummyModule
sys.modules['models'] = DummyModule()
.. code-block:: python
:linenos:
from models import MyModel
from repoze.bfg.view import bfg_view
from repoze.bfg.chameleon_zpt import render_template_to_response
@bfg_view(name='my_view', request_method='POST', context=MyModel,
permission='read')
def my_view(request):
return {'a':1}
.. code-block-teardown::
del sys.modules['models']
Only the code-block would show up. Actually being a code-block would be
helpful, too, so we could use the other features of code-blocks, like line
numbers. Or something.
If you replace .. code-block-setup:: and .. code-block-teardown::
with .. invisible-code-block:: python you can do that with Manuel now
(http://packages.python.org/manuel/#invisible-code-blocks).
Nice. I'll give that a try.
- C
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Announce] BlueBream: Script to setup a Zope project directory
On Mon, Jan 4, 2010 at 10:36 PM, Baiju M mba...@zeomega.com wrote: I hope we will be able make a migration path from Zope 3.4 ZTK to the new released packages. Err. I mean Zope 3.4 KGS Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] how to help Martijn (how can we have better discussions?)
Martijn Faassen wrote: [snip] So how can we have better discussions? We can have better discussions by helping me. How can you help me? Of course it helps if you agree with me. I realize that's frequently infeasible, but I certainly wouldn't mind. :) If you disagree with me, I'd like you to try to understand my concerns as much as you possibly can. In addition, try acknowledge my concerns as much as you possibly can without feeling you're lying. This works beter than just rejecting them. Chris McDonough pointed out to me that I didn't help in that discussion by not making my own individual concerns clear. I contributed to the problem by talking about abstract responsibilities instead of focusing on concrete needs of myself and people I know about. So: I actually *need* the zope.app information (and a well-tested zope.app) in transitioning applications (in Zope 3 or Grok) I work on the ZTK. As a Grok developer I also need that info to help transition Grok and Grok users to the ZTK. This way we can port Grok and our applications to ZTK and zope.app.* first, and then when the tests run, slowly change the imports to strip away zope.app.* dependencies. Like what we did with the ZTK itself, in fact. I'd like to share the burden of maintaining zope.app* with others. I hope those of you who want to improve the ZTK also will help in making sure zope.app.* doesn't suddenly break. I wasn't very successful in explaining all that before, so perhaps it's clearer in the personal. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] upload zope.app.exception to pypi
Martijn Faassen wrote: It seems to be occurring somewhere in the setup of the test layer, but strangely enough the publisher kicks in somewhere. I'm curious why the ZTK tests didn't catch this issue (or now the zopeapp tests). Hm, the zopeapp tests are catching this today. They weren't catching it last week. I think something broke in the mean time. I'm getting these problems across a lot of zope.app.* packages now, not just zope.app.exception. I updated the ZTK a few times with changes Hanno made to the Zope 2 fork. Perhaps I neglected to run the zopeapp tests. That's not a good sign for the future. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] New Zope 3 name: BlueBream
Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. But the package named bluebream will not provide any part of framework code by itself. All the framework code will be in zope and zope.app namespaces. BTW, the original meaning of BlueBream is same as that of Zope: http://en.wikipedia.org/wiki/Abramis_ballerus Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] upload zope.app.exception to pypi
Martijn Faassen faas...@startifact.com wrote: Jan-Wijbrand Kolman wrote: I'm trying to figure out what has changed that could be related to this, but if anyone has a hint for me... I can definitely reproduce the error. It seems to be occurring somewhere in the setup of the test layer, but strangely enough the publisher kicks in somewhere. I'm curious why the ZTK tests didn't catch this issue (or now the zopeapp tests). The publisher kicks in because when the layer is setup, the mgr user is granted the necessary permissions. This is done TTW using HTTPCaller(). In the request string that is passed to it, the basic auth credentials for globalmgr:globalmgrpw are passed in. This however seems not to work (anymore), where, looking at the history of this setup code, it had been working for a very long time. It must be something small and simple I guess, but it is needles and haystacks for me at this point... regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
Strong +1 from me (although my vote is likely not meaningful) Baiju M wrote: Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. But the package named bluebream will not provide any part of framework code by itself. All the framework code will be in zope and zope.app namespaces. BTW, the original meaning of BlueBream is same as that of Zope: http://en.wikipedia.org/wiki/Abramis_ballerus Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04.01.10 19:23, Baiju M wrote: Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. Coming from marketing I strongly suggest to think twice or better thrice before inventing the next new name in Zope world. There are already too many of them. juh -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktCPqIACgkQPUzUEFbILMQ6ugCeMdNHrABMNOCtIY8YM+Z+9c9e AsUAoOB/BVIaPxQFLiVZAV3wJQXSL823 =tcYv -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
Jan Ulrich Hasecke wrote: On 04.01.10 19:23, Baiju M wrote: Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. Coming from marketing I strongly suggest to think twice or better thrice before inventing the next new name in Zope world. There are already too many of them. Well, the name Zope 3 is effectively dead, yet there are still a number of developers who want to work on it and improve it. Those developers need to rename and regroup. BlueBream is a clever name and I think it's a great idea. Once it's released, BlueBream will probably be on my short list of preferred platforms. Shane ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
On Mon, Jan 4, 2010 at 21:44, Shane Hathaway sh...@hathawaymix.org wrote: Well, the name Zope 3 is effectively dead, yet there are still a number of developers who want to work on it and improve it. Those developers need to rename and regroup. BlueBream is a clever name and I think it's a great idea. Once it's released, BlueBream will probably be on my short list of preferred platforms. I agree completely. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shane Hathaway wrote: Jan Ulrich Hasecke wrote: On 04.01.10 19:23, Baiju M wrote: Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. Coming from marketing I strongly suggest to think twice or better thrice before inventing the next new name in Zope world. There are already too many of them. Well, the name Zope 3 is effectively dead, yet there are still a number of developers who want to work on it and improve it. Those developers need to rename and regroup. BlueBream is a clever name and I think it's a great idea. Once it's released, BlueBream will probably be on my short list of preferred platforms. +1 It would also allow us to stamp out the Zope 3 name, which continues to be confusing to newcomers (Zope 3 must be the replacement for Zope 2). jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAktCWswACgkQRAx5nvEhZLIiUACfaTtd4uhnRgJ25o3nVFY1QShp AmQAn3SsRTS8kGFDL/wgdYkPhkHrLcwM =ktcE -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.publisher 3.12 broke 25 zope.app packages
Hi there, 25 zope.app packages are broken due to changes in zope.publisher 3.12. zope.publisher had some components factored out of it into zope.login. I fixed zope.app.exception: it could be fixed by adding the zope.login requirement and adding a zcml include statement. I suspect most, probably all, other failures are similarly shallow. The breaking of so many packages wasn't noticed by anyone, until tests of svn checkouts that previously worked now broke. I hope we can put mechanisms in place so that developers of ZTK packages can be better made aware of breaking other packages that depend on the ZTK. This way the developer making the changes could do one or more of the following: * provide better backward compatibility * fix up the breaking packages * provide a better warning to others who are maintaining these packages that something was broken. I faintly, faintly recall we had such early-warning mechanisms in the past. :) Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] shrinking the ZTK: a proposed solution
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Hi there, So here's my proposed solution for the ZTK shrinking issue: The ZTK branch 'faassen-smaller' contains Hanno's smaller ZTK. Since Zope 2 forked the ZTK in response and continued to make changes to their fork, I've tried to keep it in sync with the Zope 2 fork. I've created a new 'zopeapp' package that expands the ZTK with zope.app. packages in my sandbox. This extracts that information from the ZTK. Hopefully after we get some feedback from other steering group members (very silent indeed in the holiday period when all this happened) we can make these two projects the official one: a ZTK project and a zopeapp project. A few things I ask the ZTK maintainers: I ask the ZTK maintainers to have the same concern for the zope.app packages as for any other user of the ZTK: work to support zopeapp's compatibility with the ZTK. If the zopeapp maintainers have issues, listen to them seriously. I think everybody can agree that this is within the ZTK mandate for the time being, as zopeapp clearly exists and is being used by a significant amount of people. (I'd like to work to retire it by making it used by far less people) You're kidding, right? Different frameworks / pacakges use sets of packages which intersect with the one you just invented and labeled 'zopeapp', but *nobody* is using that labeled set: it didn't even exist a hundred hours ago. One thing that the consumers of zope.app.* packages can do first is to contribute lists the specific sets (and pinned versions) they depend on: without such information, nobody can work to ensure that zopeapp is useful to those consumers. Yes, I'm thinking specifically of Grok here, for one: I don't think I also strongly encourage the ZTK maintainers to consider the situation of backwards compatibility seriously. Help people transition from their code now to the ZTK. Helping everybody migrate to the ZTK smoothly increases the value of the ZTK itself. People need to step up and ask for such help before it is even feasible to consider helping them. Obviously I cannot *force* ZTK maintainers to worry about this. Instead I'm appealing to your self-interest. And of course the transition burden is shared and should not fall solely or even predominantly on the ZTK maintainers. My self-interest? Not really: you are appealing to my altruism, in the fact that I care about the *broader* Zope community (broader than Zope2, Grok, Plone, or whatever. Neither of my chosen platforms (Zope2, bfg) rely any longer on any of thsoe pacakages at all, which makes my direct interest in them exactly zero. Again, once real users with non-hypothetical needs speak up, I know that the Zope developer community will help them, as it has alwasy done in the past. I also think we as ZTK maintainers should better consider the concerns of other users of the ZTK. In this case, Zope 2 had less of a concern for zope.app than Grok or Zope 3. I didn't even understand this until the debate was further along. The concerns of others should be considered as well instead of simply rejected. We usually can find ways to balance the concerns of everybody. To that end concerns (or lack thereof) should be clearly communicated and be listened to. For the ZTK to have any usefulness apart from mere aggregation, it needs to have a crisp identity. Anything which gets pulled into it without specific, concrete need muddies that identity, and reduces the value. Pushing to keep the set as small as possible is intended to raise the quality and usefulness of the set for *all* its users: excluding packages can actually help users of the ZTK who also use the excluded packages, precisely because it makes clear the costs of using the excluded pacakges (helping maintain them, for one). Should the zopeapp set get users (e.g., Baiju's BlueBream takes off, or if another Z3-based app ports to using it), that will make supporting zopeapp's needs a reasonable request, simliar to supporting Plone via Zope2. Until people organize such a community of interest around the zopeapp set (or some other grouping), we don't have non-hypothetical reasons to consider it viable. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktCZzgACgkQ+gerLs4ltQ7skwCdGyVfRxjM+LPl0SA6l2fRo84a OjIAn1G06ze2fwjDgPxpmOO0o4MClbJa =9AHz -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce
Re: [Zope-dev] zope.publisher 3.12 broke 25 zope.app packages
Hanno Schlichting wrote: On Mon, Jan 4, 2010 at 11:51 PM, Martijn Faassen faas...@startifact.com wrote: Good news, it was only 24 packages, I counted wrong. :) Couldn't you have solved that by updating one underlying package, like zope.app.testing? Most of zope.app generally depends on things like app.testing, app.zcmlfiles or things like app.publsher. You're probably right - I am not really thinking straight today. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] broken zope.publisher because of new content types in zope.contenttype
Hi Aaron
Betreff: Re: [Zope-dev] broken zope.publisher because of new
content types in zope.contenttype
On Sat, Jan 2, 2010 at 5:17 AM, Roger d...@projekt01.ch wrote:
Hi all
Since aaron added new mimetypes e.g. application/javascript, the
_implicitResult method in zope.publisher.http.py (line 794)
is broken
because the method checks for text/* content types if unicode is
given:
def _implicitResult(self, body):
encoding = getCharsetUsingRequest(self._request) or 'utf-8'
content_type = self.getHeader('content-type')
if isinstance(body, unicode):
try:
if not content_type.startswith('text/'):
raise ValueError(
'Unicode results must have a text content
type.')
except AttributeError:
raise ValueError(
'Unicode results must have a text content
type.')
I changed the mime-type for .js from application/x-javascript
to application/javascript. Since I didn't change any text/*
mime-types, I'm not seeing how my change could be breaking
anything that wasn't already broken. The tests for
zope.publisher run fine for me with my changes, anyway. Can
you tell how to reproduce the breakage?
Sould we remove this basic content type check above?
Or enhance the check with the new added unicode valid content types
like application/javascript.
Since whatever code is breaking for you now probably was
breaking before (since it was passing in
application/x-javascript, which is also not a text/* type),
I'm inclined to think that your problem is at a higher level.
You are absolutly right. It's not your fault and I'm fine with your
changes. I also posted already a mail with more infos. Sorry about that!
I'm still confused because I can't find the changes which makes my
custom and the z3c.zrtresouce package break.
I think this is because of some missing zcml includes which are gone
during refactoring zope.app.* to zope.* packages.
Some refactoring left over a couple of configurations in the zope.app.*
package which are gone now in my setup and probably others project
setup.
I'm fine right now and fixed my custom package. Let me know if
someone else runs into the same problem and I can backport the
fix to the z3c.zrtresource package.
Regards
Roger Ineichen
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
Am Montag 04 Januar 2010 20:16:50 schrieb Jan Ulrich Hasecke: On 04.01.10 19:23, Baiju M wrote: Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. Coming from marketing I strongly suggest to think twice or better thrice before inventing the next new name in Zope world. There are already too many of them. Although I tend to give you right, as probably no one will get the fish connection and therefore a new name has to be raised up, I vote for BlueBream, as this indicates something very new, which frees itself from those endless Zope 3, Zope 3 Application Server, Zope blah blah... considerations. +1 Best Regards, Hermann -- herm...@qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] shrinking the ZTK: a proposed solution
Am Montag 04 Januar 2010 23:10:05 schrieb Tres Seaver: Martijn Faassen wrote: Hi there, So here's my proposed solution for the ZTK shrinking issue: Should the zopeapp set get users (e.g., Baiju's BlueBream takes off, or if another Z3-based app ports to using it), that will make supporting zopeapp's needs a reasonable request, simliar to supporting Plone via Zope2. Until people organize such a community of interest around the zopeapp set (or some other grouping), we don't have non-hypothetical reasons to consider it viable. To give you some personal insight: Two of my ongoing projects - which are quite big - rely on zope.app. At least, I have various imports from these modules: zope.app.authentication zope.app.security zope.app.container zope.app.component zope.app.pagetemplate zope.app.exception I'd rather not like to rewrite all that in case zope.app dies off. But I have to further state that I'm locked into Zope 3.4.0 as the support for Python 2.4 was dropped, so I can't upgrade to the current ZTK. Therefore I'm currently not that much affected by those issues, but I personally hope that BlueBream takes off as this seems to be the logical upgrade path for me in the future. Best Regards, Hermann -- herm...@qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
Have you considered just Bream ? ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
I got the fish connection straight away. Not sure its a good move. T On Tue, Jan 5, 2010 at 7:43 AM, Hermann Himmelbauer du...@qwer.tk wrote: Am Montag 04 Januar 2010 20:16:50 schrieb Jan Ulrich Hasecke: On 04.01.10 19:23, Baiju M wrote: Hi All, I am proposing to call Zope 3 - the web frame work as BlueBream. The main use for name is documentation. Coming from marketing I strongly suggest to think twice or better thrice before inventing the next new name in Zope world. There are already too many of them. Although I tend to give you right, as probably no one will get the fish connection and therefore a new name has to be raised up, I vote for BlueBream, as this indicates something very new, which frees itself from those endless Zope 3, Zope 3 Application Server, Zope blah blah... considerations. +1 Best Regards, Hermann -- herm...@qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
Am 05.01.2010 um 00:43 schrieb Hermann Himmelbauer: Although I tend to give you right, as probably no one will get the fish connection and therefore a new name has to be raised up, I vote for BlueBream, as this indicates something very new, which frees itself from those endless Zope 3, Zope 3 Application Server, Zope blah blah... considerations. And getting an endless discussion about Zope, Zope Toolkit, Zope 2, Grok, Bluebream, repoze.bfg … I am just creating a German broschure about Zope and we are relaunching zope.de these days, and I can tell you it is hell to explain what Zope is. What's in a name? I don't mind having a name for a reborn Zope 3 and Bluebream might be ok. But we must keep an eye on our trademark Zope. What is Zope if we have - Zope Toolkit - Zope 2 - Grok - Bluebream - BFG Seems that there is no Zope anymore. ;-) juh smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.security dependency on zope.exceptions
* 2010-01-05 08:26, Fabio Tranchitella wrote: While doing it, I'm trying to remove dependencies which are zope-specific, to minimize the overhead for developers who are using the whole zope stack (like me :)). Ehm, I meant who are NOT using the whole zope stack. Fabio ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New Zope 3 name: BlueBream
Am 05.01.2010 08:13, schrieb Jan Ulrich Hasecke: Am 05.01.2010 um 00:43 schrieb Hermann Himmelbauer: Although I tend to give you right, as probably no one will get the fish connection and therefore a new name has to be raised up, I vote for BlueBream, as this indicates something very new, which frees itself from those endless Zope 3, Zope 3 Application Server, Zope blah blah... considerations. And getting an endless discussion about Zope, Zope Toolkit, Zope 2, Grok, Bluebream, repoze.bfg … I am just creating a German broschure about Zope and we are relaunching zope.de these days, and I can tell you it is hell to explain what Zope is. What's in a name? I don't mind having a name for a reborn Zope 3 and Bluebream might be ok. But we must keep an eye on our trademark Zope. What is Zope if we have - Zope Toolkit - Zope 2 - Grok - Bluebream - BFG Seems that there is no Zope anymore. ;-) juh I agree, we have two names that ar known to a wider audience: Zope and Plone. all the other items bear so little market value that even an insider can not place them. Therefore I think either of the two should be part of any new packages name meant to be recognized by non Zope affectionados. Bluebream for Zope BlueZope Bluebream gone Zope what ever robert ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
