<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.web.zope.zope3">
    <title>gmane.comp.web.zope.zope3</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22535"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22534"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22533"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22532"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22531"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22530"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22529"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22528"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22527"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22526"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22525"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22524"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22523"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22522"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22521"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22520"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22519"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22518"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22517"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22516"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22535">
    <title>Re: zope3 and zope.conf without the zodb</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22535</link>
    <description>
Hey, this discussion shouldn't be taking place on zope3-dev, which has 
been retired. Can we move it over to zope-dev?

Regards,

Martijn

</description>
    <dc:creator>Martijn Faassen</dc:creator>
    <dc:date>2007-11-01T13:52:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22534">
    <title>Re: zope3 and zope.conf without the zodb</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22534</link>
    <description>Would you be willing to share your code, particularly your published  
application and the ZCML to configure Zope 3 to not use the default  
publication stuff?  I'm curious as to how people are doing this.

- C

On Oct 31, 2007, at 2:32 PM, Kapil Thangavelu wrote:


</description>
    <dc:creator>Chris McDonough</dc:creator>
    <dc:date>2007-10-31T19:12:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22533">
    <title>Re: zope3 and zope.conf without the zodb</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22533</link>
    <description>
Why do you still need zope.conf if you don't need ZODB? I mean, there 
isn't really much else left if you take away the ZODB configuration.


</description>
    <dc:creator>Philipp von Weitershausen</dc:creator>
    <dc:date>2007-10-31T18:51:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22532">
    <title>zope3 and zope.conf without the zodb</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22532</link>
    <description/>
    <dc:creator>Kapil Thangavelu</dc:creator>
    <dc:date>2007-10-31T18:32:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22531">
    <title>Re: z3c.form: handling of interface invariants</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22531</link>
    <description>
Am 09.10.2007 um 08:43 schrieb Michael Howitz:


Done. Merged today.

</description>
    <dc:creator>Michael Howitz</dc:creator>
    <dc:date>2007-10-30T08:11:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22530">
    <title>Re: zc.testbrowser.real depends on python 2.5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22530</link>
    <description>

Actually, it's a function that is defined in zope.testbrowser and was 
lost in translation to zc.testbrowser.
</description>
    <dc:creator>Benji York</dc:creator>
    <dc:date>2007-10-23T20:14:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22529">
    <title>zc.testbrowser.real depends on python 2.5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22529</link>
    <description>Looks like zc.testbrowser 1.0a1 has a small dependency on Python 2.5.
I got this error while playing with zc.testbrowser.real:

Traceback (most recent call last):
  File "&lt;stdin&gt;", line 1, in ?
  File "/home/pw/tbtest/lib/python2.4/zc.testbrowser-1.0a1-py2.4.egg/zc/testbrowser/real.py", line 315, in getForm
    if index is None and not any([id, name, action]):
NameError: global name 'any' is not defined

This is easy to hack around, but it's probably worth documenting the
dependency...

</description>
    <dc:creator>Paul Winkler</dc:creator>
    <dc:date>2007-10-23T20:09:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22528">
    <title>Re: Better default namechooser</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22528</link>
    <description>On 2007-10-12 10:21:28 +0200, Philipp von Weitershausen 
&lt;philipp&lt; at &gt;weitershausen.de&gt; said:


Of course they can. But looking from the browser/user perspective any 
URL containing %XY looks just strange. Also those urls are often 
garbled by mail programms or alike.


Of course it's trival. Only that I've *always* had to replace it with 
something else for every single project so far. So from my perspective 
the default might work but is sort of useless.

But well, maybe it's not work the effort since we've eggs now.

</description>
    <dc:creator>Christian Zagrodnick</dc:creator>
    <dc:date>2007-10-15T07:00:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22527">
    <title>Re: Static Zope 3 APIDOC available!</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22527</link>
    <description>On 2007-10-11 18:27:39 +0200, Stephan Richter 
&lt;srichter&lt; at &gt;cosmos.phy.tufts.edu&gt; said:


Oh yes, I *hate* a translated API-Doc. Would take me hours to figure 
out what is actually meant.


</description>
    <dc:creator>Christian Zagrodnick</dc:creator>
    <dc:date>2007-10-15T06:55:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22526">
    <title>Re: ChoiceField and the use of sources/vocabularies</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22526</link>
    <description>
I agree. It's very nice.


That sounds like a sensible solution.


Yup, therefore -1.

Probably-my-last-post-to-zope3-dev-ly,
Philipp


</description>
    <dc:creator>Philipp von Weitershausen</dc:creator>
    <dc:date>2007-10-14T11:56:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22525">
    <title>Re: Zope 3 releases?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22525</link>
    <description>
Having a list of "promises" with the decision of what a release is
would be nice too. Tarball release was (at least i thought that it
was) promising that:

* You will be able to migrate from 3.3 to 3.4 without any errors, only
with a lot of deprecation warnings.
* 3.3 will only have bugfixes added, not new features.
* 3.3 will work.
* Your database will evolve from 3.3 to 3.4.

