Can someone release z3c.indexer 0.5.1, or give me rights to do so
myself? It has some important bugfixes and seems to be stable. Or is
there any work on this package planned to do soon? :-)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev
, can someone make a release on PyPI of this package?
--
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
2008/12/2 Marius Gedminas <[EMAIL PROTECTED]>:
> On Tue, Dec 02, 2008 at 02:04:39AM +0300, Dan Korostelev wrote:
>> I just removed zope.testing from the zope.index dependency and
>> replaced zope.testing.doctest imports with plain python doctest and it
>> seems to work w
The zope.configuration 3.4.1 was tagged as released two months ago,
but it's still not uploaded to PyPI. :-) Can someone upload it?
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
*
sy.
PS BTW, I think that zope.app.keyreference should be moved to plain
zope.keyreference, because it's really lightweight, useful outside of
zope and it doesn't depend on any zope.app package. What do you people
think?
--
WBR, Dan Korostelev
___
Zope-Dev
d it works okay. :-)
Or, it might be that I don't fully understand your code and
application architecture, so I would like to hear more about it. It
looks quite over-engeneered to me.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
t be too
optimal, but I'm currently most interested in clean and universal
IIndexSort definition that any index could efficiently implement.
If there's no objections, I'd like to merge it to trunk and start
adding sorting features for zope.app.catalog/z3c.indexer, as well as
zc.catalo
2008/12/27 Chris McDonough :
> Dan Korostelev wrote:
>> I also made an implementation for the FieldIndex that may not be too
>> optimal, but I'm currently most interested in clean and universal
>> IIndexSort definition that any index could efficiently implement.
>
>
ndex and
zope.app.catalog.
Thanks in advance.
--
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/listinf
2008/12/28 Chris McDonough :
> Dan Korostelev wrote:
> - I'm tempted to ditch the case normalization feature of keyword indexes.
> This
> is actually the application's job; there's no guarantee that values that are
> passed by the app will be strings. I'm not
t; who
> used them to how do the one-time upgrade in CHANGES.txt. IMO, of course.
I'm generally fine with that. So if there won't be objections until
tommorow, I'll make that refactorings and merge that code to trunk.
--
WBR, Dan Korostelev
__
e KeyError, others may
not, so I'd leave the interface as it is now.
BTW, you might be interested in zc.blist package for the ZODB-friendly
balanced lists structure.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.z
that code to zope.app.catalog trunk and make a
new feature release, containing this functionality. So I'd like
community to review these changes and comment/object it.
Thanks!
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http:/
itself, because
it can be quite useful together with zope.interface's adapter pattern.
What are you people think about including delegates code into zope.interface?
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.
2009/1/14 Dan Korostelev :
> 2009/1/13 Gary Poster :
>>
>> http://pypi.python.org/pypi/lazr.delegates
>>
>> Provides an interesting Python delegation pattern. Uses
>> zope.interface.
>
> I took a quick view at that lazr.delegates package. The code th
quired=True)
description = Text(title=u'Description', required=False)
class Item(Persistent):
implements(IItem)
title = FieldProperty(IItem['title'])
description = FieldProperty(IItem['description'])
...and use them as base for your objects.
Hope this
hematician, I am not sure,
> whether these are valid concerns. But I would like to know, what others
> think about this. Maybe you can correct me here.
>
> Best regards,
>
> --
> Uli
>
>
> ___
> Zope-Dev maillist - Zope-Dev@zop
e-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 )
>
--
WBR, Dan Korostelev
_
2009/1/27 Stephan Richter :
> On Tuesday 27 January 2009, Fred Drake wrote:
>> On Tue, Jan 27, 2009 at 6:01 AM, Dan Korostelev wrote:
>> > AFAIK, these files are for (pre-egg, no-longer-used) zpkg tool. They
>> > are removed in zope.app.renderer's trunk, BTW.
t 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 Koros
2009/1/31 Stephan Richter :
> Hi everyone,
>
> It is finally here! Thanks goes to everyone who involved!
Thank you!
BTW, there's some problems with python version requirement in the
"tarball" release. It does not accept python 2.5 while it should as
stated in the ann
"over 9000" of them in case of
key-references). I'd like to make non-deprecated backward-compatibilty
imports in the old places until we have a generic and easy-to-use tool
for "touching" ZODB objects.
Suggestions/objections?
--
WBR, Dan Korostelev
__
t for zope.container to be released before starting working on
intid and catalog?
--
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 -
2009/1/31 Martijn Faassen :
> Dan Korostelev wrote:
>> Well, I chose packages that are kind of separated from most of "zope
>> the application" packages, because there aren't many packages that
>> depend on either zope.app.catalog or zope.app.intid/keyreferenc
etiring a
> lot of packages that are mostly unused, and have a smaller, easier set
> of Zope 3 packages to maintain and understand. Users of the Zope 3
> libraries (plain Zope 3, Grok, Zope 2, Repoze, and others) should all
> benefit from this.
>
> Regards
r in zope.traversing doesn't implement
it as well so I got errors. :-/
2009/1/31 Dan Korostelev :
> Hi!
>
> That's a great piece of work you did, thanks!
>
> I've been following package releases and have noticed some mistakes
> mainly in changelog formatting:
2009/1/31 Martijn Faassen :
> Dan Korostelev wrote:
>> Also, there's a bug in zope.traversing:
>>
>> The getParents function of zope.traversing.api uses the "getParents"
>> method of IPhysicallyLocatable, which really is new ILocationInfo, but
>>
Next, I'm going to split zope.app.catalog and check other packages for
uses of zope.app.intid/zope.app.keyreference (I guess some
sqlalchemy-related packages can depend on keyreference stuff).
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-De
r the
renamed package like zope.keyreference until we have a tool for
upgrading ZODB objects properly. May be there are any side-effects
that I don't know of?
2009/2/1 Dan Korostelev :
> I just finished working on zope's intid and keyreference packages.
>
> The whole key-referen
2009/1/31 Martijn Faassen :
> Dan Korostelev wrote:
>> Also, there's a bug in zope.traversing:
>>
>> The getParents function of zope.traversing.api uses the "getParents"
>> method of IPhysicallyLocatable, which really is new ILocationInfo, but
>>
2009/2/1 Christian Theune :
> On Sun, 1 Feb 2009 02:10:00 +0300
> Dan Korostelev wrote:
>
>> I also just checked in a hack to make old keyreference objects
>> loadable if zope.app.keyreference is gone because a buildout doesn't
>> depend on it after upgrade:
>
a1 that's is a dependency of ZODB 3.9. So I
changed the path to tests/savepoint.txt in that ZCML some time before.
You unfixed the https://bugs.launchpad.net/zope3/+bug/303721 :)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev
is None in case of most root objects:) At
least that's what that RootPhysicallyLocatable from zope.traversing
does.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts o
y newbie. Next, we may want to point
people to packages like z3c.pagelet and z3c.form, so some tutorial
should be written on how to add support for that to their current
setup (z3c.rotterdam could be used as an easy way).
Here it is: http://svn.zope.org/Sandbox/nadako/zopesandbox/
--
WBR, Dan Korostele
", because
there are bug fixes and no backward-incompatibilites expected.
--
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 -
2009/2/2 Stephan Richter :
> On Monday 02 February 2009, Dan Korostelev wrote:
>> 2009/2/2 Stephan Richter :
>> > Yeah, the unversioned links are the only ones that I did not maintain.
>> > You now use a reference to the version directly.
>>
>> BTW, why
2009/2/2 Christophe Combelles :
> Dan Korostelev a écrit :
>> 2009/2/2 Christophe Combelles :
>>> Stephan Richter a écrit :
>>>> Hi everyone,
>>>>
>>>> I have setup a KGS for Zope 3.5, so that people can test the development
>>>>
ov.lt, as
there's old ubuntu versions on that servers, but if you are going to
setup another one - may be you'll get py2.6 for that? ;-)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope
t to have that script published so any developer
could use it to set roles for new packages. Stephan? :)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
Oh cool! I didn't know :) Thank you.
2009/2/6, Stephan Richter :
> On Thursday 05 February 2009, Dan Korostelev wrote:
>> BTW, it would be great to have that script published so any developer
>> could use it to set roles for new packages. Stephan? :)
>
> zope.pypisupp
upgrading from, say, Zope 3.4 to Zope 3.5 could easily find the bits
about problems that can pop up in the transition.
What are you thinking about that?
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo
se seems sensible, but if setuptools doesn't support either, then it
> needs fixing...
Why not just define an extra requirement for zcml in the main package
and not generate thousands of packages that contain only meta
directives?
--
WBR, Dan Korostelev
_
a
> lot of work and may be the easiest way out of this set of questions. :)
Yep. Also, as I said before I think we also need to use deprecation
warnings for imports that are not classes for persistent objects
(until Chiristian writes the tool to upgrade them :)).
--
WBR, Dan Korostelev
many of
> the changes made and the general response a developer should have.
That's great! Thank you. Looks like the 3.5 will be even better than 3.4 :)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/m
raise deprecation warnings about ZODB
objects, as it's really easy to fix with the magic tool and again, we
can eventually remove the deprecated import and make our code more
clean.
Let's discuss it once again :)
--
WBR, Dan Korostelev
___
Z
27;t
know twisted at all (shame on me).
--
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/z
ce.
>
> That said, I like a).
+1
--
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/list
you please set the english locale for buildbots? :)
--
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/li
o, I propose to merge the zc.copy package's changes with original
zope.copypastemove/zope.location and deprecate it. If noone objects,
I'll do that myself.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/
ion and make people able to easily copy persistent objects
w/o installing on zope.copypastemove or even zope.location.
2009/2/8 Dan Korostelev :
> The README.txt of zc.copy says that the components, provided by this
> package is apropriate for inclusion in Zope itself.
>
> The p
Okay. I prepared the "zope.copy" package in the SVN for you to check
out what I mean. :)
2009/2/8 Dan Korostelev :
> After looking at the whole copy thing for some more time, I thought
> that it even makes sense to extract the object cloning functionality
> to some &
me to package owners on PyPI
(my name there is "nadako"). Also, should I use deprecated deferred
imports or plain imports for that?
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-de
class and I don't think
that it makes much sense. So I'd propose to just remove it. What do
you people think?
Also, Martijn, Christian, was it the only reason for moving ITraverser
interface from zope.traversing to zope.location? If so, can we still
move it back?
--
WBR,
t.pt?view=auto
--
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:
2009/2/9 Dan Korostelev :
> 2009/2/9 Stephan Richter :
>> Anyone, how close are we to a z3c.form 2.0 release?
>
> I worked on the multi widget a little some time ago, adding
> conditional add/remove buttons. However, there are still some (not too
> important though) TODOs on
pdate" method. I'm
not sure that I'll be doing that very soon as it isn't very important.
So this is definetely not a reason to wait with the release.
One more thing I'd like to do is to add "klass" and "id" to the forms
themselves so one could easily c
nd after we decide which
option to choose I volunteer to migrate current zope.app.locales
translations to every egg that have msgids, previously translated by
zope.app.locales. However, that's kinda pain in the ass and I'll
gladly accept any help on that. :-)
--
WBR, Dan Korostelev
so it can be used as an application component
in the PasteDeploy pipeline without any additional python code. The
zope.publisher also provides a simple WSGI application for use with
paste.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://
2009/2/10 Stephan Richter :
> On Monday 09 February 2009, Dan Korostelev wrote:
>> Nowadays, when we have a fully egg-based setup, the translations in
>> the zope.app.locales package make no sense anymore as it's very hard
>> to maintain them and it just wrong (to me at
2009/2/10 Stephan Richter :
> On Monday 09 February 2009, Dan Korostelev wrote:
>> FileWidget - It doesn't clear the bytes value if no new file is
>> uploaded now, which is nice. But there's also should be a way to clear
>> current value if the field is not r
ldout recipe) that collects
translations from multiple packages into one PO/TMX/whatever file for
using it as a translation memory file for translation tools.
4) call for translators
5) ...
6) PROFIT! :-)
Correct me if I'm wrong.
It would also cool to integrate it with launchpad translation sy
, everything works fine.
Hmm.. zope.container actually uses BTrees from the ZODB3 egg module
for implementing BTreeContainer.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross p
2009/2/10 Laurent Mignon :
> Dan Korostelev wrote:
>> 2009/2/10 Laurent Mignon :
>>> The problem encountered is that zope.container specify ZODB3 as a main
>>> dependency. After checking the code, it seems that ZODB is only required
>>> for tests. If I modif
locales
package, so you can commit it there, if you have commit rights, or
create a report in the zope 3 bugtracker
(https://bugs.launchpad.net/zope3). Or you can just send the updated
.po file to me and I'll update it in the svn. :-)
--
WBR, Dan Korostelev
d a test and you can check it in. :-)
Also, please add a note to CHANGES.txt about that you changed the
signature of SelectFieldWidget, as it breaks backward-compatibility.
Or think a way to avoid that problem. :-)
--
WBR, Dan Korostelev
___
Zope-Dev mai
zope2 will just use zope3 modules as eggs and won't
maintain a copy of them.
--
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
ority over each other, based on registration order
(though that could be developed to give user more control over catalog
priorities). So I think it's possible to override some msgids if you
do that carefully. :-)
--
WBR, Dan Korostelev
___
Zope-Dev
to translate them every time. But it should be really easy for
applications to override them, so we'll have to work on that.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**
hange soon, so may be
we'll connect them to launchpad translation system as well.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding!
2009/2/11 Laurent Mignon :
> Stephan Richter wrote:
>> On Wednesday 11 February 2009, Dan Korostelev wrote:
>>>> Thanks for getting our attention on this. I consider this a show-stopper
>>>> for 2.0. Dan, let's think about something creative that allows us
2009/2/11 Stephan Richter :
> On Wednesday 11 February 2009, Dan Korostelev wrote:
>> Yeah. So one solution, as I said before is to release zope.sitecompat
>> egg that provides a "zope.site" module, but doesn't implement a site
>> implementation,
actions.update() for setup and actions.execute() for actual
execting) and that fact is used in MultiWidget and many custom forms.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross pos
ction handler to signal about that. Probably, a simple
boolean form instance variable will do the trick :)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
2009/2/21 Dan Korostelev :
> 2009/2/21 Roger Ineichen :
>> we should carefully review this part and probably
>> add action.update after action.execute. Right now, without looking
>> at the code I think we do not update actions after execute. Which
>> could end in bad a
times, but
now, as you are doing that, I'll be happy to help developing and
testing this package.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
e3" solution. However I'd like to see parts that are neither
zmi-specific nor plone-specific to be refactored to a separate
package. The ZopeStore from plone.openid, for example :-)
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.o
2009/2/24 Benji York :
> On Tue, Feb 24, 2009 at 8:29 AM, Dan Korostelev wrote:
>> 2009/2/24 Baiju M :
>>> Hi Dan,
>>>
>>> On Tue, Feb 24, 2009 at 6:40 PM, Dan Korostelev wrote:
>>>> Log message for revision 97207:
>>>> Creat
2009/2/24 Jim Fulton :
> I agree that it shouldn't go in zope.app. I believe I suggested
> putting this in zc.openid, although I'm fine with zope.openid.
Why zc? I thought it's only for packages coming from the zope
corporation. Or does Shane works for ZC? :)
--
2009/2/24 Shane Hathaway :
> Dan Korostelev wrote:
>>
>> 2009/2/24 Jim Fulton :
>>>
>>> I agree that it shouldn't go in zope.app. I believe I suggested
>>> putting this in zc.openid, although I'm fine with zope.openid.
>>
>&g
ut an additional refactoring strategy: we
could move ZMI-related packages to separate packages, like zmi.* or
something, leaving imports in zope.app.* and making zope.app.* really
deprecated. That way we can state that ZMI is not the Zope, but
something built on it. And this way gives us more refact
into the zope.pipeline? Like some resource injectors or XHTML slimmers
and so on. It would be really great to be able to do that with single
ZCML directive.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mail
ctory,
you'll rip most of them. However, some things, like trusted adapters
rewrap objects using ProxyFactory, so, maybe we could add some
modifier to the ProxyFactory function that just makes it return object
as is w/o wrapping. This way we could turn off proxies globally
without need to
onfiguration extensions, even if it has only one
directive now).
Jim, if you're fine with that, can you please give me rights for
zc.configuration on PYPI, my user name is "nadako".
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-
2009/2/26 Martijn Faassen :
> Dan Korostelev wrote:
>> The "exclude" directive provided by zc.configuration package is easy
>> to use and straightforward. I think it's used almost in every
>> zope-based application setup.
>
> I highly doubt so; I do
2009/2/26 Roger Ineichen :
>> (note though that including an extra "meta.zcml" can be
>> avoided if you make use of the z3c.autoinclude library)
>
> Oh, cool.
>
> Now we only need to find out how to write an z3c.autoexlude
> and a z3c.autooverride library
>
> Done, although, if you were me, you'd just leave it. :)
Thanks. I think we need to make people know that they don't need this
package anymore if they are looking for a way to exclude
configuration.
--
WBR, Dan Korostelev
___
Zope-D
about ITALNamespaceData
support? The contentprovider support won't be full without these
things.
2009/2/26 Dan Korostelev :
> Log message for revision 97320:
> Reenable z3c.pt tests, breaking tests again.
>
> Changed:
> U z3c.pagelet/trunk/src/z3c/pagelet/tests.py
>
> -
2009/2/27 Stephan Richter :
> On Friday 27 February 2009, Dan Korostelev wrote:
>> >> Also, I it
>> >> looks crazy how zope.i18n.locales things works, especially when it
>> >> comes to inheritance. :)
>> >
>> > Feel free to improve it.
2009/2/26 Martijn Faassen :
> Hey,
>
> On Thu, Feb 26, 2009 at 12:43 PM, Dan Korostelev wrote:
> [snip]
>>> (note though that including an extra "meta.zcml" can be avoided if you
>>> make use of the z3c.autoinclude library)
>>
>> Yep, I know abo
s, when it seems that most people
just build their own applications using their custom app configuration
files, I don't think that there's much sense for package-includes for
including components like zope.file. I can think of a use for
package-includes for some CMS
2009/3/4 Tres Seaver :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dan Korostelev wrote:
>> 2009/3/4 Tres Seaver :
>>> Log message for revision 97465:
>>> Branch removing zope.deferred.
>>>
>>>
>>> Changed:
>>
ndenices for
functionality that actually requires these dependencies, like
ZODB/hookable/etc.?
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
re on the development version anyway. :-)
(however, of course if would be nicer to do compattests before
merging, but this should'nt take much time?)
> I would also like to make 'setup.py test' actually work in the absence of
> bu
2009/3/4 Martijn Faassen :
> Dan Korostelev wrote:
>> 2009/3/4 Tres Seaver :
>>>>> Note that I'm not actually proposing that we merge this branch any time
>>>>> soon: it is a bit of a straw man for the ongoing process conversation.
>>>> Why
ramework" now), but
more about general development guidelines applied to any package in
zope svn (except the "migration" section, maybe), but I personally
don't have any objections, as it's still easy to find those docs and
that's the most important. :-)
--
WBR, Dan K
ll as compatibility imports in
the original package.
I'd volunteer to do that little refactorings, if noone objects.
--
WBR, Dan Korostelev
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross p
2009/3/5 Dan Korostelev :
> The zope.schema is also needed for the password
> manager vocabulary, but I'm not sure if the vocabulary should go to
> the new package, because it adds a dependency on zope.schema. What do
> people think?
Ah, I forgot that the password managers a
moving functionality extras. I still don't get how extras
are different from additional packages.
I'd also like to officially clear things about dependencies for zcml
configuration. Most of our packages can be used nicely without any
zcml, but the zcml-related dependencies can be quite la
annotation pattern, that was deprecated ages ago. If it's
like that, I'd like to remove that registration for
zope.principalannotation that is about to born as well as for
zope.annotation.
Can someone clarify this point?
--
WBR, Dan Korostelev
_
nly part of the "extras". Dividing this package also would have
> made no sense--it was already just a few small classes.
>
> For a package as central as zope.component, I think the pattern Tres
> is pursuing--dividing everything up--makes sense.
>
> For most other pac
1 - 100 of 166 matches
Mail list logo
