Re: [Zope-dev] Request input on bug about HTTP response.setStatus
Hi all > Betreff: [Zope-dev] Request input on bug about HTTP response.setStatus > > Hi all. There's some disagreement about how to resolve the > bug below, even though there's agreement that we want it > resolved. Your input would be appreciated so we can find a > consensus and move forward with a solution. > > https://bugs.edge.launchpad.net/zope3/+bug/322486 As far as I can see, we all agree that we need to be able to use new response status. And the question is, should we be able to use them ad hoc or do we need to declare them first. In programming language normaly you can just use things. But a framework like a server must be configured first befor you can use new things. I think it's a question if the response setStatus is a kind of the server as a framework or if this is just another python method. As far as I can tell, I personaly like to use setStatus(209) and I whould be surprised if something other then 209 get returned as 209 by getStatus() (as shane told). another solution could be to introduce an additional argument. (seatbelt) e.g. def setStatus(status, force=False): if force: # don't fallback to status 500 else: # fallback to 500 if given status doesn't exist Anyway, Python is a bike and java is a car. Because why? Java has built in seatbelts and airbags and Python is light and fast. Regards Roger Ineichen ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Request input on bug about HTTP response.setStatus
Hi all. There's some disagreement about how to resolve the bug below, even though there's agreement that we want it resolved. Your input would be appreciated so we can find a consensus and move forward with a solution. https://bugs.edge.launchpad.net/zope3/+bug/322486 Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.security changes
On Wednesday 28 January 2009, Dan Korostelev wrote: > I think, the better place to move zcml directives is zope.component, > as it already depends on zope.security for the zcml support and the > "class" directive also has component-related "factory" subdirective > which declared in zope.component. Good point. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.security changes
On Wednesday 28 January 2009, Marius Gedminas wrote: > Sounds good! > > What about the other use case of , i.e. declaring implemented > interfaces, as in > > > > I was waiting for that comment. :-) I wanted to write the same this morning, but then decided that the new solution is better than anything else I could think of. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Attention Zope 3 KGS consumers: zope.kgs changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan Richter wrote:
> On Wednesday 28 January 2009, Marius Gedminas wrote:
>> Can you add Apache rewrite rules to redirect the old URLs to the new
>> locations, just on general principles ("cool URLs don't change")?
>
> If someone with sys admin rights helps me, sure. On the other hand, now that
> I
> think about it, I wonder whether symlinks would work too.
If Apache is configured to follow them, yes.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJgOLN+gerLs4ltQ4RAsRdAJ9jn0hnbqNFO2TfAioJuQZlQkWJKQCeJvij
FhW+l9TQYNowhQ9FGt1xgbA=
=uUdg
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.security changes
2009/1/29 Marius Gedminas : > On Wed, Jan 28, 2009 at 06:42:58PM +0100, Martijn Faassen wrote: >> Hi there, >> >> In the dependency cleanup effort we've got going on at the Grok >> cavesprint here at my house, we have moved code around some more. >> >> zope.security was already defining ZCML directives so we've moved the >> directive from zope.app.component and and the >> directive from zope.app.security into zope.security as well. These only >> need things that are in zope.security already (or its dependencies) and >> the directives are about security declarations, so they seem to fit >> quite well into their new place. > > Sounds good! > > What about the other use case of , i.e. declaring implemented > interfaces, as in > > > > +1. That's kinda strange to have it in zope.security. I think, the better place to move zcml directives is zope.component, as it already depends on zope.security for the zcml support and the "class" directive also has component-related "factory" subdirective which declared in zope.component. -- WBR, Dan Korostelev ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.security changes
On Wed, Jan 28, 2009 at 06:42:58PM +0100, Martijn Faassen wrote: > Hi there, > > In the dependency cleanup effort we've got going on at the Grok > cavesprint here at my house, we have moved code around some more. > > zope.security was already defining ZCML directives so we've moved the > directive from zope.app.component and and the > directive from zope.app.security into zope.security as well. These only > need things that are in zope.security already (or its dependencies) and > the directives are about security declarations, so they seem to fit > quite well into their new place. Sounds good! What about the other use case of , i.e. declaring implemented interfaces, as in ? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] z3c.recipe.compattest
Hi there, Here at the Grok dependency reduction sprint Sylvain and Wolfgang have been working on a buildout recipe called 'z3c.recipe.compattest': http://pypi.python.org/pypi/z3c.recipe.compattest What this brings to Zope development is a way to test changes in one package against a lot of other packages to check whether things haven't been broken by your change. It will download each package and run the tests per package (in a separate process so that tests don't have hidden dependencies on each other). It can test against releases on PyPI or take the trunks of packages on svn.zope.org. We're currently running it through paces and work out any problems with it, but I think it'll be quite useful for people working on larger-scale changes that could potentially affect many packages. We've used it to find all kinds of incompatibilities that were created between packages already, and have been fixing some of them. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.security changes
Hi there, In the dependency cleanup effort we've got going on at the Grok cavesprint here at my house, we have moved code around some more. zope.security was already defining ZCML directives so we've moved the directive from zope.app.component and and the directive from zope.app.security into zope.security as well. These only need things that are in zope.security already (or its dependencies) and the directives are about security declarations, so they seem to fit quite well into their new place. This way we can (eventually) lift some dependencies of packages on zope.app.security and zope.app.component and point it to zope.security instead, which will help clean up the dependency structures. We've left backwards compatibility imports in place in the zope.app.* packages (hopefully enough of it) so that existing code will continue to work. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Attention Zope 3 KGS consumers: zope.kgs changes
On Wednesday 28 January 2009, Marius Gedminas wrote:
> Can you add Apache rewrite rules to redirect the old URLs to the new
> locations, just on general principles ("cool URLs don't change")?
If someone with sys admin rights helps me, sure. On the other hand, now that I
think about it, I wonder whether symlinks would work too.
Regards,
Stephan
--
Stephan Richter
Web Software Design, Development and Training
Google me. "Zope Stephan Richter"
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Attention Zope 3 KGS consumers: zope.kgs changes
On Tue, Jan 27, 2009 at 09:57:49AM -0800, Stephan Richter wrote:
> With these extensions comes also a change in URLs. All files/directories
> related to a particular version are now located within a directory named
> after the version. For the Zope 3 KGS, this will have the following impact:
>
> http://download.zope.org/zope3.4/versions-3.4.0c4.cfg
> ->
> http://download.zope.org/zope3.4/3.4.0c4/versions.cfg
>
> http://download.zope.org/zope3.4/controlled-packages-3.4.0c4.cfg
> ->
> http://download.zope.org/zope3.4/3.4.0c4/controlled-packages.cfg
>
> I will retroactively change the locations for all zope3.4 KGS releases.
Can you add Apache rewrite rules to redirect the old URLs to the new
locations, just on general principles ("cool URLs don't change")?
Marius Gedminas
--
http://pov.lt/ -- Zope 3 consulting and development
signature.asc
Description: Digital signature
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Attention Zope 3 KGS consumers: zope.kgs changes
On Wednesday 28 January 2009, Sebastien Douche wrote: > On Tue, Jan 27, 2009 at 18:57, Stephan Richter > > wrote: > > as you probably saw from the checkins last night, Paul and I finished all > > outstanding coding tasks that were blocking a Zope 3.4 release based on a > > KGS. In particular, we can generate a skinable Web site for a KGS and the > > release process is now very much automated. > > Great! Is there any reason to not upload zope.kgs and zope.release to Pypi? Nope, I will do that soon. I was just concentrating on the Zope 3.4 release first. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Tue Jan 27 12:00:00 2009 UTC to Wed Jan 28 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Tue Jan 27 20:45:37 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010951.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Tue Jan 27 20:47:11 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010952.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Tue Jan 27 20:48:42 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010953.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Tue Jan 27 20:50:12 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010954.html Subject: OK : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Tue Jan 27 20:51:44 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010955.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Jan 27 20:53:14 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010956.html Subject: OK : Zope[2.buildout]-trunk Python-2.4.5 : Linux From: Zope Tests Date: Tue Jan 27 20:54:48 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010957.html Subject: OK : Zope[2.buildout]-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Jan 27 20:56:29 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-January/010958.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Attention Zope 3 KGS consumers: zope.kgs changes
On Tue, Jan 27, 2009 at 18:57, Stephan Richter wrote: > as you probably saw from the checkins last night, Paul and I finished all > outstanding coding tasks that were blocking a Zope 3.4 release based on a > KGS. In particular, we can generate a skinable Web site for a KGS and the > release process is now very much automated. Great! Is there any reason to not upload zope.kgs and zope.release to Pypi? -- Sebastien Douche ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
