Christian Heimes added the comment:
The new patch adds new.boundcfunction as a replacement for
new.instancemethod(id, None, cls). I'm going to add docs if you like the
approach.
Added file: http://bugs.python.org/file8810/py3k_remove_newunbound2.patch
__
Tracker
Changes by Adam Olsen:
--
nosy: +rhamphoryncus
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1225584
_
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Guido van Rossum:
In http://bugs.python.org/issue1774369 I mentioned that I wanted to
rename __builtins__ to __rootns__. Though right now I think something
longer and less cryptic might be better. The reason is to avoid for
once and for all the confusion between
Changes by Christian Heimes:
--
keywords: +py3k
nosy: +tiran
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1498
__
___
Python-bugs-list mailing list
Unsubscribe:
Christian Heimes added the comment:
A simple replace with sed -i works just fine. Afterwards the code needs
only minor adjustments and cleanups.
find -name \*.py -or -name \*.c -or -name \*.h | xargs sed -i
's/__builtins__/__root__/g'
__
Tracker [EMAIL
Guido van Rossum added the comment:
OK, then we need to agree on a new name. I find __root__ too short,
__rootns__ too cryptic, and __root_namespace__ too long. :-) What else
have we got?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1498
Christian Heimes added the comment:
__origin__
__footing__
__radix__
__namespace__
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1498
__
___
Python-bugs-list mailing list
Georg Brandl added the comment:
Note though that the new module was deprecated once...
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1497
__
___
Python-bugs-list mailing list
Guido van Rossum added the comment:
OK. Some code review comments:
- Please clean up the comment in classobject.c starting with Method
objects are used for one purposes: -- to begin with, one purposes is
ungrammatical. Best to remove the (a) bullet and rephrase the whole
thing more like Method
Guido van Rossum added the comment:
Time for a quick poll on the list.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1498
__
___
Python-bugs-list mailing list
Unsubscribe:
Guido van Rossum added the comment:
BTW I'm okay with submitting this as is (plus docs and tests) and
tighten the spec later.
--
assignee: gvanrossum - georg.brandl
keywords: +patch, py3k
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1496
New submission from Achim Gaedke:
Regarding the compile() function in html/lib/built-in-funcs.html:
Please add a note about the exceptions raised by this function.
--
components: Documentation
messages: 57850
nosy: AchimGaedke
severity: minor
status: open
title: failure behaviour of
Bill Janssen added the comment:
No, the close must be removed. It's the wrong *way* to transfer
responsibility. Close means close, not I wash my hands of
responsibility here. What's hidden here is that the open socket is
transferred to the response, which continues to use it. In fact, the
New submission from Steve Jones:
See for yourself, on
http://docs.python.org/tut/node6.html
*
for n in range(2, 10):
... for x in range(2, n):
... if n % x == 0:
... print n, 'equals', x, '*', n/x
... break
... else:
Guido van Rossum added the comment:
Bill, is there a code example that should work but breaks because of
that close()? ATM, there doesn't seem to be anything in the tests that
breaks...
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1348
Guido van Rossum added the comment:
2 *is* a prime number.
--
nosy: +gvanrossum
resolution: - invalid
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1500
__
New submission from Jim Jewett:
http://docs.python.org/lib/typesnumeric.html contains a table listing the
mathematical operators. Please add a note to the final row (x ** y meaning
x to the power y) indicating that Python has chosen to define 0**0==1
Note 6: Python defines 0**0 to be 1.
Guido van Rossum added the comment:
So is this a Mac-only issue?
And couldn't the GIL state cleanup also invoke user code, which might be
abused to create more threads, wreaking havoc that way? I'm kind of
worried about putting this into 2.5.2 and breaking somebody's working
code (that's
Guido van Rossum added the comment:
(Can you also submit a doc fix that would have prevented issue 1500? :-)
--
nosy: +gvanrossum
priority: - low
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1501
__
Guido van Rossum added the comment:
I'm okay with adding this to 2.6 (and hence 3.0) but not with doing this
to 2.5.
--
nosy: +gvanrossum
priority: - low
resolution: - accepted
versions: -Python 2.4, Python 2.5, Python 3.0
__
Tracker [EMAIL PROTECTED]
Guido van Rossum added the comment:
I'm not sure I understand why anyone would ever want to send a 100
response anyway.
If I were to add support for this, I'd probably refactor send_response()
so that there's a lower-level function send_response_only() that *only*
sends the response header and
New submission from Chris Mellon:
One of the most common requests in c.l.p and #python is a way to break
an iterable up into some particular size chunks. For example, abcdef
- ab, cd, ef. It's pretty easy to write one, but there are a few
subtleties to it (like if you want padding or partial
Raymond Hettinger added the comment:
Sorry, this has been proposed and rejected previously. One of the
reasons was that the docs already have a C-speed recipe, grouper(),
that shows how to do it with padding and it is even simpler to do it
without padding using only zip() or izip(). Another
Raymond Hettinger added the comment:
FWIW, I find __root__ to be just right. It is not subject
misspelling. It is distinct enough to serve as a mental link to a
specific concept. The leading and trailing underscores cause just
enough typing pain that I wouldn't want anything longer.
New submission from Guido van Rossum:
See e.g.:
http://www.python.org/dev/buildbot/3.0/ppc%20Debian%20unstable%203.0/builds/303/step-test/0
Note how it fails the first time and passes on the re-run. I've seen
this before (just not on any of my own systems). I've also seen it fail
twice (on
Ronald Oussoren added the comment:
This is not a mac-specific issue, the script happens to be mac-specific
because that's how I found the issue.
Amaury's patch adds a unittest that reproduces the problem in a
platform-indepenent way using ctypes.
The _PyGILState_Fini function might cause
26 matches
Mail list logo