At 09:27 PM 7/23/2006 -0700, Brett Cannon wrote:
On 7/23/06, Phillip J. Eby
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] wrote:
one proxy plus one namechecker equals one capability. In other words,
you could take the restricted interpreter, the proxy mechanism, and the
namechecker and leave most of
On 7/23/06, Phillip J. Eby [EMAIL PROTECTED] wrote:
At 09:27 PM 7/23/2006 -0700, Brett Cannon wrote:When I say name checker I mean the Zope type that allows you to specify alist of names that are allowed for a given object.This allowing is not
based on identity or code signing or anything like
James Y Knight [EMAIL PROTECTED] wrote:
To cut a long story short, it is impractical for a language run-time
system to call user-defined handlers with any degree of reliability
unless the compiled code and run-time interoperate carefully - I have
been there and done that many times, but
Brett Cannon wrote:
On 7/23/06, *Armin Rigo* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Also, I hate to sound self-centered, but I should point out somewhere
that PyPy was started by people who no longer wanted to maintain a fork
of CPython, and preferred to work on building
Hi Giovanni,
On Sun, Jul 23, 2006 at 03:30:50PM +0200, Giovanni Bajo wrote:
I'm not sure big-O tells the whole truth. For instance, do we want to allow
an implementation to use a hash table as underlying type for a list? It
would match big-O requirements, but would still be slower than a plain
The CanDo developers are sprinting for three days starting on this
coming Friday, so there's space available for a Python sprint. I'll
try to attend at least on Saturday (Sunday may not be possible for
me). Does anyone want to come and work on Python stuff? If yes,
please add your name to
At 12:50 AM 7/24/2006 -0700, Brett Cannon wrote:
OK, then I need something clarified. If you read
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/TransitionToSecurityProxieshttp://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/TransitionToSecurityProxies
, it talks
I'm cross-compiling Python using uClibc buildroot, which installs target include
files and libraries to a directory like ~/toolchain rather than /usr. I
couldn't figure out any way to convincing the top-level python/setup.py to look
in ~/toolchain instead of /usr when detecting what modules to
Greg Ewing [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Joe Smith wrote:
Microsoft as a general rule, does not go after people distributing
products
that Microsoft has labeled
free, even after Microsoft no longer distributes that product.
But if the licence agreement
Joe Smith [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Neil Hodgson [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Trent Nelson:
I ended up playing around with Profile Guided Optimization, running
``python.exe pystones.py'' to collect call-graph data after
Between the two of you, I think you have made the case that the language
specification is better to not include such details. As you both note,
it is difficult to capture the essence of what is desired from the
performance of the implementation. To tag on other version, what about
Big-O space
At 12:04 PM 7/25/2006 +1200, Greg Ewing wrote:
Phillip J. Eby wrote:
When I say name checker I mean the Zope type that allows you to
specify a
list of names that are allowed for a given object. This allowing is not
based on identity or code signing or anything like that. It's just a
Phillip J. Eby wrote:
At 12:04 PM 7/25/2006 +1200, Greg Ewing wrote:
Phillip J. Eby wrote:
When I say name checker I mean the Zope type that allows you to specify
a list of names that are allowed for a given object. This allowing is not
based on identity or code signing or anything like that.
There are still a bunch of outstanding bugs. rc1 is about a week away
and it would be great to fix these. Many of these are also present in
2.4, but it would be nice to squash them in 2.5. Here's the list from
PEP 356:
http://python.org/sf/1526585 - SystemError concat long strings
I've fixed most of the problems (or determined they weren't problems)
from all the warnings issued by Klocwork's static analysis tool. The
following are outstanding issues.
This first group looks like real problems to me:
# 74 Object/funcobject.c:143Suspicious deref of ptr before NULL check
Neal Norwitz wrote:
http://python.org/sf/1513611 - XML: xml.sax.expatreader missing
It would be great to fix *all* of these. In this list, at least 3
(4?) can cause segfaults, and #1521947 can cause incorrect results.
IMO, 1513611 should block the release, since it's a regression
16 matches
Mail list logo
