[Zope3-dev] Re: zope.app.schema (and other junk)

Jim Fulton jim at zope.com
Tue Jul 18 06:28:21 EDT 2006


On Jul 18, 2006, at 6:16 AM, Philipp von Weitershausen wrote:

> Jim Fulton wrote:
>> -=-
>> Modified: Zope3/branches/3.3/doc/CHANGES.txt
>> ===================================================================
>> --- Zope3/branches/3.3/doc/CHANGES.txt	2006-07-17 19:24:19 UTC  
>> (rev 69162)
>> +++ Zope3/branches/3.3/doc/CHANGES.txt	2006-07-17 19:26:12 UTC  
>> (rev 69163)
>> @@ -10,6 +10,10 @@
>>
>>      Bugfixes
>>
>> +      - Fixed issue 604, Mutable schemas were accidentally  
>> included in
>> +        the 3.2 release even though they weren't ready and didn't
>> +        work. They are not included in the 3.3 release.
>> +
>
> I see you've removed the zope.app.schema package from the release. I
> don't think we can do that. The vocabulary registry that looks up
> vocabularies as utilities is located in there
> (zope.app.schema.vocabulary). It's a vital part for Zope 3.

Hm. Why?  I don't really want something that is just an alternate
spelling for getUtility? Does it provide any value beside looking up
a utility?

> The (now
> deprecated) 'vocabulary' ZCML directive is also defined there, we need
> it for BBB.

Right.  I noticed that there were lots of tests failing in the release
and I feared it had something to do with this.  Since I couldn't
even make a release as things stood, I decided not to worry about it  
for now.


> I suggest we remove everything that has to do with mutable schemas
> somewhere else (zope.mutableschema?) and leave zope.app.schema in the
> release. Alternatively, we can move the two items I mentioned above to
> zope.schema and indeed get rid of zope.app.schema in the release.

OK, I suggest we move the zope.mutable schema out, or even remove it.
I actually porefer removing it.  It will still be in the  
repositoiry.  I don't want to
create a new mysterious directory with non-working code.

>
> P.S.: Btw, there's lots of junk lurking in zope.app that we aren't
> shipping and I don't see anyone stepping up to fix some of this
> bitrotten code (it's been there since the pre-X3.0 days). Perhaps it's
> time to move all of this out of zope.app, or even the Zope 3 tree
> altogether?

Yes, but let's get through the "June" release first. :/

Jim

--
Jim Fulton			mailto:jim at zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org





More information about the Zope3-dev mailing list