-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> On Tue, Jan 26, 2010 at 11:08 PM, Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Baiju M wrote:
>>
>>> What about committing SVG (source) file, so that others can modify
>>> easily.
>> How doe the SVG so
On Tue, Jan 26, 2010 at 11:08 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Baiju M wrote:
>
>> What about committing SVG (source) file, so that others can modify
>> easily.
>
> How doe the SVG source files interact with the (TrueType, I presume?)
> font file?
Font
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> What about committing SVG (source) file, so that others can modify
> easily.
How doe the SVG source files interact with the (TrueType, I presume?)
font file?
> BTW, logos comes under trademark law, which is different from
> copyrig
On Tue, Jan 26, 2010 at 10:13 PM, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Christian Theune wrote:
>> On 01/25/2010 03:15 AM, Baiju M wrote:
>>> Hi Christophe,
>>>
>>> On Mon, Jan 25, 2010 at 12:45 AM, Christophe Combelles
>>> wrote:
maybe just be sure the or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
> On 01/25/2010 03:15 AM, Baiju M wrote:
>> Hi Christophe,
>>
>> On Mon, Jan 25, 2010 at 12:45 AM, Christophe Combelles wrote:
>>> maybe just be sure the original author won't claim anything in the future?
>>> ie. the logo shou
On Sunday 17 January 2010, Martin Aspeli wrote:
> Stephan Richter wrote:
> > On Sunday 17 January 2010, Martin Aspeli wrote:
> >> I'm using zope.testing-3.7.7, which is what comes with Zope 2.12.
> >
> > Here is what I have in effectively any package:
> >
> > [coverage-test]
> > recipe = zc.recipe.
Hi,
Christian Theune wrote:
> On 01/26/2010 03:30 PM, Souheil CHELFOUH wrote:
>> Well, the first step is already to cut the dependencies and get a sane
>> tree and a reusable package.
>> The second step, however, if people feel like it, will be to refactor
>> a bit and _that_ will need careful pl
On 01/26/2010 03:30 PM, Souheil CHELFOUH wrote:
> Well, the first step is already to cut the dependencies and get a sane
> tree and a reusable package.
> The second step, however, if people feel like it, will be to refactor
> a bit and _that_ will need careful planning, yes.
> But, one thing at a t
Well, the first step is already to cut the dependencies and get a sane
tree and a reusable package.
The second step, however, if people feel like it, will be to refactor
a bit and _that_ will need careful planning, yes.
But, one thing at a time :)
However, I'll polish a bit zope.plugabbleauth and
Hi,
On 01/26/2010 03:02 PM, Jan-Wijbrand Kolman wrote:
> Hi,
>
>
> Just my quick 2 euro cents here:
>
> As far as I can tell, what Souheil did so far is no architectural change, but
> a
> change like so many in the recent past where a zope.app.something package has
> been refactored into a z
Hi,
Christian Theune wrote:
> On 01/26/2010 09:32 AM, Souheil CHELFOUH wrote:
>> I hear you and understand you.
>
> Thanks. :)
>
>> I'm not advertizing for an immediate and brainless action.
>> What I did this week end is simply to split the PAU from all the
>> components provided with it (wel
On Tue, Jan 26, 2010 at 7:49 AM, Marius Gedminas wrote:
> Any ideas about
> fixing the deprecation warning caused by renormalizing.py? All it does
> is
>
> 'import doctest'
>
> which, due to Python's unfortunate import semantics, is interpreted as
>
> 'from zope.testing import doctest'
> Ideas
On Jan 26, 2010, at 7:49 AM, Marius Gedminas wrote:
> I got tired of seeing things like
>
> /home/mg/tmp/buildout-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 m
I got tired of seeing things like
/home/mg/tmp/buildout-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
and since zope.testing
Summary of messages to the zope-tests list.
Period Mon Jan 25 12:00:00 2010 UTC to Tue Jan 26 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: Mon Jan 25 20:36:30 EST 2010
URL: http://
On Tue, Jan 26, 2010 at 11:20, Christian Theune wrote:
> I think this has to do with too little communication going on within the
> steering group (one of the founding premises was to do as little
> "backroom" communication as possible which ended up in no backroom
> communication, which IMHO does
Christian Theune wrote:
>> As a matter of constructive criticism, it would be useful to have
>> something like this on the z3c.caching PyPI page. Right now, there is no
>
> That's a typo, right?
D'oh; z3c.coverage, I meant.
>> way that I can see to understand how the package is meant to be used
>
Hi,
I'm just putting in some 0.02EUR here to give some feedback about the
current state.
On 01/22/2010 10:27 PM, Martijn Faassen wrote:
> Hi there,
>
> This is to announce my withdrawal from the Zope Toolkit steering
> group.
I'm also sad to see you go -- hopefully with the chance of seeing you
Hi Marius,
On Wed, Dec 30, 2009 at 4:37 AM, Marius Gedminas wrote:
> So, what's the way forward for existing Zope 3.4 (KGS) users?
I hope you might be heard about "BlueBream". My ideas is
to create a successor to "Zope 3". As part of this effort,
I started working on a KGS based on zopetookit:
* Martijn Faassen [2010-01-22 22:27]:
> This is to announce my withdrawal from the Zope Toolkit steering group.
I'm saddened to hear this. I feel that many if not all of the things you
were trying to set in motion in our community are desperately needed.
I'm sorry to hear that you have been worn
On 12/30/2009 12:17 AM, Martijn Faassen wrote:
> Hey,
>
> Marius Gedminas wrote:
>> So, what's the way forward for existing Zope 3.4 (KGS) users?
>>
>> Rewrite our apps so we don't depend on anything in zope.app and switch
>> to the ZTK?
>
> That's not possible as far as I can see, as the Zope 3.
On 01/11/2010 06:25 AM, Chris McDonough wrote:
> Baiju M wrote:
>> On Mon, Jan 11, 2010 at 10:22 AM, Baiju M wrote:
>>> Hi All,
>>> There was an adapter registration provides IUserPreferredCharsets.
>>> I can see it has moved to zope.i18n.locales with some others here:
>>> http://svn.zope.
On 01/11/2010 02:26 PM, Roger wrote:
> Hi all
>
> I'm not happy with the current vocabulary registry
> concept.
Please note that vocabularies have had a successor concept for a while:
sources.
They are much cleaner and split their concerns for various aspects much
more nicely.
They don't provid
Hi,
On 01/26/2010 09:32 AM, Souheil CHELFOUH wrote:
> Christian,
>
> I hear you and understand you.
Thanks. :)
> I'm not advertizing for an immediate and brainless action.
> What I did this week end is simply to split the PAU from all the
> components provided with it (well, most of it).
> That
Christian,
I hear you and understand you.
I'm not advertizing for an immediate and brainless action.
What I did this week end is simply to split the PAU from all the
components provided with it (well, most of it).
That was motivated by my current work and by the will to see the
dependencies become
Hi,
On 01/26/2010 09:06 AM, Souheil CHELFOUH wrote:
> Hello,
>
> I took the liberty to start the work by a first simple move :
> splitting apart what is "strictly" about PAU's core and the rest.
> PAU and some plugins have been put in :
> http://svn.zope.org/repos/main/zope.pluggableauth/trunk/
>
Hello,
I took the liberty to start the work by a first simple move :
splitting apart what is "strictly" about PAU's core and the rest.
PAU and some plugins have been put in :
http://svn.zope.org/repos/main/zope.pluggableauth/trunk/
The rest has been kept in:
http://svn.zope.org/repos/main/zope.ap
On 01/18/2010 05:34 AM, Martin Aspeli wrote:
> Stephan Richter wrote:
>> On Sunday 17 January 2010, Martin Aspeli wrote:
>>> I'm using zope.testing-3.7.7, which is what comes with Zope 2.12.
>>
>> Here is what I have in effectively any package:
>>
>> [coverage-test]
>> recipe = zc.recipe.testrunner
28 matches
Mail list logo
