Claudiu Popa added the comment:
No, my home directory is actually /root. The attached patch should be clearer
now (I hope). Regarding your question, wouldn't checking for this duplicate
what os.path.expanduser already does? (Unless checking for the exact same
string before returning it.)
Mark Dickinson added the comment:
It seems likely that this information is just out of date. But even if there
*are* still built-in functions lurking somewhere that don't release the GIL
during I/O, the statement in the docs isn't really helpful in finding them.
Either way, I'd recommend
Changes by Mark Dickinson dicki...@gmail.com:
--
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22006
___
___
Changes by Terry J. Reedy tjre...@udel.edu:
--
stage: - test needed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21964
___
___
Python-bugs-list
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21964
___
___
Xavier de Gaye added the comment:
Two issues here:
a) in IDLE, on a 'return' debug event in the main module, the step command does
not end the debugging session.
b) in IDLE, BdbQuit is raised by the quit command when the debugger is started
with pdb.set_trace().
I do not know IDLE, but a)
Robin Becker added the comment:
I'll repeat the post I made to BreamoreBoy regarding this bug:
re: http://bugs.python.org/issue1047397
this bug is now 10 years old. I'm not sure why it's to be considered
closed because the original intent of the bug report was that the html
output of the cgitb
Antoine Pitrou added the comment:
It all depends what you call I/O. What is true is that not all functions
doing system calls release the GIL, AFAIR. If you mean I/O as in actual disk or
network I/O then yes, all such functions whould release the GIL.
That said, I agree that the statement
Antoine Pitrou added the comment:
That doesn't sound like a good idea. lru_cache is a decorator, that acts as
transparently as possible (i.e. the decorated function has the same metadata
and appearance as the original function). Therefore, the lru_cache'd function
should also pickle as a
Stephen Paul Chappell added the comment:
If you want the IDLE shell to be as consistent as possible with the editor
windows, changing the TAB binding to insert four spaces instead of a tab
(alternative 2) would be helpful.
--
___
Python tracker
New submission from Yannick Duchêne:
`make test` fails with Python 3.4.1 on Ubuntu 12.04 Intel 32 bits.
The single `./configure` option used, was `--prefix=$HOME/.local`.
As attached file, an archive containing both standard output and standard error
outputs.
Not some important error
STINNER Victor added the comment:
I can reproduce the issue on Linux:
Sorry, I forgot to mention that I reproduced the issue on Fedora 20 with Python
2.7.
I cannot reproduce with Python 3.3.
--
___
Python tracker rep...@bugs.python.org
New submission from Tyler Wade:
On Mac OSX, struct.unpack incorrectly handles bools.
Python 3.4.1 (default, May 19 2014, 13:10:29)
[GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.40)] on darwin
Type help, copyright, credits or license for more information.
import struct
Guido van Rossum added the comment:
Not in my wildest dreams could I have expected that that claim would still be
in the docs 20 years later. :-) Please get rid of it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22006
Ned Deily added the comment:
Doing a quick look, the results vary. Using current python.org 2.7.8 and 3.4.1
installers, the results are correct. These interpreters are built with Apple
gcc-4.2 (non-LLVM) from Xcode 3.2.6. Other 2.7 and 3.4.x builds I have
available at the moment, including
Mark Lawrence added the comment:
Does this render the patch against build_pgo.bat on #17667 obsolete?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21907
___
Mark Lawrence added the comment:
See also #21907.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17667
___
___
Mark Lawrence added the comment:
I don't understand this at all, but if this is a Sphinx bug shouldn't it be
reported on the appropriate bug tracker and not here?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
Changes by Brian Curtin br...@python.org:
--
nosy: -brian.curtin
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17667
___
___
Python-bugs-list
Roundup Robot added the comment:
New changeset 4f359c631bb0 by Mark Dickinson in branch '2.7':
Issue #22006: Remove outdated thread module caveat. Thanks Dan O'Reilly for
the report.
http://hg.python.org/cpython/rev/4f359c631bb0
--
___
Python
Roundup Robot added the comment:
New changeset 855ff9182a07 by Mark Dickinson in branch '3.4':
Issue #22006: Remove outdated _thread caveat. Thanks Dan O'Reilly for the
report.
http://hg.python.org/cpython/rev/855ff9182a07
New changeset 3b6b905ae229 by Mark Dickinson in branch 'default':
Mark Dickinson added the comment:
It's gone.
--
resolution: - fixed
stage: needs patch - resolved
status: open - closed
versions: -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22006
R. David Murray added the comment:
Agreed, the documentation should be modified to say (using os.fstat on its
file descriptor, and its 'name' attribute if arcname is not specified).
--
assignee: - docs@python
components: +Documentation
nosy: +docs@python, r.david.murray
stage: -
Mark Dickinson added the comment:
The relevant piece of code in the struct module looks like this:
static PyObject *
nu_bool(const char *p, const formatdef *f)
{
BOOL_TYPE x;
memcpy((char *)x, p, sizeof x);
return PyBool_FromLong(x != 0);
}
Is it possible that BOOL_TYPE is a
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 3.5 -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16446
___
Mark Dickinson added the comment:
Some debugging shows that we're calling 'nu_bool' even for , which is
a bit odd.
Ah, I see. There's an optimisation that uses the native table functions
instead of the big/little-endian ones if the size and byte order match.
--
Terry J. Reedy added the comment:
With Python 3.4.1, Win 7, there is a detour stepping through displayhook before
arriving at the same place with the same result upon quitting. If one does not
quit, stepping ends at
c:\programs\python34\lib\threading.py(235)__enter__()
- return
paul j3 added the comment:
As Steven notes, the patch lacks tests. It also lacks documentation.
The 2 things that this class does different from 'version' are
- write without passing the text through 'textwrap'
- write to a user defined file
There is a difference in opinion between Éric and
Changes by Brian Curtin br...@python.org:
--
nosy: -brian.curtin
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17896
___
___
Python-bugs-list
Mark Lawrence added the comment:
I also find the location annoying and would be happy to see it moved.
Regarding the extra long build time on the buildbots due to having to
recompile Tcl/Tk and OpenSSL is this a one off the first time you run after
the commit, or does it always happen because
Terry J. Reedy added the comment:
The problem with just /\t// is the absence of a secondary prompt.
def f():
return 'not acceptible'
Hence the 8+4+4... proposal. With a proportional font, the return would start
to the *left* of def. Adding '... ' works for fixed pitch fonts, but
Mark Lawrence added the comment:
From what I can see the code is completely the same in default but does this
matter or not? As a matter of interest is there an official policy regarding
code clones, whether in C or pure Python?
--
nosy: +BreamoreBoy
Changes by Ned Deily n...@acm.org:
--
components: +Build -Macintosh
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22012
___
___
Python-bugs-list
Ned Deily added the comment:
FTR, the problem also shows up with the current clang-3.4 (3.4.2) and clang3.5
(svn213451-1) packages in Debian testing (on i386), building --with-pydebug and
without, so the issue is not confined to OS X.
--
assignee: ronaldoussoren -
Changes by Ned Deily n...@acm.org:
--
title: struct.unpack('?', '\x02') returns (False,) on Mac OSX -
struct.unpack('?', '\x02') returns (False,) when Python is built with clang
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 9cd3ab7c09d1 by Benjamin Peterson in branch '2.7':
args doesn't need to be a tuple (closes #17210)
http://hg.python.org/cpython/rev/9cd3ab7c09d1
New changeset ffbbd43d7342 by Benjamin Peterson in branch '3.4':
args doesn't need to be a tuple
Mark Lawrence added the comment:
The patch is very short so can we have a formal review please.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15305
___
Andrew Barnert added the comment:
http://thread.gmane.org/gmane.comp.python.ideas/28310 discusses the same idea.
Guido raised a serious problem with either adding an argument to readline and
friends, or adding new methods readrecord and friends: It means the hundreds of
existing file-like
Andrew Barnert added the comment:
While we're at it, Douglas Alan's solution wouldn't be an ideal solution even
if it were a builtin. A fileLineIter obviously doesn't support the stream API.
It means you end up with two objects that share the same file, but have
separate buffers and
Andrew Barnert added the comment:
One last thing, a quick dirty solution that works today, if you don't mind
accessing private internals of stdlib classes, and don't mind giving up the
performance of _io for _pyio, and don't need a solution for binary files:
class
Martin Panter added the comment:
I experimented with various redirections to /dev/null, files, and other
terminal windows on Linux. Current behaviour I am seeing seems to be something
like this:
* Prefers prompting to stderr if both stdout and stderr are terminals
* Prefers prompting to
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1152248
___
___
Python-bugs-list
Ned Deily added the comment:
The problem here is that you are trying to use sys.stdin for two different
purposes: 1. as a data input source for your program using stdin redirected to
a disk file; and 2. for pdb's source of debugging commands, expected to be a
terminal file. By specifying -m
Martin Panter added the comment:
For Posix (dunno about Windows), calling terminate or kill at the OS level
after a poll or wait has already succeeded is a bad idea, because the PID may
have been recycled. It is essentially operating on a released resource, similar
to calling “os.close” on a
Zachary Ware added the comment:
After the most recent changes to the buildbot scripts, it would be every time
without a patch to the clean script, but at the time I only meant a single time
(which really isn't a big deal).
The patch is well out of date, I can update it if we can come to a
Ned Deily added the comment:
(In the future, please just show the test failures and their tracebacks rather
than uploading a tar file.)
The logs show three test failures in test_os:
==
ERROR: test_fds
46 matches
Mail list logo
