--On 5. Juli 2006 18:56:25 +0200 Florent Guillaume [EMAIL PROTECTED] wrote:
Is anyone opposed to me removing the stupid:
_getattr = getattr
_none = None
marker = _marker
local namespace optimizations that are found in
unrestrictedTraverse?
I am pretty sure that
On 5 Jul 2006, at 19:05, Andreas Jung wrote:
--On 5. Juli 2006 18:56:25 +0200 Florent Guillaume [EMAIL PROTECTED]
wrote:
Is anyone opposed to me removing the stupid:
_getattr = getattr
_none = None
marker = _marker
local namespace optimizations that are found in
--On 5. Juli 2006 19:11:16 +0200 Florent Guillaume [EMAIL PROTECTED] wrote:
On 5 Jul 2006, at 19:05, Andreas Jung wrote:
--On 5. Juli 2006 18:56:25 +0200 Florent Guillaume [EMAIL PROTECTED]
wrote:
Is anyone opposed to me removing the stupid:
_getattr = getattr
_none =
Florent Guillaume wrote:
Is anyone opposed to me removing the stupid:
_getattr = getattr
_none = None
marker = _marker
local namespace optimizations that are found in unrestrictedTraverse?
I find these things rather confusing when looking at zope core code, and
always
On Wed, Jul 05, 2006 at 07:21:29PM +0200, Andreas Jung wrote:
| Does that mean you're for or against it?
|
|
| For (of course) :-)
It has been demonstrated in other lists that global lookups are most
of the time faster than local lookups in recent versions of python.
--
Sidnei da Silva
--On 5. Juli 2006 16:45:21 -0300 Sidnei da Silva [EMAIL PROTECTED]
wrote:
On Wed, Jul 05, 2006 at 07:21:29PM +0200, Andreas Jung wrote:
| Does that mean you're for or against it?
|
|
| For (of course) :-)
It has been demonstrated in other lists that global lookups are most
of the time
Sidnei da Silva wrote at 2006-7-5 16:45 -0300:
...
It has been demonstrated in other lists that global lookups are most
of the time faster than local lookups in recent versions of python.
That would extremely surprise me:
While global lookup was significantly optimized,
it is still an
Florent Guillaume wrote at 2006-7-5 18:56 +0200:
Is anyone opposed to me removing the stupid:
_getattr = getattr
_none = None
marker = _marker
local namespace optimizations that are found in
unrestrictedTraverse?
Why do you think they were stupid?
They do save time
On Wed, Jul 05, 2006 at 10:29:34PM +0200, [EMAIL PROTECTED] wrote:
| That would extremely surprise me:
|
| While global lookup was significantly optimized,
| it is still an lookup with a string as argument.
|
| For local lookup on the other hand, the compiler has
| turned the name into
...and then I find it. Phew :)
http://article.gmane.org/gmane.comp.web.zope.devel/8925
--
Sidnei da Silva
Enfold Systemshttp://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
___
Zope-Dev maillist -
Sidnei da Silva wrote at 2006-7-5 18:06 -0300:
...and then I find it. Phew :)
http://article.gmane.org/gmane.comp.web.zope.devel/8925
But you see that this post does not compare local versus global
access but cell reference in enclosing (!) scope versus global access.
As my example proves,
On Wed, Jul 05, 2006 at 11:30:19PM +0200, [EMAIL PROTECTED] wrote:
| Sidnei da Silva wrote at 2006-7-5 18:06 -0300:
| ...and then I find it. Phew :)
|
| http://article.gmane.org/gmane.comp.web.zope.devel/8925
|
| But you see that this post does not compare local versus global
| access but cell
12 matches
Mail list logo
