Dave Malcolm added the comment:
I renamed it from sys.breakpoint to sys._breakpoint, since this is
CPython-specific
--
title: Add Py_BREAKPOINT and sys.breakpoint hooks -> Add Py_BREAKPOINT and
sys._breakpoint hooks
___
Python tracker
&l
New submission from Dave Malcolm :
Issue 5793 rationalized all usage of C "character" handling to use
"Py_"-prefixed locale-unaware macros, at the "char" level.
In particular, this comment was added in two places to Include/bytes_methods.h
in r72044:
http://svn.p
Changes by Dave Malcolm :
--
title: Remove -> Remove deprecated C "character" handling macros ISUPPER() etc
___
Python tracker
<http://bugs.pytho
Dave Malcolm added the comment:
Thanks for reviewing.
If I'm reading things correctly, the ISUPPER et al macros were added in 2.6 and
3.0, and deprecated in 2.7 and 3.1.
Tested with a full run of "-m test.regrtest -uall" here (x86_64 Fedora 13),
with both 2-byte and 4-b
Dave Malcolm added the comment:
Committed to py3k in r86210
--
___
Python tracker
<http://bugs.python.org/issue10288>
___
___
Python-bugs-list mailing list
Unsub
Dave Malcolm added the comment:
FWIW, I'm working on fixing up the this patch to work against py3k; I'm
assuming there's still interest in the AST visitor + specific optimization
passes approach.
--
___
Python tracker
<http
Dave Malcolm added the comment:
Seems to relate to this gdb feature:
http://sourceware.org/ml/gdb-patches/2005-05/msg00637.html
Barry: is your ~/.gdbinit world writable?
I can cook up a patch to ignore such warnings
--
___
Python tracker
<h
Dave Malcolm added the comment:
Alternatively, it looks like having it owned by another user would do this.
For curiosity's sake, what's the output of:
ls -al /home/barry/.gdbinit
on that buildbot?
Given that it's a security warning, should this simply be treated as
miscon
Dave Malcolm added the comment:
I've been working on this against the py3k branch. I'm attaching what I've got
so far.
I foolishly didn't check the tlee-ast-optimize branch, instead using file6850
as a base.
Rune Holm/titanstar, I assume you've signed a PSF contri
Dave Malcolm added the comment:
Another optimization idea: detect local dictionaries that are only ever used in
non-mutating ways, and convert them to constants, rather than rebuilding the
dict from scratch each time.
See e.g. htmlparser.py:adjustSVGAttributes etc within the bm_html5lib
Dave Malcolm added the comment:
Closing "won't fix", since this was misconfiguration; filtering out such
warnings might mask a security issue.
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bu
New submission from Dave Malcolm :
In various places within the generated Python/Python-ast.c, error handling
generates a repr() and raises exceptions accordingly.
Currently in py3k the generated code uses PyBytes_AS_STRING() on the repr. My
understanding is that repr() should be a
Dave Malcolm added the comment:
The attached patch:
- extends the ast error-handling selftest with code that triggers this crash
(on unpatched code)
- fixes Parser/asdl_c.py to generate code using _PyUnicode_AS_STRING instead
- contains the generated changes to Python/Python-ast.c
FWIW
Changes by Dave Malcolm :
--
nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan
___
Python tracker
<http://bugs.python.org/issue10391>
___
___
Pytho
New submission from Dave Malcolm :
In msg#120541 of issue#1346238 Raymond suggested to "aim high", so here goes...
I'm opening this as a separate bug as it's a very different approach to the
patches in that bug; adding those on the nosy list for that bug. Sorry in
ad
Changes by Dave Malcolm :
Added file: http://bugs.python.org/file19584/before.png
___
Python tracker
<http://bugs.python.org/issue10399>
___
___
Python-bugs-list mailin
Changes by Dave Malcolm :
Added file: http://bugs.python.org/file19585/after.png
___
Python tracker
<http://bugs.python.org/issue10399>
___
___
Python-bugs-list mailin
New submission from Dave Abrahams :
http://twistedmatrix.com/trac/ticket/4916#comment:2 suggests that maybe there's
a bug in distutils. Something in the build process for twisted is deciding
that I have Sun CC installed instead of letting pycc, which can handle the job
of picking the co
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue10924>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue11410>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Dave Malcolm :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue9263>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Dave Malcolm :
--
resolution: -> accepted
stage: patch review -> committed/rejected
status: open -> closed
versions: -Python 3.3
___
Python tracker
<http://bugs.python.or
Changes by Dave Malcolm :
--
nosy: +loewis
___
Python tracker
<http://bugs.python.org/issue9635>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
Various thoughts/nitpicking:
- is it possible to indicate with a coding convention (e.g. comments) which
parts of the code are intended to be called from a signal handler? It seems
worth making this explicit. Or perhaps put it all in one file?
- within
New submission from Dave Peck :
If you use `import` to load a package and subpackage:
import package
import package.subpackage
Then the `package` module instance will contain a `subpackage` attribute:
assert "subpackage" in dir(sys.modules['package']), &qu
New submission from Dave Malcolm :
With hg/mercurial 0.9.3, the build of CPython fails with this error:
gcc -pthread -c -fno-strict-aliasing -g -O0 -Wall -Wstrict-prototypes-I.
-IInclude -I./Include-DPy_BUILD_CORE \
-DHGVERSION="\"`LC_ALL=
Dave Malcolm added the comment:
Works OK with mercurial 1.3.1
(specifically, this is on a RHEL5 box, using mercurial-1.3.1-3.el5.i386.rpm
from EPEL5)
Closing this out, and changing title to help people searching for this. Not
sure of the exact version of mercurial that's req
Dave Peck added the comment:
Definitely could agree with this assessment, but it is surprising given the
lack of parallel behavior between 'import' and 'imp'.
Note that imp.load_module(subpackage) _does_ modify the parent module's
attributes -- but it will never put
Dave Malcolm added the comment:
I tried again, and I'm still able to reproduce this bug on a RHEL5 box with
cpython --with-pydebug as of a recent checkout (69030:00217100b9e7 as it
happens):
$ ./python -c "import multiprocessing.managers ; mpp = multiprocessing.Po
Dave Malcolm added the comment:
This is indeed looking like it's RHEL-specific.
I was about to close it out as a duplicate of issue 10517, but I'm wondering
why Brian chose to open it as a separate bug.
--
___
Python trac
Dave Malcolm added the comment:
jcea: I notice that on 2011-02-22 you made these changes:
assignee: dmalcolm -> dino.viehland
nosy: +dino.viehland
versions: +Python 3.3 -Python 3.2
Did you mean to change the assignee, or was this an accid
New submission from Dave Malcolm :
For Python 2 (here with 2.7.1):
$ python -c 'import locale; locale.setlocale(locale.LC_ALL, "tr_TR.UTF-8");
import decimal'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib64/python2.7/decimal.py
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue11845>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
>From IRC discussion, how about something like:
The current implementation consolidates integers in the range -5 to 256
(inclusive) into singleton PyIntObject instances, whereas other integer values
have unique PyIntObject instances created for them.
T
Dave Malcolm added the comment:
Perhaps should also note that this is done for the purposes of optimization
(both speed and memory).
--
___
Python tracker
<http://bugs.python.org/issue11
Dave Malcolm added the comment:
Interpreter idea: " is " could trigger a compatibility warning,
perhaps, to help people avoid relying on CPython quirks
--
___
Python tracker
<http://bugs.python.o
New submission from Dave Opstad :
Python 2.7.1 doesn't appear to do the usual implicit call to str() for
subclasses of unicode. In the following snippet, I would have expected print
myTest and print str(myTest) to behave the same:
>>> class Test(unicode):
... de
Dave Opstad added the comment:
I guess I was confused by the inconsistency with Python 3, which *does* call
the __str__ method, even though, again, no coercion is needed:
Python 3.2 (r32:88452, Feb 20 2011, 10:19:59)
[GCC 4.0.1 (Apple Inc. build 5493)] on darwin
Type "help",
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue11849>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Dave Abrahams :
The attached file demonstrates
--
components: Library (Lib)
files: bug.py
messages: 135770
nosy: dabrahams
priority: normal
severity: normal
status: open
title: doctest not working on nested functions
versions: Python 2.6, Python 2.7
Added file: http
Dave Malcolm added the comment:
Fix committed to py3k as r86499
--
___
Python tracker
<http://bugs.python.org/issue9518>
___
___
Python-bugs-list mailin
Dave Malcolm added the comment:
Perhaps "make patchcheck" (a.k.a Tools/scripts/patchcheck.py ) should verify
the markup of Misc/NEWS? Not sure what the easiest way to do that is, though,
without bringing in lots of deps.
--
nosy:
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue1353344>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
> Third, for that Graphviz output, was anything special required? If so,
> I would toss the code into Tools for others to benefit from.
It's merely the "to_dot" function from Lib/__optimizer__.py (which turns an AST
into .dot sour
Dave Malcolm added the comment:
Sorry again for another epic-length comment...
I'm attaching the latest work-in-progress on this.
The code is still fairly messy (embarrasingly so in places), but it's better to
have it out in public in this tracker than stuck on my hard drive.
Sym
Dave Malcolm added the comment:
Thanks for reading through this.
> There are a couple places you mention not doing the optimization when
> specific functions are used (e.g. dir, globals, locals), how exactly do you
> verify that, given those functions could be bound to any name?
I d
New submission from Dave Malcolm :
Misc/NEWS needs to be valid reST.
Issue 10450 identified an issue where it wasn't.
"make patchcheck" potentially could check the markup of that file, and,
potentially all the other places in the source tree that are supposed to be
valid r
Dave Malcolm added the comment:
Opened as issue 10507
--
___
Python tracker
<http://bugs.python.org/issue10450>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Dave Malcolm :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue9263>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
Attaching a simplified version of the patch; I got rid of the callbacks.
Still doesn't have test cases.
I suspect that the use of __STRING and __PRETTY_FUNCTION__ may be compatibility
issues. I believe that __FILE__ and __LINE__ and standard C t
Dave Malcolm added the comment:
> If this a work in progress, you could create an SVN branch in the
> sandbox (you can then use svnmerge to avoid diverging too much from
> mainline) or an hg repo.
Good idea; I've created branch "dmalcolm-ast-optimization-branch" (of
py3
Dave Malcolm added the comment:
py3k-ast-pyoptimize-2010-11-19-006.patch fixed up and committed to the branch
as r86715; I'll work on that branch for the time being.
--
___
Python tracker
<http://bugs.python.org/is
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue10517>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
I'm able to reliably reproduce this on a RHEL 5 box (i386 in this case).
All of the "ProcessPool*" unittest subclasses within
Lib/test/test_concurrent_futures.py exhibit this hang, each printing out just
the name of the first test (so presumabl
Dave Malcolm added the comment:
Minimal reproducer:
$ ./python -c "from concurrent.futures import * ; e = ProcessPoolExecutor() ;
e.submit(pow, 2, 5)"
Fatal Python error: Invalid thread state for this thread
--
___
Python trac
Dave Malcolm added the comment:
Seems to be an issue within (or triggered by) multiprocessing (test_threads and
test_threading pass OK, fwiw):
$ ./python -m test.test_multiprocessing
Fatal Python error: Invalid thread state for this thread
Traceback (most recent call last):
File "
Dave Malcolm added the comment:
By strategically adding print() and input() calls, I was able to isolate the
error to this line in test_multiprocessing.py's test_main:
ManagerMixin.pool = ManagerMixin.manager.Pool(4)
specifically, to the construction:
ManagerMixin.manager.P
Dave Malcolm added the comment:
FWIW, I was able to do an almost full run of regrtest on this box with:
-x test_multiprocessing test_concurrent_futures
Other than those two, all tests pass.
So _something_ is going wrong w.r.t. threads, though I'm not sure what at this
New submission from Dave Malcolm :
2.6.6 has an erronenous use of a unittest method that was added in 2.7, but
it's only seen when running as root. More specificially, with this guard:
if posix.getuid() == 0 and hasattr(posix, 'getgroups') and sys.platform !=
'darwi
New submission from Dave Malcolm :
(was misspelled when issue 5650 was fixed, FWIW)
--
assignee: orsenthil
components: Library (Lib)
files: py3k-fix-jwz-surname.patch
keywords: patch
messages: 123079
nosy: dmalcolm, orsenthil
priority: low
severity: normal
status: open
title
Dave Malcolm added the comment:
Fixed in py3k in r86932
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Dave Malcolm added the comment:
This is very interesting work - thank you!
Sorry for not commenting earlier (very busy), so here are my thoughts so far.
The baseline for the diff appears to be against the py3k branch, in that it
adds back in classes from 2.*: PyIntObject.
There's curr
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue1705520>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
A (probably crazy) idea that just occurred to me:
typedef char utf8_bytes;
typedef char iso8859_1_bytes;
typedef char fsenc_bytes;
then specify the encoding in the type signature of the API e.g.:
- int PyRun_SimpleFile(FILE *fp, const char *filename)
+ int
Dave Malcolm added the comment:
What version of the compiler was this with?
(For reference, I see that you also filed this downstream in Fedora's bug
tracker as:
https://bugzilla.redhat.com/show_bug.cgi?id=661510 )
--
nosy: +dmalcolm
___
P
Dave Malcolm added the comment:
Forgot to close this one out
--
resolution: -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Changes by Dave Malcolm :
--
stage: patch review -> committed/rejected
___
Python tracker
<http://bugs.python.org/issue9518>
___
___
Python-bugs-list mai
Changes by Dave Malcolm :
--
assignee: -> dmalcolm
___
Python tracker
<http://bugs.python.org/issue10399>
___
___
Python-bugs-list mailing list
Unsubscri
Dave Malcolm added the comment:
One of RH's gcc gurus told me in IRC that:
__ppc__ is not a standard powerpc*-linux macro
__PPC__ or __powerpc__ is
--
___
Python tracker
<http://bugs.python.org/is
Dave Malcolm added the comment:
For reference, this seems to affect SWIG, specifically, I'm seeing build
failures using:
/usr/share/swig/2.0.1/python/pycontainer.swg
from swig-2.0.1
See downstream build failure report for znc, which uses swig to generate python
3 bindings:
Dave Malcolm added the comment:
Note that for that test case to be run, it must be on an installed python:
@unittest.skipIf(sysconfig.is_python_build(),
"need an installed Python. See #7774")
Am testing the 2.7 branch now on an x86_64 Fed
Dave Malcolm added the comment:
That test works for me on this x86_64 Fedora 13 box (using latest 2.7 code from
SVN, built and installed to a test prefix):
[da...@surprise bin]$ ./python -m test.regrtest -v test_subprocess
== CPython 2.7.1+ (release27-maint:87724, Jan 3 2011, 19:39:26) [GCC
Dave Malcolm added the comment:
I should note that Fedora Core 4 reached its "End of Life" at August 2006:
http://fedoraproject.org/wiki/End_of_life
Do you see this with a more up-to-date version of Fedora?
--
___
Python trac
Dave Malcolm added the comment:
FWIW, I just added this patch downstream to Fedora's python 3 builds:
http://pkgs.fedoraproject.org/gitweb/?p=python3.git;a=blob_plain;f=python-3.2b2-fix-ppc-debug-build.patch;hb=5659c63442be2e91eb42e60284d7a9a9ab0
Dave Malcolm added the comment:
Adrian verified in the downstream bug tracker that this fixed the build for him
(and the logs show it successfully ran the test suite), so I committed my patch
to py3k as r87796.
--
___
Python tracker
<h
Dave Malcolm added the comment:
Merged back to 3.1 as r87800 and to 2.7-maint as r87801
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Dave Malcolm added the comment:
Attaching updated version of the patch.
I've added a selftest which (in a sacrificial subprocess) abuses ctypes to
break an ob_refcnt, and then triggers a garbage collection.
I also changed the printing to stderr to directly use fprintf and fflush to
e
Dave Malcolm added the comment:
As above, but I added an extra call to fflush in case the call to
_PyObject_Dump leads to a segfault.
--
Added file:
http://bugs.python.org/file20344/py3k-objdump-on-gcmodule-assertions-2011-01-10-002.patch
New submission from Dave Malcolm :
If we start a short-lived process which finishes before we begin communicating
with it (e.g. by crashing), we can receive a SIGPIPE due to the receiving
process no longer existing. This becomes an EPIPE, which becomes an:
OSError: [Errno 32] Broken pipe
Dave Malcolm added the comment:
On Wed, 2011-02-09 at 16:41 +, Barry A. Warsaw wrote:
> IIRC we thought about something like this during the PEP discussions and
> Guido nixed it.
FWIW, the closest I could find was this mail:
http://www.mail-archive.com/python-dev@python.org/ms
Changes by Dave Malcolm :
--
title: test_concurrent_futures crashes with "Fatal Python error: Invalid thread
state for this thread" -> test_concurrent_futures crashes with "--with-pydebug"
on RHEL5 with "Fatal Python error: Invalid
Dave Malcolm added the comment:
I spent some time bisecting the SVN history in the py3k branch, and believe
that r84914 is the commit that introduced this issue.
Details:
Trying on 4-core i386 RHEL 5 box
$ svn up -r REV
$ make clean ; make
(configured --with-pydebug)
Reproducer
Changes by Dave Malcolm :
--
nosy: +krisvale
___
Python tracker
<http://bugs.python.org/issue10517>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
r84914 was the implementation of issue 9786 (Native TLS support for pthreads)
--
___
Python tracker
<http://bugs.python.org/issue10
Dave Malcolm added the comment:
This appears to be happening in a child process when the parent process is
running:
Lib/multiprocessing/util.py, line 255, in _exit_function ()
Liberally adding printf() and getpid() calls in various places, seems to always
happen when parent process is
Dave Malcolm added the comment:
CVE-2011-0705
--
___
Python tracker
<http://bugs.python.org/issue11197>
___
___
Python-bugs-list mailing list
Unsubscribe:
Dave Malcolm added the comment:
FWIW, this regressed in 2.6.6 relative to 2.6.5, due to r79646 adding the
T_STRING_INPLACE test code to the 2.6 branch.
Note to self: https://bugzilla.redhat.com/show_bug.cgi?id=677392
--
___
Python tracker
<h
New submission from Dave Flogeras :
>From the python prompt, raw_input() (2.7.1) and input (3.2.0) behave as
>documented (they strip the trailing EOL chars)
However the two line test program:
x = raw_input() # or input() in 3.2.x
print( repr( x ))
And then run from the command line
Dave Flogeras added the comment:
Ok, I'm actually not sure of what I just said. I might not be running the
version I think I am, since windows behaves differently when using a program
started with extensions vs. started with python. It might actually be that
Python 2.7 is correct, bu
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue775964>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Dave Malcolm :
In many places throughout the existing test suite, there are assertions of the
form:
self.assertTrue(chips in menu)
and of the form:
self.assertTrue(cheese not in shop)
If these fail, the error message will merely tell you that the condition
failed
New submission from Dave Malcolm :
Currently sys.std[in|out|err] are set to the locale encoding but only if they
are directly connected to a tty (and PYTHONIOENCODING is not set in the
environment to override things).
The conditionality on "isatty" leads to lots of unexpected ch
Changes by Dave Malcolm :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue7745>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue1475523>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue5504>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Dave Malcolm :
--
nosy: +dmalcolm
___
Python tracker
<http://bugs.python.org/issue7861>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Dave Fugate :
Sprinkled throughout CPython's test modules are snippets of code such as the
following taken from 2.7A3's test_old_mailbox.py (line 141):
box = mailbox.UnixMailbox(open(self._path, 'r'))
The key thing to observe here is the file being
New submission from Dave Malcolm :
http://www.python.org/dev/faq/ doesn't seem to explain how to regenerate
"configure"
Here's an attempt at answering that question; I hope the following is
appropriate and factually correct:
How to regenerate the "configure&q
Dave Malcolm added the comment:
Eric Smith:
> Isn't it true that after regenerating configure that you need to check
> it back in? Or is that so obvious to everyone except me that it's not
> worth mentioning?
FWIW the above point wasn't obvious to me; if that's t
Dave Malcolm added the comment:
At Red Hat we've done some work on this feature. I'm sorry for not updating
this issue, I was swamped with tasks both pre-PyCon and during the event; I did
show the following to various folks at PyCon; I attempted to find Skip at PyCon
but was un
101 - 200 of 633 matches
Mail list logo