I am a bit wary that skipping a tarball release and going directly to
eggs might cause evolution and backwards compatibility problems for
anyone that was using the 3.3 tarball. I only managed to migrate from
3.3 to 3.4 eggs through 3.4.0b1 tarball, because SchoolTool just
didn't work with eggs without a significant set of changes to the
code.

So releasing a tarball and then working towards an egg based 3.5 that
will have a migration path from 3.4 tarball might take less time, than
creating a set of 3.4 eggs that work with 3.3 applications.


Well - if it will be possible to go from Zope 3.3 that got released in
Ubuntu to a set of zo</description>
    <dc:creator>Ignas Mikalajunas</dc:creator>
    <dc:date>2007-10-12T10:54:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22524">
    <title>Re: Better default namechooser</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22524</link>
    <description>
Why would you want to replace all non-ASCII characters by default? Names 
of contained objects can be unicode, and URLs can contain unicode 
segments as well (encoded as UTF-8). Having the default namechooser make 
the arbitrary decision of disallowing everything that's not ASCII seems 
quite arbitrary.


Again, object names may contain spaces. I don't understand why this 
should be the *default* policy. If you need this kind of stuff, then I 
suggest you write your own namechooser; it's quite trivial.


</description>
    <dc:creator>Philipp von Weitershausen</dc:creator>
    <dc:date>2007-10-12T08:21:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22523">
    <title>Re: Let's move over to zope-dev</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22523</link>
    <description>
On Oct 11, 2007, at 12:34 PM, Marius Gedminas wrote:


If someone wants to do this and needs access, I'm happy to set them  
up. Not it!

Jim

--
Jim Fulton
Zope Corporation


</description>
    <dc:creator>Jim Fulton</dc:creator>
    <dc:date>2007-10-11T17:37:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22522">
    <title>Re: Let's move over to zope-dev</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22522</link>
    <description/>
    <dc:creator>Marius Gedminas</dc:creator>
    <dc:date>2007-10-11T16:34:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22521">
    <title>Re: Static Zope 3 APIDOC available!</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22521</link>
    <description>
It was generated from the trunk a few weeks back. The entire APIDOC code needs 
to be reviewed in light of eggs.


No, especially not for the static version. It is very impractical to try to 
translate all the information anyways, since it is generated from code.

Regards,
Stephan
</description>
    <dc:creator>Stephan Richter</dc:creator>
    <dc:date>2007-10-11T16:27:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22520">
    <title>Re: Static Zope 3 APIDOC available!</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22520</link>
    <description>Stephan Richter a écrit :


It's very useful, thanks!

Is there a way to know the version number it applies to?
Is there any l10n support or is it planned?


Christophe
</description>
    <dc:creator>Christophe Combelles</dc:creator>
    <dc:date>2007-10-11T15:30:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22519">
    <title>Re: Let's move over to zope-dev</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22519</link>
    <description>
So, this is the last thread.  Good bye zope3-dev ! :(

Regards,
Baiju M


</description>
    <dc:creator>Baiju M</dc:creator>
    <dc:date>2007-10-11T14:50:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22518">
    <title>Re: Zope 3 releases?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22518</link>
    <description/>
    <dc:creator>Christian Theune</dc:creator>
    <dc:date>2007-10-11T14:42:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22517">
    <title>Let's move over to zope-dev</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22517</link>
    <description>
I think we have agreement (or an absense of anyone who is willing to  
publicly admit to disagree) to retire this list and move over to zope- 
dev.  Let's do so.  I'll wait a little while before trying to  
actively prevent posts here.  I suggest we let any existing threads  
run out and start new threads on zope-dev.

Jim

--
Jim Fulton
Zope Corporation


</description>
    <dc:creator>Jim Fulton</dc:creator>
    <dc:date>2007-10-11T14:17:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22516">
    <title>Re: Better default namechooser [Off topic]</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22516</link>
    <description>Been looking for something like that for some time.
I would love to use more of the stuff from the plone repos.
But it is all gpl which makes it a no go.
Maybe the Plone dudes could start to use lgpl for the zope 3 components 
they develop?

Sidnei da Silva wrote:

</description>
    <dc:creator>Oliver Marx</dc:creator>
    <dc:date>2007-10-11T14:12:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.zope3/22515">
    <title>Re: Better default namechooser</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.zope3/22515</link>
    <description>
I suggest looking (and using!) at plone.i18n.normalizer, just an
'easy_install' away:

http://api.plone.org/Plone/3.0/public/src/plone.i18n/plone/i18n/plone.i18n.normalizer.tests.test_normalizer-module.html

</description>
    <dc:creator>Sidnei da Silva</dc:creator>
    <dc:date>2007-10-11T14:02:05</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.web.zope.zope3">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.zope.zope3</link>
  </textinput>
</rdf:RDF>
