New submission from Neal Norwitz:
def foo():
... if x:
... yield None
...
dis.dis(foo)
2 0 LOAD_GLOBAL 0 (x)
3 POP_JUMP_IF_FALSE 14
3 6 LOAD_CONST 0 (None)
9 YIELD_VALUE
10
New submission from Neal Norwitz:
def fo():
... if a:
... if b:
... if c:
...print
...
dis.dis(fo)
2 0 LOAD_GLOBAL 0 (a)
3 POP_JUMP_IF_FALSE 28
3 6 LOAD_GLOBAL 1 (b)
9 POP_JUMP_IF_FALSE
New submission from Neal Norwitz:
This problem goes back to 2.6 at least.
In Lib/cgi.py
FieldStorageClass = None
def read_multi(self, environ, keep_blank_values, strict_parsing):
Internal: read a part that is itself multipart.
ib = self.innerboundary
New submission from Neal Norwitz:
I was looking through code like this:
foo = '%s%s%s' % ('https://', host, uri)
and realized this could be rewritten by the interpreter as:
foo = 'https://%s%s' % (host, uri)
I tried to determine how much code this might affect, but it was pretty hard
Neal Norwitz nnorw...@gmail.com added the comment:
If this script isn't used any more, it should be removed.
On Fri, Jan 13, 2012 at 8:31 AM, Antoine Pitrou rep...@bugs.python.orgwrote:
Antoine Pitrou pit...@free.fr added the comment:
I think the script was used by the period regression
Neal Norwitz nnorw...@gmail.com added the comment:
There is some precedent for allowing minor differences in -O mode.
http://mail.python.org/pipermail/python-dev/2008-February/077193.html
I think we should push this to see how practical we can make it.
Dave, this is great work, I'm really
Neal Norwitz nnorw...@gmail.com added the comment:
Thanks for taking care of this guys. Sorry, I got swamped with mail
and had to archive 3,000+ messages. It looks like it's in good hands.
Let me know if there's anything you need. I may not have access to
the box anymore, however, I can
Neal Norwitz nnorw...@gmail.com added the comment:
Can you debug this problem any further? What is the C call stack? Does
the problem occur if you build in debug mode (./configure
--with-pydebug)? Does the problem occur with a different compiler (if
you have access to another one on the same
Neal Norwitz [EMAIL PROTECTED] added the comment:
The patch looks good.
These problems also apply to 2.5 I assume? You might want to ping MvL
to let him know since he's about to cut that release.
--
keywords: -needs review
nosy: +nnorwitz
New submission from Neal Norwitz [EMAIL PROTECTED]:
This happens on 2.4 and 3.0, probably all versions:
When running this simple program (save to a file):
print(type(__builtins__))
__import__(__file__.split('/')[-1][:-3])
I get:
type 'module'
type 'dict'
I would expect the type
Neal Norwitz [EMAIL PROTECTED] added the comment:
Interesting approach. I was surprised to see the change to the AST, but
I understand why you did it. I think if the AST optimization approach
works out well, we will want to have some more general mechanism to
communicate these optimization
Neal Norwitz [EMAIL PROTECTED] added the comment:
The only one that is probably an issue based on Antoine's info is:
test_unicode leaked [1, 1] references, sum=2
I've seen test_urllib2_localnet leak 3 before. I don't know that it's
a real leak. I'm pretty sure it is not a regression though
Neal Norwitz [EMAIL PROTECTED] added the comment:
This may not be a real release blocker, but I want to raise the
priority. It is a regression and we should try to fix it, especially if
it's easy.
--
priority: normal - release blocker
___
Python
Neal Norwitz [EMAIL PROTECTED] added the comment:
It seems that if the tests are run in this order:
./python -E -tt ./Lib/test/regrtest.py -u all test_xmlrpc test_ctypes
test_json test_bsddb3 test_pickletools
The error will trigger consistently. That is in 2.6 with a debug build
on a dual cpu
New submission from Neal Norwitz [EMAIL PROTECTED]:
test_pickletools fails sporadically on at least two platforms I've seen.
http://www.python.org/dev/buildbot/all/x86%20gentoo%20trunk/builds/4120/step-test/0
http://www.python.org/dev/buildbot/all/ppc%20Debian%20unstable%20trunk/builds/1908
Neal Norwitz [EMAIL PROTECTED] added the comment:
Committed revision 66009.
--
assignee: - nnorwitz
resolution: - fixed
status: open - closed
type: - security
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3627
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
priority: critical - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2744
___
___
Python
New submission from Neal Norwitz [EMAIL PROTECTED]:
Even after adding the current patch in http://bugs.python.org/issue3651
there are many reference leaks. This bug can be a placeholder for all
the reference leaks returned from:
./python ./Lib/test/regrtest.py -R 3:2 -uall,-bsddb
Neal Norwitz [EMAIL PROTECTED] added the comment:
I fixed some problems in r66016. This patch seems like it has other
things which might be useful, so I'll keep it open until it's handled.
--
nosy: +nnorwitz
___
Python tracker [EMAIL PROTECTED]
http
Neal Norwitz [EMAIL PROTECTED] added the comment:
Another PyBuffer_Release(pin); looks necessary at @@ -805,6 +807,7 @@.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3651
Neal Norwitz [EMAIL PROTECTED] added the comment:
In 3.0 the free is necessary, though see http://bugs.python.org/issue3662 .
--
nosy: +nnorwitz
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3304
Neal Norwitz [EMAIL PROTECTED] added the comment:
Daniel, thanks for running the fuzzer! It would be great if you could
keep running it and find any more problems before releasing 2.6 and 3.0.
I agree with Benjamin and Amaury. PyArg_ParseTupleAndKeywords()
shouldn't update the pointer
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1375
___
___
Python-bugs-list
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - feature request
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2456
___
___
Python-bugs-list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Is this still a problem?
--
nosy: +nnorwitz
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1210
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1658
___
___
Python-bugs-list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Is this still a problem?
--
nosy: +nnorwitz
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1840
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2747
___
___
Python-bugs-list
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
type: crash - behavior
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2562
___
___
Python-bugs-list
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
assignee: - theller
components: +ctypes -Extension Modules
nosy: +theller
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1838
Neal Norwitz [EMAIL PROTECTED] added the comment:
The valgrind errors below are possibly related.
Conditional jump or move depends on uninitialised value(s)
PyUnicodeUCS2_EncodeUTF8 (unicodeobject.c:2216)
_PyUnicode_AsString (unicodeobject.c:1417)
save (_pickle.c:930)
Pickler_dump
Neal Norwitz [EMAIL PROTECTED] added the comment:
Also there should be a Misc/NEWS entry added. Also check the doc to see
it needs updating wrt ownership.
--
type: - resource usage
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org
Neal Norwitz [EMAIL PROTECTED] added the comment:
Indeed. The problem was an incorrect conversion of str - unicode,
instead of converting to bytes. On getting the buffer from unicode, it
tried to read data which was uninitialized.
Hmmm, this fix is for 3.0 only, but the problem is happening
New submission from Neal Norwitz [EMAIL PROTECTED]:
The attached patch against 2.6 fixes the memory leaks reported against
the bsddb module. There are still (probably) reference leaks.
Jesus, it would be great if you can look at this before the release.
--
assignee: jcea
components
New submission from Neal Norwitz [EMAIL PROTECTED]:
Some of these leaks reported by valgrind are likely duplicates. I don't
know how many individual cases of these leaks there are.
11,119 bytes in 14 blocks are possibly lost in loss record 86 of 119
realloc (vg_replace_malloc.c:429
Neal Norwitz [EMAIL PROTECTED] added the comment:
There are also tons of reference leaks when running regrtest.py with -R.
Even code as simple as this leaks:
eval('1')
1
[40731 refs]
eval('1')
1
[40732 refs]
eval('1')
1
[40733 refs]
eval('1')
1
[40734 refs]
eval('1')
1
[40735 refs
Neal Norwitz [EMAIL PROTECTED] added the comment:
This is a partial (or complete) duplicate of 3656.
--
nosy: +nnorwitz
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3651
Neal Norwitz [EMAIL PROTECTED] added the comment:
This is a partial (or complete) duplicate of 3651.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3656
New submission from Neal Norwitz [EMAIL PROTECTED]:
The trunk revision was 65335.
--
components: Interpreter Core
messages: 71608
nosy: nnorwitz
priority: release blocker
severity: normal
status: open
title: apple security patches need to be forward ported to py3k
versions: Python 3.0
Neal Norwitz [EMAIL PROTECTED] added the comment:
Committed revision 65261 for 2.5
Committed revision 65262 for 2.4.
--
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2620
Neal Norwitz [EMAIL PROTECTED] added the comment:
I'd like to clarify the approach to fixing these types of problems.
...
However, I like constricting it to AttributeError only as that would
make it much less confusing. This might be something to bring up on
python-dev.
I suspect
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
priority: normal - critical
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue
__
___
Python-bugs-list mailing list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Why not use the normal recursion check mechanism? Specifically,
if (Py_EnterRecursiveCall(unicode % ))
return NULL;
// err = Warn();
Py_LeaveRecursiveCall();
I don't see where the problem with threads comes
Neal Norwitz [EMAIL PROTECTED] added the comment:
I think `uname -m` will be equal to alpha in this case. There are
several uses of `uname -m` in configure.in. You might need to add a
new section. It might also be possible to clean up various special
cases to make a generic `uname -m` section
Neal Norwitz [EMAIL PROTECTED] added the comment:
What is the status of this bug? AFAICT, the code is now correct. Have
the doc changes been applied? The resolution on this report should be
updated too. It's currently rejected.
--
nosy: +nnorwitz
Neal Norwitz [EMAIL PROTECTED] added the comment:
Bumping the priority. I'd like to see this fixed before the next
release. What version(s) does this problem apply to: 2.5, 2.6, 3.0?
--
nosy: +nnorwitz
priority: critical - release blocker
__
Tracker
Neal Norwitz [EMAIL PROTECTED] added the comment:
So if the fix was applied to 2.5 branch and 2.6 (3.0 should have
picked up from 2.6 automatically), can we close this bug?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2601
Neal Norwitz [EMAIL PROTECTED] added the comment:
I think this will be fairly difficult to set up. If the clean buildstep
had been executed, you would have to rerun configure and compile before
you can run any tests.
We could re-order and do clean first. That would leave all the build
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
assignee: amaury.forgeotdarc - gvanrossum
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2235
__
___
Python-bugs-list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Trent, go ahead and try this out. We should definitely be moving in
this direction. So I'd rather fix the problem than keep suffering with
the current problems of not being able to run the test suite
concurrently. I think bind_port might
Neal Norwitz [EMAIL PROTECTED] added the comment:
I think this was a module that I skipped. I think Anthony might have
had a patch, but if we have a fix, I'm not sure it matters. We need to
fix this for 2.5.3, upping the priority.
--
nosy: +anthonybaxter
priority: high - release
Neal Norwitz [EMAIL PROTECTED] added the comment:
Gerhard, could you take a look?
--
assignee: - ghaering
nosy: +ghaering, nnorwitz
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2515
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
priority: - release blocker
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2515
__
___
Python-bugs-list mailing list
Neal Norwitz [EMAIL PROTECTED] added the comment:
Eric, could you take a look?
--
assignee: - eric.smith
nosy: +eric.smith, nnorwitz
priority: - high
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2526
Neal Norwitz [EMAIL PROTECTED] added the comment:
I'm setting the priority to release blocker for now. George, please
provide a way for us to reproduce with a stock python (ie, no third
party extensions). Thanks.
--
nosy: +nnorwitz
priority: - release blocker
Neal Norwitz [EMAIL PROTECTED] added the comment:
Brett, didn't you have a similar problem you fixed a while ago? I
assigned to you for more input, feel free to reset to nobody.
--
assignee: - brett.cannon
nosy: +brett.cannon, nnorwitz
priority: - release blocker
Neal Norwitz [EMAIL PROTECTED] added the comment:
Travis, could you take a look?
--
assignee: - teoliphant
nosy: +nnorwitz, teoliphant
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2538
Neal Norwitz [EMAIL PROTECTED] added the comment:
On Tue, Apr 1, 2008 at 6:14 AM, Brett Cannon [EMAIL PROTECTED] wrote:
Brett Cannon [EMAIL PROTECTED] added the comment:
Neal's issues are addressed in this patch. I also finally filled out
warnings.h. The only thing that I didn't deal
Neal Norwitz [EMAIL PROTECTED] added the comment:
I didn't realize this was waiting for me. You should have just checked
it in, that would have gotten me to review faster. :-)
pythonrun.c:
* Should PyModule_GetWarningsModule() return a valid pointer?
* The code below crashes. Need
Neal Norwitz [EMAIL PROTECTED] added the comment:
Ugh. The manpage for accept on Ubuntu 6.10 says:
On Linux, the new socket returned by accept() does not inherit file
status flags such as O_NONBLOCK and O_ASYNC from the listening socket.
This behaviour differs from the canonical BSD
Neal Norwitz [EMAIL PROTECTED] added the comment:
Christian checked this in a few days ago in r61953 and a few other
revisions.
--
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2477
Neal Norwitz [EMAIL PROTECTED] added the comment:
Antoine, I hope to look at this patch eventually. Unfortunately, there
are too many build/test problems that need to be resolved before the
next release. If you can help out with those, I will be able to review
this patch sooner
New submission from Neal Norwitz [EMAIL PROTECTED]:
This is a patch that modifies the parser to allow getting the future
import flags into the AST. There are 2 approaches that are embedded
within the patch. Both approaches can be seen in Python/pythonrun.c.
1) update_flags_from_node
New submission from Neal Norwitz [EMAIL PROTECTED]:
The attached file has a snapshot of the python.org homepage that was
causing test_urllibnet to fail on some platforms (2 sparc, and ia64 at
least), but not other platforms. This should be handled consistently.
I don't know if there are really
New submission from Neal Norwitz [EMAIL PROTECTED]:
r61837 removed the dl module. It needs a 2to3 fixer written to use ctypes.
--
assignee: collinwinter
components: 2to3 (2.x to 3.0 conversion tool)
messages: 64394
nosy: collinwinter, nnorwitz
priority: critical
severity: normal
status
Neal Norwitz [EMAIL PROTECTED] added the comment:
StandardError has been removed from Python 3.0. It's use is deprecated.
Instead of catching StandardError, do:
try:
# ...
except Exception:
# ...
--
assignee: loewis - nnorwitz
nosy: +nnorwitz
resolution: - out of date
Neal Norwitz [EMAIL PROTECTED] added the comment:
Ya, I'll get around to it...hopefully soon. But if someone wants to
do it for me, I won't complain. :-)
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2183
New submission from Neal Norwitz [EMAIL PROTECTED]:
Explicit relative imports using from .foo import * should work.
http://mail.python.org/pipermail/python-3000/2008-March/012564.html
--
components: Interpreter Core
messages: 63942
nosy: nnorwitz
priority: critical
severity: normal
New submission from Neal Norwitz [EMAIL PROTECTED]:
Guido mentioned this in python-3000-checkins. I agree the problem
should be fixed.
I think the automatic skip on ImportError is harmful.
We should add a helper function to test_support so that you can write
foobar
New submission from Neal Norwitz [EMAIL PROTECTED]:
This patch returns more memory to the system when doing:
x = [unicode(i) for i in xrange(100)]
del x
If the above code is done, the memory before and after is quite
different. After this patch, the memory of the process as reported
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
assignee: - nnorwitz
nosy: +nnorwitz
priority: - urgent
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2375
Neal Norwitz [EMAIL PROTECTED] added the comment:
After discussing this with MvL, I'll check this patch into trunk and
2.5. Alec, if you find other issues, please create a new patch.
Committed revision 61458.
Committed revision 61485. (2.5)
__
Tracker [EMAIL
Changes by Neal Norwitz [EMAIL PROTECTED]:
--
assignee: - nnorwitz
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2321
Changes by Neal Norwitz [EMAIL PROTECTED]:
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2321
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman
Neal Norwitz [EMAIL PROTECTED] added the comment:
Committed revision 61492.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2332
Neal Norwitz [EMAIL PROTECTED] added the comment:
See PEP 352. Currently this is slated for python 2.8. Perhaps the
schedule should be sped up a bit in light the current release schedule.
Brett, any comments? We should add all the warnings from PEP 352 with
the -3 flag to 2.6
Neal Norwitz [EMAIL PROTECTED] added the comment:
Marshal is the wrong place for this sort of thing (the code object is
where it should be done).
I botched the analysis. The case is common, but only for the empty
tuple which I forgot to ignore. (None,) was a common case when I
measured
Neal Norwitz [EMAIL PROTECTED] added the comment:
I bet with just a little more work, you could get rid of t and stream.
t is only used for a single set of opcodes (STORE_SLICE+n). stream is
only used for the PRINT opcodes. The code in print could be moved to a
function which might allow
Neal Norwitz [EMAIL PROTECTED] added the comment:
Can't next_instr and stack_pointer move inside the for loop too?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2262
Neal Norwitz added the comment:
I suppose you are aware that performing this optimization in general
would break a lot of existing code that uses inspect.getstack() or
sys._getframe() to peek at the caller's local variables. I know this
Yes, with this optimization the variable might
New submission from Neal Norwitz:
This patch optimizes code like:
x = any_expression
return x
to:
return any_expression
Currently it only optimizes out the local variable if there is a return
because it can't determine if this is the last use of the variable or not.
This shouldn't
Neal Norwitz added the comment:
I forgot to mention that if another loop was added to PyCode_Optimize
that kept track of the # of times each local variable was
LOAD_FAST/STORE_FAST/DELETE_FAST and that the count was 2, we could
perform a similar optimization without requiring the return.
Bonus
New submission from Neal Norwitz:
Optimize list comprehensions by using the list on the stack, rather than
storing in a (local/global) variable. This reduces the size of the
stack by one pointer, reduces the bytecode size by 8, and reduces the
iterations in the eval loop by 2 + # of iterations
Neal Norwitz added the comment:
I forgot to mention that if another loop was added to PyCode_Optimize
that kept track of the # of times each local variable was
LOAD_FAST/STORE_FAST/DELETE_FAST and that the count was 2, we could
perform a similar optimization without requiring the return.
Bonus
Neal Norwitz added the comment:
It would be great to see test cases with this change. That would help
answer Alexander's question too.
--
nosy: +nnorwitz
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1394
New submission from Neal Norwitz:
Various bits are often duplicated in code objects. For example,
sometimes names and varnames are equal. In this case, we don't need two
objects since they are both const. This patch implements a trivial fix
for this case. However, there are more cases. We
Neal Norwitz added the comment:
Guido says to do it only with -O.
http://mail.python.org/pipermail/python-dev/2008-February/077193.html
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2181
Neal Norwitz added the comment:
Christian,
Could you clean this patch up? Specifically:
* Put everything into one patch
* Eliminate unnecessary changes (changing variable name or whitespace)
* Conform to the style in the file
* Verify all the tests run with regrtest.py -u all when built
New submission from Neal Norwitz:
Georg, I hope you don't mind me assigning this to you. Feel free to
unassign. A colleague pointed me to section 5.7 in the old ref doc:
http://docs.python.org/ref/shifting.html
It says that shifting operations lose data on overflow. This info is
outdated
Neal Norwitz added the comment:
I think sys is appropriate for clearing the cache. Lib/test/regrtest.py
still has a reference to gc rather than sys.
Why do the CompactFreeList APIs return an int that is always 0? Seems
like they should return a real value or be void.
I'm not sure why you
Neal Norwitz added the comment:
I was hoping you could get rid of my entire hack. I didn't (still
don't) completely understand the intention of the code, so can't really
offer any more advice. IMO, the patch is an improvement so you should
check it in.
--
assignee: nnorwitz
Neal Norwitz added the comment:
I just added -Wstrict-overflow to the code in sysmodule.c
(sys_getframe) and tried with gcc 4.2.1. It doesn't warn. I wonder
if 4.3 is more picky or warns when it shouldn't?
Unless if I changed the code so it doesn't work:
typedef struct {int ref;} PyObject
Neal Norwitz added the comment:
On Jan 27, 2008 6:45 PM, Ismail Donmez [EMAIL PROTECTED] wrote:
Can you try with -Wstrict-overflow=3 , but yes I am using gcc 4.3 trunk.
I just tried with =1, =2, =3, and no =. All the same result: no warning.
Ismail, thanks for going through all this effort
Changes by Neal Norwitz:
--
nosy: +nnorwitz
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1621
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Changes by Neal Norwitz:
--
nosy: +nnorwitz
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1303614
_
___
Python-bugs-list mailing list
Unsubscribe:
http
Neal Norwitz added the comment:
I looked at Guido's latest deldict.diff patch--the one to
Objects/object.c only. It seems good. I can't convince myself either
way about the change to Objects/typeobject.c. I can't think of a way
to cause a problem. It seems safer to use Py_CLEAR in this case
Neal Norwitz added the comment:
This started happening consistently on my box and I was able to
reproduce it. Revision 60233 should fix this problem. I forwarded the
checkin to Greg. Hopefully he can comment if there is a problem. (Also
cc'd him on this bug report that I'm now closing
Neal Norwitz added the comment:
This may happen every time on the MIPS buildbot. Here is a recent run.
http://www.python.org/dev/buildbot/all/MIPS%20Debian%20trunk/builds/190/step-test/0
My guess is that there is some exception happening in C code and that
propagates back up to the error we
Neal Norwitz added the comment:
Nick, can you backport this and add a NEWS entry? Thanks.
--
nosy: +nnorwitz
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1705170
Neal Norwitz added the comment:
I don't have access to a 10.5 machine. My guess is that the difference
is between configure not setting _XOPEN_SOURCE and/or
_XOPEN_SOURCE_EXTENDED and it being set in pyconfig.h. At least those
are both defined on 10.4.
This page talks about needing
1 - 100 of 122 matches
Mail list logo