Re: zope.intid and zope.keyreference.interfaces.NotYet exception (patch)

"Roger" <[email protected]>
Newsgroups gmane.comp.web.zope.devel
Message-ID <[email protected]>
Hi Kirill

Why not just implement your own package and use this
enhanced IntIds utility from there in your project?

Regards
Roger Ineichen
_____________________________
END OF MESSAGE

> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:[email protected]] Im
Auftrag
> von Cykooz
> Gesendet: Dienstag, 10. Januar 2012 23:28
> An: zope-dev
> Betreff: [Zope-dev] zope.intid and zope.keyreference.interfaces.NotYet
exception
> (patch)
> 
> Hi,
> 
> I created a patch for a package zope.intid that almost completely
> solves the problem with the zope.keyreference.interfaces.NotYet
> exception.
> 
> I implemented a deferred indexing of objects added to the container
> which is not connected to the ZODB.
> As soon as the container is added to the ZODB - all deferred objects
> will be indexed.
> 
> I also added a marker IIntIdsDisabled for marking objects that must
> not be indexed.
> 
> 
> I would be grateful if someone could look at my changes and merge them
> into the main branch.
> My fork of zope.intid - https://bitbucket.org/cykooz/zope.intid/src
> 
> 
> PS: Sorry for my English.
> 
> -------------------
> Cykooz (Kirill Kuzminykh)
> _______________________________________________
> Zope-Dev maillist  -  [email protected]
> 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.zope.org/mailman/listinfo/zope )


_______________________________________________
Zope-Dev maillist  -  [email protected]
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.zope.org/mailman/listinfo/zope )
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.