Log message for revision 122436:
revert changes
Changed:
U Zope/branches/2.13/src/OFS/ObjectManager.py
U Zope/branches/2.13/src/Products/PageTemplates/Expressions.py
U Zope/branches/2.13/src/ZPublisher/HTTPRequest.py
-=-
Modified: Zope/branches/2.13/src/OFS/ObjectManager.py
Log message for revision 122429:
micro optimizations
Changed:
U Zope/branches/2.13/src/OFS/PropertyManager.py
U Zope/branches/2.13/src/OFS/Traversable.py
U Zope/branches/2.13/src/ZPublisher/HTTPRequest.py
-=-
Modified: Zope/branches/2.13/src/OFS/PropertyManager.py
Log message for revision 122279:
replace map/lambda with list comprehension
Changed:
U Zope/branches/2.13/src/App/ApplicationManager.py
U Zope/branches/2.13/src/App/CacheManager.py
U Zope/branches/2.13/src/OFS/Cache.py
U Zope/branches/2.13/src/OFS/CopySupport.py
U
Log message for revision 122280:
chameleon compatibility
Changed:
U Zope/trunk/src/Products/SiteErrorLog/www/main.pt
U Zope/trunk/src/Products/SiteErrorLog/www/showEntry.pt
-=-
Modified: Zope/trunk/src/Products/SiteErrorLog/www/main.pt
Log message for revision 122282:
replace map+lambda with list comprehensions
Changed:
U Zope/trunk/src/App/CacheManager.py
U Zope/trunk/src/OFS/Cache.py
U Zope/trunk/src/OFS/CopySupport.py
U Zope/trunk/src/OFS/ObjectManager.py
U Zope/trunk/src/OFS/PropertyManager.py
U
Log message for revision 122286:
micro optimization
Changed:
U Zope/branches/2.13/src/App/ApplicationManager.py
U Zope/branches/2.13/src/App/ImageFile.py
U Zope/branches/2.13/src/App/special_dtml.py
U Zope/branches/2.13/src/OFS/Application.py
U
Log message for revision 122247:
chameleon compatibility
Changed:
U Zope/branches/2.13/src/Products/SiteErrorLog/www/main.pt
-=-
Modified: Zope/branches/2.13/src/Products/SiteErrorLog/www/main.pt
===
---
Log message for revision 122248:
chameleon compatibility
Changed:
U Zope/branches/2.13/src/Products/SiteErrorLog/www/showEntry.pt
-=-
Modified: Zope/branches/2.13/src/Products/SiteErrorLog/www/showEntry.pt
===
---
Log message for revision 122249:
changelog updated
Changed:
U Zope/branches/2.13/doc/CHANGES.rst
-=-
Modified: Zope/branches/2.13/doc/CHANGES.rst
===
--- Zope/branches/2.13/doc/CHANGES.rst 2011-07-14 18:43:27 UTC (rev 122248)
Log message for revision 122161:
replace has_key with in operator
Changed:
U Zope/branches/2.13/src/App/ApplicationManager.py
U Zope/branches/2.13/src/App/ProductContext.py
U Zope/branches/2.13/src/App/ProductRegistry.py
U Zope/branches/2.13/src/App/special_dtml.py
U
Log message for revision 121950:
remove testing code
Changed:
U Zope/trunk/src/OFS/Traversable.py
-=-
Modified: Zope/trunk/src/OFS/Traversable.py
===
--- Zope/trunk/src/OFS/Traversable.py 2011-06-15 14:12:27 UTC (rev 121949)
Log message for revision 121936:
optimize access to product packages
Changed:
U Zope/trunk/src/App/FactoryDispatcher.py
-=-
Modified: Zope/trunk/src/App/FactoryDispatcher.py
===
--- Zope/trunk/src/App/FactoryDispatcher.py
Log message for revision 121937:
relace has_key call with 'in' operator
Changed:
U Zope/trunk/src/App/ApplicationManager.py
U Zope/trunk/src/App/ProductContext.py
U Zope/trunk/src/App/ProductRegistry.py
U Zope/trunk/src/App/special_dtml.py
U Zope/trunk/src/OFS/Image.py
U
Log message for revision 121561:
create brnach for acquisition work
Changed:
A Zope/branches/fafhrd-no-acquisition/
-=-
___
Zope-Checkins maillist - Zope-Checkins@zope.org
https://mail.zope.org/mailman/listinfo/zope-checkins
I'm aware of this but it kind of defeats the idea of seperating code and
configuration...
So, other ideas?
create new zcml directive.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross
On Tue, 2008-04-15 at 17:37 +0200, Roger Ineichen wrote:
The other option whould be to split every widget into it's own
package and use z3c.widget as namespace package.
What do you think?
i think we should split z3c.schema and z3c.widget to separate packages,
so we can have one namespace
On Tue, 2008-04-15 at 16:14 +0200, Christian Zagrodnick wrote:
Hi,
I'd need a zope.schema field for blobs. Should this go directly to
zope.schema or some third party package?
there is z3c.schema package for various third party packages
___
Hello,
Seem zc.recipe.filestorage has bug in blob-dir
for this buildout config
[var]
recipe = zc.recipe.filestorage
blob-dir = parts/varblobs
zc.recipe.filestorage generates
zodb
blobstorage
blob-dir ../parts/varblobs
shared-blob-dir no
filestorage
path
Hi all,
Who is author of z3c.blobfile package? Could anybody make release?
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
On Unix-like systems, we can use `os.fork()`. The advantage of this approach
is that I can use OS system calls to kill the process. However, ZODB database
storages cannot be shared between processes. Nikolay Kim has done some
preliminary experiments and found that `db.open()` locks
Hi Alan,
i'm author of ZopeScheduler product, lets coordinate our work
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
it'll be open source.
source in attach.
it not very usefull without additional products that must actually
handle emails.
now i'm working on mail storage products.
Ooh! This is really cool. Will this be open source? I'll be a lot of people
will be interested in this.
-Fred
Thanks Fred!
all works well.
P.S. i'm developing smtp server for zope and already have working code.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
is there any way create server for new protocol without changing ZServer
module?
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
You must implement the server for the new protocol
and you will need some integration code.
You have lots of examples at hand.
write server itself not very hard, i simply don't want patch
ZServer/components.xml
is there any way don't touch Zserver?
25 matches
Mail list logo