Eric Snow added the comment:
Backwards compatibility requirements still apply to the importlib API -
while the default import system won't call FileFinder.find_module() any
more, third party import reimplementations are still free to do so.
Except that a good portion of the importlib API is
Changes by Eric Snow ericsnowcurren...@gmail.com:
Removed file: http://bugs.python.org/file26641/issue15502_new_abc.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15502
___
Eli Bendersky added the comment:
Attaching an updated patch that completes the documentation of network objects
(attributes, methods and operations). Additionally, inserted the provisional
package note and a new in 3.3 notice.
--
Added file:
Nick Coghlan added the comment:
Fair point. However, the find_module() variant of the API isn't dead yet, so we
should still support it. find_module() likely won't die completely until 4.0.
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
Should we do something before Python 3.3 final?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13072
___
___
STINNER Victor added the comment:
On Windows, stdin, stdout and stderr are creates using TextIOWrapper(...,
newline=None).
In this case, TextIOWrapper._writenl is os.linesep and so '\r\n'.
Oh, I was wrong: stdin is created with newline=None, but stdout and stderr are
created with
STINNER Victor added the comment:
The change was already done in another issue. I'm closing this one.
changeset: 71315:30f91fbfc8b3
user:Victor Stinner victor.stin...@haypocalc.com
date:Wed Jul 13 23:47:21 2011 +0200
files: Lib/test/regrtest.py
description:
Issue #12550:
STINNER Victor added the comment:
So can we close this issue, or should we start to document private functions?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15213
___
Manu Cupcic added the comment:
I am also hitting this issue.
I have been able to reproduce it in python 2.5 and 2.7, on debian 6 (64 bits)
Exactly like the reporter, I am making extensive use of threads. I am also
using SQLalchemy.
All my threads but one are waiting (probably for the GIL) :
New submission from Dirkjan Ochtman:
It seems nice if datetime.timestamp() would be mentioned in the What's New.
Does that seem acceptable? I'm happy to whip up a patch.
--
assignee: docs@python
components: Documentation
messages: 167096
nosy: djc, docs@python
priority: normal
Serhiy Storchaka added the comment:
Agree with Meador.
--
nosy: +storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15488
___
___
Roundup Robot added the comment:
New changeset 5a8c5631463f by Martin v. Löwis in branch '2.7':
Issue #8847: Disable COMDAT folding in Windows PGO builds.
http://hg.python.org/cpython/rev/5a8c5631463f
--
nosy: +python-dev
___
Python tracker
New submission from Chris Jerdonek:
The Dev Guide should say the preferred way (or even a way) to run tests using
the Python 2.7 build:
http://docs.python.org/devguide/runtests.html
This will help submitters who want to check that their patch works with 2.7.
In Python 2.7, this did not work
Roundup Robot added the comment:
New changeset 2638ce032151 by Martin v. Löwis in branch '3.2':
Issue #8847: Disable COMDAT folding in Windows PGO builds.
http://hg.python.org/cpython/rev/2638ce032151
New changeset 029cde4e58c5 by Martin v. Löwis in branch 'default':
Issue #8847: Disable COMDAT
Martin v. Löwis added the comment:
Thanks for the research and the fix!
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8847
___
Chris Jerdonek added the comment:
I verified that this patch can be applied to 2.7 and that those tests pass as
well.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15510
___
Ezio Melotti added the comment:
FWIW this is already mentioned in the quick start [0].
Do you want to propose a patch for runtest.rst?
[0]: http://docs.python.org/devguide/#quick-start
--
type: - enhancement
___
Python tracker
Chris Jerdonek added the comment:
FWIW this is already mentioned in the quick start [0].
I didn't catch that, thanks.
Do you want to propose a patch for runtest.rst?
Sure.
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
To debug this issue, it would help to have the following information:
- locale encoding: encoding variable
- tested character: ch
- character read by ncurses: read
Can someone reproducing the issue try to add: print(encoding=%s, ch=%r,
read=%r % (encoding,
STINNER Victor added the comment:
You didn't add any test for non regression??
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8847
___
___
New submission from abael:
Python-2.7.3/Objects/stringobject.c( SHA256SUM
ad7795c75e2a25247e4dea4cc5327c225c4da03b7c7d57226c817ba6d12a316c)
static PyObject *string_join(PyStringObject *self, PyObject *orig);
OLD IMPLEMENT LOGIC(Pseudo code):
char *sep = PyString_AS_STRING(self);
Changes by abael hyj...@gmail.com:
--
components: +Interpreter Core -Library (Lib)
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15522
___
___
Chris Jerdonek added the comment:
Attaching a patch for review.
--
keywords: +patch
stage: needs patch - patch review
Added file: http://bugs.python.org/file26645/issue-15521-1.patch
___
Python tracker rep...@bugs.python.org
New submission from Jarvis:
In the Python 2.4, it closes the socket only by calling request.close() method.
There is a risk by using this method to close socket. If the socket handle
count does not reach zero because another process still has a handle to the
socket then the connection is not
Stefan Krah added the comment:
Is it possible without too much effort to keep the old behavior
('u' - Py_UNICODE)? Then I'd say that should go into 3.3.
The problem with the current behavior is that it's neither backwards
compatible nor PEP-3118 compliant.
If it is too much work to restore
STINNER Victor added the comment:
Here is a patch reverting changes of the PEP 393, as suggested by Martin von
Loewis. With the patch, array uses Py_UNICODE* type for the 'u' format. So
array.array('u', '\u0010')[0] should return '\uDBFF' on Windows.
--
keywords: +patch
Added
Martin v. Löwis added the comment:
You didn't add any test for non regression??
Please rephrase your question: what tests did I not add?
I did add the tests that Stefan proposed.
--
___
Python tracker rep...@bugs.python.org
Chris Jerdonek added the comment:
Please backport and leave open for distutils2.
Éric, is there a place where updates to the distutils2 docs can be viewed and
made prior to reinclusion in the main Python repo? For example, the
documentation here:
Charles-François Natali added the comment:
Is there something else I can do to help resolve this bug ? I can help
debugging this, but I am not sure how to proceed. I have a --with-pydebug
interpreter stopped at the segfault in gdb.
Could you post the output of :
p op
and
thread apply
Manu Cupcic added the comment:
(gdb) p op
$12 = (PyObject *) 0x4dc7bc0
thread all apply bt is going to be very long no ? Could you tell me what you
want to know that is not in info threads maybe ? I can definitely post it here,
but it's going to be a lot of output.
I can be available on IRC
New submission from Dmitry Dvoinikov:
The following line prints different things each time you run it:
python3 -c print(', '.join({ '1': '2', '3': '4' }.keys()))
The output is either 1, 3 or 3, 1. Is such indeterministic behavior
intentional ?
Using Python 3.3.0b1 (default, Aug 1 2012,
Antoine Pitrou added the comment:
This has to wait for 3.4, since it's an enhancement, not a bug.
--
versions: +Python 3.4 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15488
___
Antoine Pitrou added the comment:
The comment needs to be fixed before the issue is closed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15213
___
Stefan Krah added the comment:
The diff between b9558df8cc58 and default with array_revert_pep393.patch
applied is small, but I noticed that in some places you switched back to
Py_UNICODE typecode and in others not. For instance, in struct arraydescr
typecode is still char.
I'm not sure why
STINNER Victor added the comment:
Please rephrase your question: what tests did I not add?
I did add the tests that Stefan proposed.
Ah yes, you added new tests to Python 3.2 and 3.3, but no to Python
2.7. Why not adding these new tests to Python 2.7?
--
Antoine Pitrou added the comment:
Yes, because hash randomization is now enabled by default:
http://docs.python.org/dev/reference/datamodel.html#object.__hash__
If you want deterministic behaviour, just set e.g. PYTHONHASHSEED=0.
(or any other fixed value)
--
nosy: +pitrou
STINNER Victor added the comment:
The diff between b9558df8cc58 and default with array_revert_pep393.patch
applied is small, but I noticed that in some places you switched back to
Py_UNICODE typecode and in others not.
I just copied code from Python 3.2, I forgot to update typecode type
Changes by Antoine Pitrou pit...@free.fr:
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15524
___
Antoine Pitrou added the comment:
Hi, several points:
- Python 2.7 is in bugfix mode; you need to work from the default Mercurial
branch as explained in http://docs.python.org/devguide/ . In practice, this
means your patch will target the future Python 3.4, and therefore either
Nick Coghlan added the comment:
Indeed, there are still a couple of Windows failures, but they aren't related
to this.
--
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15425
New submission from Nick Coghlan:
test_multiprocessing failed on one of the XP buildbots with a permission error:
http://buildbot.python.org/all/builders/x86%20XP-4%203.x/builds/7223/steps/test/logs/stdio
The immediate rerun also failed, but the one at the end of the test run
succeeded.
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13072
___
Martin v. Löwis added the comment:
Ah yes, you added new tests to Python 3.2 and 3.3, but no to Python
2.7. Why not adding these new tests to Python 2.7?
The tests don't crash Python 2.7. So they are not useful as a test whether
the bug has been worked-around. I actually don't know how to
New submission from Nick Coghlan:
regrtest bailed out completely on one of the Windows 7 builders due to a
problem with accessing the temporary working directory:
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/410/steps/test/logs/stdio
It's seems a touch
Changes by Nick Coghlan ncogh...@gmail.com:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15519
___
___
Python-bugs-list
Antoine Pitrou added the comment:
Well, test_startfile seems to be a common issue on that buildbot.
--
nosy: +jeremy.kloth, pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15526
___
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15522
___
___
Python-bugs-list mailing list
Antoine Pitrou added the comment:
I'm not sure why some finders are named Finder and others Importer. It
makes things confusing.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15519
Antoine Pitrou added the comment:
Uh, how is this a bug? An empty text doesn't contain lines at all, so returning
an empty list of lines sounds right.
Furthermore, by fixing this, you may break existing software.
--
nosy: +pitrou
___
Python tracker
Antoine Pitrou added the comment:
Yes, of course.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15520
___
___
Python-bugs-list
Jeremy Kloth added the comment:
I must also add that the proposed solution works well within the test suite as
the access denied error can also occur when creating subsequent files, not just
removing them.
This solution eliminates the need to wrap all creation calls with access denied
Jeremy Kloth added the comment:
Well, test_startfile seems to be a common issue on that buildbot.
I wouldn't really call it common (twice in the last 30 runs).
However I would wager that the PermissionError is being caused by an
unknown (without having Process Monitor running when the error
Barry A. Warsaw added the comment:
I've mostly run out of time to work on the docs, but I do want to say that I
thought long and hard about all the terminology decisions. Please don't
change them lightly, and definitely don't change them until you've tried to go
through the documentation and
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +brian.curtin
stage: - patch review
versions: +Python 2.7, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15496
___
Brett Cannon added the comment:
The importers can both find and load modules (e.g. BuiltinImporter defines both
find_module() and load_module()), while the finders only find modules (e.g.
only define find_module()). It's defined in the glossary, so maybe more links
to that would help.
Antoine Pitrou added the comment:
The importers can both find and load modules (e.g. BuiltinImporter
defines both find_module() and load_module()), while the finders only
find modules (e.g. only define find_module()).
Ah, fair enough. I thought loader objects were always distinct from
New submission from Serhiy Storchaka:
:c:func:`PyMem_Malloc(n)` on Doc/c-api/memory.rst:109 rendered in HTML as tt
class=xref c c-func docutils literalspan
class=prePyMem_Malloc(1)()/span/tt (note double parents). There are many
other examples on this and other pages. The issue is actual for
Brett Cannon added the comment:
So just to weigh in on this, I think meta path finder and path entry finder
(as Barry stated in the glossary already) clearly delineate what is from
sys.meta_path and what is from some path entry hook by having a clarifying word
to go with finder (either kind
Dirkjan Ochtman added the comment:
Can we have someone take a look at this? It seems fairly innocuous.
--
nosy: +djc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6308
___
Ezio Melotti added the comment:
Thanks for the patch.
I'm not sure it's necessary to add a new section though, unless you are
planning to add more differences there.
+base command instead of the one described above: ::
You can just use ... above:: here.
--
Changes by Antoine Pitrou pit...@free.fr:
--
title: Double parents in functions references - Double parens in functions
references
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15527
___
Daniel Holth added the comment:
re-tweak treatment of md5 in hashlib docs (the SHA-2 family is currently
recommended by http://csrc.nist.gov/groups/ST/toolkit/secure_hashing.html)
--
Added file: http://bugs.python.org/file26648/hashlib.patch
___
New submission from Richard Oudkerk:
A patch with docs and tests for the idea I suggested on python-ideas:
http://comments.gmane.org/gmane.comp.python.ideas/15863
To repeat what I wrote there, the current issues with weakref callbacks include:
1. They are rather low level, and working out
New submission from Tom Tromey:
I was debugging this bug reported against gdb:
http://sourceware.org/bugzilla/show_bug.cgi?id=14386
It turns out that what went wrong in this code was that
PyIter_Check evaluates to 0 when its argument is a
Python list.
This happens because the PyIter_Check
Benjamin Peterson added the comment:
That's because lists are iterators not iterable.
--
nosy: +benjamin.peterson
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15529
Roundup Robot added the comment:
New changeset b99a82bc2cde by Richard Oudkerk in branch 'default':
Issue #15525: Increase timeout when TerminateProcess() fails
http://hg.python.org/cpython/rev/b99a82bc2cde
--
nosy: +python-dev
___
Python tracker
Richard Oudkerk added the comment:
I would guess that the process has already terminated (or is being torn down)
but the timeout is not long enough to let the parent join child.
Let's see if increasing the timeout fixes the failures.
--
___
Python
Eric Snow added the comment:
@Barry: I'm fine with what you've said. My big concern is that we be really
consistent here because of the complexity of the import system. Things are at
a point that I think we're pretty close in the regard, so I'm mostly fine if we
stay put. My only real
Eric Snow added the comment:
Also, WindowsRegistryImporter is misnamed. It should be WindowsRegistryFinder
(see issue15502). Depending on the patch there, I'll update the one here.
--
dependencies: +Meta path finders and path entry finders are different, but
share an ABC
Eric Snow added the comment:
I guess the real question here is if anyone has problems with adding
WindowsRegistryFinder to importlib.machinery (and to the importlib docs). If
it should stay private than I'd like to throw a _ on the name of the class.
The change to importlib.abc would likely
Brett Cannon added the comment:
It should be exposed (i.e. if SourcelessFileLoader is documented and exposed
then so should WindowsRegistryFinder).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15519
Brett Cannon added the comment:
The patch will have Finder break all subclasses that don't define find_loader
which is backwards-incompatible. And if you really want to deprecate Finder you
should have a warning in an __init__ method (as one would hope people are
calling super() as
Roundup Robot added the comment:
New changeset 6e03f9b72c61 by Victor Stinner in branch 'default':
Issue #15463: Write a test for faulthandler truncating the name of functions
http://hg.python.org/cpython/rev/6e03f9b72c61
--
___
Python tracker
STINNER Victor added the comment:
I added a test checking that faulthandler truncates strings to
MAX_STRING_LENGTH characters using a very long function name. I consider this
issue as done.
--
resolution: - fixed
status: open - closed
___
Python
STINNER Victor added the comment:
Are we going to fix this before 3.3? Any objections to Victor's patch?
detect_truncate.patch is now raising an error if a line is longer than BUFSIZ,
whereas Python supports lines longer than BUFSIZ bytes (it's just that the
encoding cookie is ignored if the
STINNER Victor added the comment:
Sounds totally overkill to me.
I changed the maximum length of a string to 500 characters instead of
100. It should be enough for most cases.
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
The comment needs to be fixed before the issue is closed.
Ah yes, here is a patch updating the comment of _PyOS_URandom() and
the doc of the os module.
--
keywords: +patch
Added file: http://bugs.python.org/file26650/urandom_doc.patch
Roundup Robot added the comment:
New changeset 3edc71ed19e7 by Victor Stinner in branch 'default':
Issue #15441: Skip test_nonascii_abspath() of test_genericpath on Windows
http://hg.python.org/cpython/rev/3edc71ed19e7
--
nosy: +python-dev
___
Python
STINNER Victor added the comment:
This issue (the test) should be fixed, see the issue #15478 for the real fix.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15441
Chris Jerdonek added the comment:
I didn't want to write such test, but I can review a patch adding such test.
Victor, did you see and review my patch? There is currently no test to check
that a long file path (longer than 100 characters) will render, which was the
original issue that was
STINNER Victor added the comment:
Victor, did you see and review my patch? There is currently no test to check
that a long file path (longer than 100 characters) will render, which was the
original issue that was fixed. The patch provides such a test.
Yes, I saw your patch, but I don't
New submission from STINNER Victor:
Attached patch enhances Py_MIN and Py_MAX to check that types of both arguments
are compatible at compile time. Checks are only done if the compiler is GCC.
The patch uses also Py_MIN and Py_MAX in more places. (The commit may be done
in two parts.)
Chris Jerdonek added the comment:
Yes, I saw your patch, but I don't want to create very long filename.
Not all platforms support paths longer than 500 characters.
I think you may have a slight misunderstanding. My patch was not meant to test
paths over 500 characters. It tests a path
New submission from Dave Abrahams:
the docs for os.path don't mention the following facts which I think are
important (in fact I assumed the facts would be the reverse):
os.path.realpath(l) works when l is a broken symbolic link, returning the path
to the (missing) target
os.path.readlink(l)
Brett Cannon added the comment:
I think Benjamin meant to say lists are iterables not iterators. =)
--
nosy: +brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15529
___
Stefan Krah added the comment:
array_revert_pep393-2.patch looks good (checked against 7042a83f37e
and all following commits that should be kept).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13072
Christian Heimes added the comment:
+1
win32 supports thread names, too.
http://msdn.microsoft.com/en-us/library/xcb2z8hs.aspx
--
nosy: +christian.heimes
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15500
Changes by Christian Heimes li...@cheimes.de:
--
nosy: +christian.heimes
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15468
___
___
Chris Jerdonek added the comment:
Here are additional test cases impacted by this issue:
wrap( )
[]
wrap(\n\n\n)
[]
wrap(\n\n\n, replace_whitespace=False)
[]
wrap( \n\n, replace_whitespace=False)
[]
--
___
Python tracker
Martin v. Löwis added the comment:
I think that's too late for 3.3. It's not a bug fix.
If we use this kind of feature, we either need to declare a minimum supported
GCC version (any GCC older than 10 years can be dropped IMO), or check for the
specific version of GCC in which all the
Dave Malcolm added the comment:
Note to self: a messy way of forcing gdb to do the equivalent of a breakpoint
directly from Python is:
os.kill(os.getpid(), signal.SIGTRAP)
--
___
Python tracker rep...@bugs.python.org
New submission from Andy Lutomirski:
This program:
import subprocess, sys
p = subprocess.Popen(['bash', '-c', 'while true; do echo x; sleep 1; done'],
bufsize=0, stdout=subprocess.PIPE)
for line in p.stdout:
sys.stdout.buffer.write(line)
sys.stdout.flush()
sits around and does
Nick Coghlan added the comment:
As a final attempt at giving the path import machinery the emphasis it
deserves without misusing the importer term, how about:
1. path import subsystem for that whole section of the import machinery;
and
2. path import finder specifically for the meta path finder
STINNER Victor added the comment:
I think that's too late for 3.3. It's not a bug fix.
Oops, I chose 3.3 instead of 3.4. Fixed.
If we use this kind of feature, we either need to declare a minimum supported
GCC version
typeof() and __builtin_types_compatible_p() were introduced to gcc in
STINNER Victor added the comment:
@Georg: are you ok with this change? It reverts the behaviour of Python 3.2 and
avoids to have to maintain an API that nobody wants to use ('u' format using
Py_UCS4, 32 bits unsigned).
--
nosy: +georg.brandl
___
Barry A. Warsaw added the comment:
On Aug 01, 2012, at 10:03 PM, Nick Coghlan wrote:
1. path import subsystem for that whole section of the import machinery;
and
2. path import finder specifically for the meta path finder that
importlib calls PathFinder and the new docs currently call path
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
versions: +Python 3.4 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1521950
___
___
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14713
___
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15525
___
___
Python-bugs-list
STINNER Victor added the comment:
Let's see if increasing the timeout fixes the failures.
At least, the 3 following builds succeed (let's see the next builds).
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
1 - 100 of 132 matches
Mail list logo
