Gregory P. Smith added the comment:
The call stack for that code path failing is:
#0 get_data (fp=0xf64920, archive=0xe77ecc
/home/greg/sandbox/python/cpython/2.7/junk95142.zip,
toc_entry=('/home/greg/sandbox/python/cpython/2.7/junk95142.zip/ziptestpackage/ziptestmodule.py',
0, 16, 16,
Terry J. Reedy added the comment:
*17481 is about changing getargspec to use signature, at least as a backup. But
that would not fix the example here. The calltips have been moved in 20122.
--
___
Python tracker rep...@bugs.python.org
Terry J. Reedy added the comment:
I am assuming that Serhiy meant to close this.
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19020
___
Terry J. Reedy added the comment:
There is insufficient info for any action on our part.
--
resolution: - works for me
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19584
New submission from Yury V. Zaytsev:
Hi,
I've managed to get the test suite of Python to run on Python 3.4.0b2 version
cross-compiled for a specialized POWER chip. I get a number of failures that
seem to have the same nature. I'm under impression, that actually the tests
might need to be
Gregory P. Smith added the comment:
The problem appears to be that every zipimporter instance keeps its own
reference to the zip files table of contents (self-files) instead of
continually using the module wide zip_directory_cache but the zip_stat_cache is
being maintained externally to that
Changes by STINNER Victor victor.stin...@gmail.com:
--
nosy: +mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20342
___
___
Vajrasky Kok added the comment:
Here is the patch for listobject. A couple of thoughts:
1. I can not convert this signature:
if (!PyArg_ParseTuple(args, O|OO:index, v,
_PyEval_SliceIndex, start,
_PyEval_SliceIndex, stop))
Nadeem Vawda added the comment:
No, I'm afraid I haven't had a chance to do any work on this issue since my last
message.
I would be happy to review a patch for this, but before you start writing one,
we should settle on how the API will look. I'll review the existing discussion
in detail over
Larry Hastings added the comment:
The bug you saw was an easy fix; the converter function needs to return 1
(success) from the == Py_None branch.
And yes, more unit tests would be good, fixing the documentation would be good
too. I did say the patch was nowhere near ready.
I will assume
Yury V. Zaytsev added the comment:
The CPU model is IBM PowerPC A2, the information about the cross-compiler is as
follows:
$ /bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc -v
Reading specs from
Tal Einat added the comment:
You look very handsome today Larry :)
Regardless, I do think this is a good idea. I've converted several functions
that have -1 as a default value for ints where they ideally should have None.
Having None as the default will be much clearer and less error prone
Tal Einat added the comment:
My only comment from reviewing the patch is that you seem to have used
NULLABLE_PY_SSIZE_T_INITIALIZE by accident one time in int_converter (in
clinic.py).
Other than that, as you already know, make sure to return 1 in both converters
in the if (arg == Py_None)
Serhiy Storchaka added the comment:
1. In list.index use custom converter.
/*[python input]
class slice_index_converter(CConverter):
type = 'Py_ssize_t'
converter = '_PyEval_SliceIndex'
[python start generated code]*/
2. In list.__init__ use either unspecified default value or
Changes by Yury V. Zaytsev y...@shurup.com:
Added file: http://bugs.python.org/file33613/pyconfig.h
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20342
___
Gregory P. Smith added the comment:
Here's a fix that I believe works with one TODO in there that needs
investigation due to a question about the current historical zipimport code.
--
Added file: http://bugs.python.org/file33614/issue19081-subimport-fix-gps02.diff
Serhiy Storchaka added the comment:
I don't remember who specifically needed the nullable ints, so I just added a
bunch of Derby contestants.
There are no much need in nullable ints, if they are needed, different use
cases require different semantic. I don't think we can now write general
Serhiy Storchaka added the comment:
And thank you for the fix for the __init__ methods. Could you please commit it?
The I'll update patches for bz2 and lzma modules.
Looks as Vajrasky Kok has encountered with yet one bug in generated __init__
wrapper(issue20185).
--
STINNER Victor added the comment:
According to what Yury told me on IRC, it's a cross-compilation issue. He wrote
me that the following commands returns b'C?\xff\x01\x02\x03\x04\x05' which is
the double big endian version, but DOUBLE_IS_BIG_ENDIAN_IEEE754 is not defined
from pyconfig.h
Larry Hastings added the comment:
Then you disagree with Guido, who says that optional integer arguments without
a viable publishable default value should accept None to mean use the default
value:
https://mail.python.org/pipermail/python-dev/2014-January/131673.html
Larry Hastings added the comment:
I'll fix the return NULL problem. However, you are using optional groups in
the list __init__. The original doesn't use them. Please stop using optional
groups in functions that don't require them.
--
___
Python
Serhiy Storchaka added the comment:
I thought it was too late for 3.4, and the conversion should not change the
behavior (we can change the behavior later in 3.5).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20341
Fabian Kochem added the comment:
Éric said that he should be able to get to it soon.:
https://twitter.com/merwok_/status/425596183176704002
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8876
Larry Hastings added the comment:
I guess we should ask Guido for clarification. But I got the impression that
we could *gently* tweak the signatures of functions if they were not
representable in Python syntax. He thought that giving the parameter of
_sha1.sha1() a default value of b'' was
Serhiy Storchaka added the comment:
I think that we do not yet have enough data. Too little cases are known for
which unsigned integer converters are needed, and different cases require a
different behavior. I prefer to defer until we convert the majority of the
code. Then we will see what
New submission from Christian Pérez:
To reproduce the error:
$ wget http://dbnsfp.houstonbioinformatics.org/dbNSFPzip/dbNSFP2.0.zip
$ python
Python 2.7.4 (default, Sep 26 2013, 03:20:26)
[GCC 4.7.3] on linux2
Type help, copyright, credits or license for more information.
from zipfile import
Changes by Serhiy Storchaka storch...@gmail.com:
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20343
___
___
Yury V. Zaytsev added the comment:
I've re-named the issue to reflect the problem.
One possible solution that I can see is to use AC_C_BIGENDIAN macro, either
exclusively, or only when cross-compiling.
In the latest autoconf sources, this macro seems to try to detect the
endianness from
Serhiy Storchaka added the comment:
Could you please test with in-development version Python 2.7.6+? Unlikely it is
related to issue6759, but perhaps it is related to issue20048.
--
___
Python tracker rep...@bugs.python.org
Larry Hastings added the comment:
Actually, the documented behavior of itertools.repeat() is that the times
argument takes a default of None.
Equivalent to:
def repeat(object, times=None):
...
http://docs.python.org/3/library/itertools.html#itertools.repeat
--
Serhiy Storchaka added the comment:
There is no problem on Linux.
I think wrapping will be more preferable. 200 columns looks to wide for tips.
Perhaps in 3.4 we can use textwrap.wrap() with the max_lines argument. And left
simple truncating in earlier versions.
--
Ezio Melotti added the comment:
Because you inserted LIBDIR before it existed, import noticed it didn't
exist and so put None into sys.path_importer_cache[LIBDIR]
I'm not familiar with sys.path_importer_cache, but what happens if instead of
putting None, sys.path_importer_cache[LIBDIR] is
Ram Rachum added the comment:
Patch attached. Is this good?
--
keywords: +patch
Added file: http://bugs.python.org/file33616/patch.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20218
STINNER Victor added the comment:
doko One possible solution that I can see is to use AC_C_BIGENDIAN
macro, either exclusively, or only when cross-compiling.
This is wrong. The macro is not used to check the endian but to check
the IEEE 754 implementation. The check is important to decide if
Ezio Melotti added the comment:
Why this issue has been closed even though people were still discussing it and
submitting patches?
Terry, can you check if the new patches should be applied?
--
stage: needs patch - patch review
status: closed - pending
Changes by Jeremy Kloth jeremy.kloth+python-trac...@gmail.com:
--
nosy: +jkloth
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20341
___
___
Nick Coghlan added the comment:
Right, at the very least we want to handle positional only arguments (since PEP
362 also handles those).
My one concern with using def as the prefix is the fact it's not actually
Python syntax.
How do you feel about using sig: as the prefix? That would still
Stefan Krah added the comment:
+1 for sig: .
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20326
___
___
Python-bugs-list mailing list
Larry Hastings added the comment:
The fact that def isn't Python syntax is, if anything, a mild point in its
favor. I don't want anyone hitting on this by accident. sig: isn't Python
syntax either, and yet you yourself propose it ;-)
How about sig=?
--
Christian Pérez added the comment:
With 2.7.6+ works fine.
Python 2.7.6+ (2.7:c28e07377b03, Jan 22 2014, 12:56:14)
[GCC 4.7.3] on linux2
Type help, copyright, credits or license for more information.
from zipfile import ZipFile
[54979 refs]
[54979 refs]
with ZipFile(dbNSFP2.0.zip, r) as
Fabian Kochem added the comment:
A dirty hack is to include this line at the top of your setup.py:
del os.link
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8876
___
Roundup Robot added the comment:
New changeset b3c2472c12a1 by Nick Coghlan in branch '3.3':
Issue #20317: Don't create a reference loop in ExitStack
http://hg.python.org/cpython/rev/b3c2472c12a1
--
nosy: +python-dev
___
Python tracker
Nick Coghlan added the comment:
Oh, that's quite neat. Because of the way _GeneratorContextManager works, the
context is actually already set correctly on the thrown exceptions, but
ExitStack is assuming it will be wrong.
This means _fix_exception (part of ExitStack.__exit__) ends up setting
Tal Einat added the comment:
Found two bugs in the draft patch in Objects/longobject.c:
1) In _PyLong_NullableIntConverter, there is no index variable, so the
Py_DECREF and Py_XDECREF need to be removed from the end of the function.
2) In _PyLong_NullablePy_ssize_tConverter, the index
Nick Coghlan added the comment:
That wasn't quite what I meant. def (a, b, c) *looks* like Python syntax
(aside from the missing function name), but def (a, b, c, /) does not. So I
consider def a misleading prefix.
By contrast, neither of these looks like it is trying to be a valid function
Roundup Robot added the comment:
New changeset 46c3ea358784 by Nick Coghlan in branch 'default':
Merge #20317 from 3.3
http://hg.python.org/cpython/rev/46c3ea358784
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20317
Serhiy Storchaka added the comment:
Seems this is related issue:
import zlib, inspect
zlib.compressobj.__text_signature__
'(level=Z_DEFAULT_COMPRESSION, method=DEFLATED, wbits=MAX_WBITS,
memLevel=DEF_MEM_LEVEL, strategy=Z_DEFAULT_STRATEGY, zdict=None)'
Changes by Serhiy Storchaka storch...@gmail.com:
--
resolution: - out of date
stage: - committed/rejected
status: open - closed
superseder: - zipfile's readline() drops data in universal newline mode
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
Thank you for your report Christian. This bug already fixed in issue20048. Wait
for Python 2.7.7 bugfix release.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20343
Larry Hastings added the comment:
Yes, that is how it must work. This is symmetric with pure Python functions:
import inspect
import zlib
def foo(a=zlib.Z_DEFAULT_COMPRESSION): pass
...
str(inspect.signature(foo))
'(a=-1)'
--
Larry Hastings added the comment:
I missed the detail that you were working with a patch applied.
I suspect the problem is, you misspelled one of the expressions you provided as
a default value. Try str(inspect.signature(x)) on every function you
converted. I bet one of them will throw an
Tal Einat added the comment:
Attached nearly complete conversion of Modules/_collectionsmodule.c.
I've converted all functions using PyArg_* functions, including __new__
methods, but not deque.__init__.
I'm attaching a separate patch for deque.__init__.
--
Added file:
Tal Einat added the comment:
Attached a patch converting deque.__init__ in Modules/_collectionsmodule.c,
which completes the conversion of this file.
This patch depends Larry's first patch in issue20341 (Argument Clinic: add
nullable ints). This functionality is used to simplify the existing
Serhiy Storchaka added the comment:
Yes, that is how it must work. This is symmetric with pure Python
functions:
This is because in pure Python functions we have no enough information. I
believe than origin expression is more useful in the help. Compare:
import re, inspect
p =
Larry Hastings added the comment:
This is because in pure Python functions we have no enough
information. I believe than origin expression is more useful
in the help.
That doesn't matter. inspect.Signature would have to change in order to
provide the original expression, and it's not
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +ncoghlan, skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20339
___
___
Python-bugs-list
Serhiy Storchaka added the comment:
Without the = unspecified parameters will be non-optional.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20293
___
Antoine Pitrou added the comment:
Some things:
- the concept of a nullable thing in Python doesn't exist; why not optional?
- why is there a error field in the new structs?
- the fact that the structs are defined in longobject.h looks bonkers
- boolean fields can be char instead of int (and
Larry Hastings added the comment:
- the concept of a nullable thing in Python doesn't exist; why not optional?
That's not what it means. Python parameters are optional if they
have a default value. These parameters are nullable, in the sense
that they can be either of a specific type or None.
Antoine Pitrou added the comment:
That's not what it means. Python parameters are optional if they
have a default value. These parameters are nullable, in the sense
that they can be either of a specific type or None. (But Noneable
seemed like a bad name). They are not necessarily
New submission from Arne Babenhauserheide:
Currently the default operation of logging prints messages like the following:
INFO:root: Milk found.
This is close to a print-call, but not much more useful - especially not in
small scripts. To make the default settings more useful to quick
New submission from Tobias Klausmann:
The subprocess docs state that the first argument can be either a string or an
iterable that contains the program and arguments to run. It also points out
that using shell=True allows for shell constructs. It does not mention a
subtlety that is introduced
Tal Einat added the comment:
Another bug in the patch:
In int_converter.__init__ in clinic.py, the patch adds:
if not isinstance(self.default, int):
fail(Illegal default value for int_converter)
This fails if no default is specified, e.g. for positional only argument. The
condition
R. David Murray added the comment:
This was discussed in issue 6760. There I advocated (and still advocate)
option (3). Unfortunately it looks like our doc update in that issue actually
*lost* the documentation for your option (2) that used to be there, though it
wasn't exactly clear what
Berker Peksag added the comment:
Attached patch to set TERM='' by default in test.script_helper._assert_python.
--
keywords: +patch
nosy: +berker.peksag
stage: needs patch - patch review
title: script_helper._asert_python should set TERM='' by default. -
script_helper._assert_python
Changes by Berker Peksag berker.pek...@gmail.com:
Added file: http://bugs.python.org/file33623/issue18300_test_doctest.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18300
___
R. David Murray added the comment:
Well, you can always call basicConfig yourself...that's kind of the point of
it. I'm guessing the current output was chosen exactly because it is pretty
much just a print of the input to the log method. But I don't have strong
feelings about it. On the
R. David Murray added the comment:
Believe me, we are *well* aware of the issue that linux stores filenames as
bytes.
I agree that the inability to always transcode is an issue. That's why I'd
like the opinion of someone who has studied this problem in more depth.
--
nosy: +ncoghlan
Changes by Tal Einat talei...@gmail.com:
--
assignee: - docs@python
components: +Build, Demos and Tools, Documentation
nosy: +docs@python
type: - enhancement
versions: +Python 3.4
___
Python tracker rep...@bugs.python.org
Changes by Serhiy Storchaka storch...@gmail.com:
--
resolution: - duplicate
superseder: - Argument Clinic does not support the 'l' format
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20346
New submission from Tal Einat:
There is no entry for 'l', which maps to 'long' according to 'long_converter'
in clinic.py.
Patch attached for Doc/howto/clinic.rst.
--
files: missing_long_legacy_converter.clinic.rst.patch
keywords: patch
messages: 208818
nosy: larry, taleinat
priority:
New submission from Christopher the Magnificent:
On OS X 10.9.1
This works:
Python 2.7.5 (default, Aug 25 2013, 00:04:04)
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin
Type help, copyright, credits or license for more information.
import __future__
dir(__future__)
STINNER Victor added the comment:
Python 2.7.5 (default, Aug 25 2013, 00:04:04)
You should try the version 2.7.6 which contains a fix for OS X 10.9:
http://www.python.org/download/releases/2.7.6/
--
nosy: +haypo, hynek, ned.deily
___
Python
Changes by R. David Murray rdmur...@bitdance.com:
--
assignee: ronaldoussoren -
resolution: - duplicate
stage: - committed/rejected
status: open - closed
superseder: - python.org Interactive interpreter linked with libedit can
segfault on future OS X
Tal Einat added the comment:
Attached is a complete conversion of Modules/_randommodule.c. Three
_random.Random methods were converted: seed, getrandbits and __new__.
There's was an problem converting _random.Random.__new__. I overcame it cleanly
and think this patch is good. Details about
Ned Deily added the comment:
This is a duplicate of Issue18458. The crash is caused by an incompatible
change introduced in OS X 10.9 to the Apple-supplied version of libedit's
readline compatibility layer and can affect Python versions that dynamically
link with the system libedit (not all
New submission from Brett Cannon:
http://docs.python.org/3.4/howto/
Seems several sections are listed on their own in the index.
--
assignee: larry
components: Documentation
messages: 208824
nosy: brett.cannon, larry
priority: normal
severity: normal
status: open
title: Argument Clinic
Brett Cannon added the comment:
Can't you at least say you don't know how import works unless you're
Canadian? =)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19081
___
Tal Einat added the comment:
Attached complete conversion of Modules/xxlimited.c, Modules/xxmodule.c and
Modules/xxsubtype.c.
There are no tests for these and the code is not used by anything AFAIK, so I
was extra careful and went over the diffs manually once everything was done.
--
New submission from Tal Einat:
This is caused by the code fields = list(parser_body_fields) under
if new_or_init: in CLanguage.output_templates().
'parser_body_fields' is initialized to None and may not be set before the
above mentioned code.
Attached is a patch which replaces the line with:
Brett Cannon added the comment:
So those semantics have existed as long as PEP 302 has been around, which is
Python 2.3 (that PEP itself is over a decade old), so changing them now would
break code.
And honestly I wouldn't change it anyway. On some filesystems, stat calls are
extremely
Brett Cannon added the comment:
So the docs don't mention this support anywhere. The 'l' format isn't listed in
the table of legacy to Argument Clinic converters, nor is there a list of
converters that only exist in Argument Clinic. So unless I read the section on
return converters and
Brett Cannon added the comment:
Re-positioning to work with both tarfile and zipfile since tarfile's 'r' will
transparently decompress as necessary. Might need to scale back some
functionality to make it easily work with both formats. But since are both
alternative storage solutions then some
Stefan Krah added the comment:
I think we should probably not convert xx*.c. They are for newcomers
who will likely be confused by the additional information overload.
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
New submission from Serhiy Storchaka:
Proposed patch replaces errorprone uses of tkapp.split() to tkapp.splitlist().
* Variable.trace_vinfo(). Actually there are no difference between split() and
splitlist(), because trace vinfo always returns a list of 2-element tuple of
strings and none of
Terry J. Reedy added the comment:
How about we extend the limit from 79 to say 120, to accommodate people who use
longer docstring lines, and only wrap the signature line, when present, like
the one for HTTPConnection, as the signature is the important information to
include.
--
Serhiy Storchaka added the comment:
Yes, I think we can extend the limit (until implement wrapping). On my narrow
monitor there is a room only for 120 character tip (when it starts right from
left side of the screen), so I prefer to wrap long lines. In any case too long
lines are not
Terry J. Reedy added the comment:
I presume the OP only cared about the Shell Window, and that was fixed.
I agree that submitted patches should not be ignored. I have decided I really
want editor windows labelled as sometimes run the *same* file with more than
one version, and it can be
New submission from Charles-Axel Dein:
IMO csv.DictWriter and csv.DictReader provides a nicer interface for complex
CSV file. I see some people reinventing the DictReader and DictWriter pretty
frequently, because when they rapidly scan the documentation all examples are
about csv.reader and
Moritz Neeb added the comment:
Here's a patch that changes the headings in clinic.rst, such that only the
first appears in the HOWTO listing. I also adapted the first according to the
convention in http://docs.python.org/devguide/documenting.html#sections
--
keywords: +patch
nosy:
New submission from Daniël van Eeden:
I use 'AUTH PLAIN secret' to login to a POP3 server with a proxy user. I
can't use 'pass_()' as I need to supply a admin user and the user to proxy into.
class adminpopserver(poplib.POP3):
def auth(self, method, secret):
return
New submission from Craig Silverstein:
Don't ask me how, but our code managed to combine multiprocessing, sqlite, and
tkinter all in one app, and got a hanging behavior, though only on a particular
OS. Removing any of these removes the hang. I filed this under tkinter, but
the fault could
Serhiy Storchaka added the comment:
Here is a patch (for 3.4) which wraps long lines. Now you can display a tip for
textwrap.TextWrapper.
--
keywords: +patch
stage: needs patch - patch review
Added file: http://bugs.python.org/file33632/idle_calltips_wrap.patch
Glenn Langford added the comment:
The same bug also exists in concurrent.futures.as_completed(). The minimal fix
suggested here also works, but the bigger fix suggested in issue #20297 is
recommended for as_completed().
--
___
Python tracker
R. David Murray added the comment:
This is basically rfc 5034 support? Sounds like a good idea.
I'm going to mark this issue as 'easy' because it isn't a whole lot of code,
but for anyone who wants to tackle it, know that understanding the RFC and
getting it *right* is not necessarily
New submission from jan matejek:
When compiling make profile-opt, the instrumented python executable segfaults
upon exit, even though it appears to run fine.
This breaks the build process, because make evaluates the segfault as if the
respective compilation step failed.
GDB yields the
Changes by Moritz Neeb n...@kpvn.de:
--
nosy: +zormit
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20351
___
___
Python-bugs-list mailing list
Vinay Sajip added the comment:
I don't think it is necessary or advisable to change the default, as it is very
easy to provide your own format. As RDM has noted, this could affect backward
compatibility. Furthermore, there are bound to be differing views of what an
ideal default should be, so
Changes by Vinay Sajip vinay_sa...@yahoo.co.uk:
--
resolution: - wont fix
status: open - pending
type: - enhancement
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20345
Giampaolo Rodola' added the comment:
Attached patch includes tests. I took test_sax.py as an example.
--
Added file: http://bugs.python.org/file33633/issue18695-2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18695
1 - 100 of 147 matches
Mail list logo
