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 disagr
On Mon, Jan 4, 2010 at 00:43, Chris McDonough 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.mo
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
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://
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 IS
On Mon, Jan 4, 2010 at 6:32 PM, Jan-Wijbrand Kolman
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
Baiju M wrote:
> On Mon, Jan 4, 2010 at 6:32 PM, Jan-Wijbrand Kolman
> 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 al
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.or
On Mon, Jan 4, 2010 at 7:32 PM, Jan-Wijbrand Kolman
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-De
Jan-Wijbrand Kolman wrote:
> 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?
I see someone gave you the owner role already, so you should be able to
go ahead.
Regards,
Martijn
__
Jan-Wijbrand Kolman wrote:
> Baiju M 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.testin
Baiju M wrote:
> On Mon, Jan 4, 2010 at 7:32 PM, Jan-Wijbrand Kolman
> 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 up
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
On Mon, Jan 4, 2010 at 9:01 PM, Stephan Richter
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
On Sat, Jan 2, 2010 at 5:17 AM, Roger 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(
Benji York wrote:
> On Sun, Jan 3, 2010 at 6:43 PM, Chris McDonough 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
>>
On Mon, Jan 4, 2010 at 10:36 PM, Baiju M 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.o
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
Hi there,
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 ki
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 cat
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 origi
Martijn Faassen 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
> strangel
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 it
-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 inve
Jan-Wijbrand Kolman wrote:
[snip]
> It must be something small and simple I guess, but it is needles and
> haystacks
> for me at this point...
Since I could reproduce this failure with zopeapp, it must be a very
recent change.
From what I can see, zope.container and zope.publisher changed.
z
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
On Mon, Jan 4, 2010 at 21:44, Shane Hathaway 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
-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
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,
probab
Baiju M wrote:
> I am proposing to call "Zope 3 - the web frame work"
> as "BlueBream".
+1
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
-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
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 fra
Hi there,
Good news, it was only 24 packages, I counted wrong. :)
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.zo
On Mon, Jan 4, 2010 at 11:51 PM, Martijn Faassen 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 ap
Hanno Schlichting wrote:
> On Mon, Jan 4, 2010 at 11:51 PM, Martijn Faassen
> 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.t
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 wrote:
> > Hi all
> >
> > Since aaron added new mimetypes e.g. application/javascript, the
> > _implicitResult method in zope.publisher.http.py
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
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 su
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.
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 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 - th
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
On Tue, Jan 5, 2010 at 12:43 PM, Jan Ulrich Hasecke
wrote:
>
> 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 som
Happy New Year to everybody,
I'm working to isolate a core set of ZTK packages which are independent
from Zope and reusable outside the Zope community. One of them is
zope.security, which can be used (and it is useful, indeed) with non-zope
frameworks too.
While doing it, I'm trying to remove dep
* 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
__
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"
On Tue, Jan 5, 2010 at 08:36, Martin Aspeli wrote:
> +1. It puts the final nail in the Zope 3 coffin and allows a reborn
> vampire to emerge from slumber.
Vampire Fish! Aaaargh!
--
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64
_
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 v
47 matches
Mail list logo
