Mark Dickinson added the comment:
Without having looked too hard, the many warnings are almost certainly from our
definition of Py_NAN. That's been fixed in the default branch. I'm not sure
whether it's worth backporting just to fix warnings.
--
Serhiy Storchaka added the comment:
Sorry, it's my fault. Here is a patch which should fix the bug.
--
nosy: +skrah
Added file: http://bugs.python.org/file28082/test_unknown_option.patch
___
Python tracker rep...@bugs.python.org
Serhiy Storchaka added the comment:
Actually 2.7 tests should not be broken, but this patch unify 2.7 and 3.x code.
--
Added file: http://bugs.python.org/file28083/test_unknown_option-2.7.patch
___
Python tracker rep...@bugs.python.org
anatoly techtonik added the comment:
pyunit_time.patch is invalid - missing space on the last line.
--
nosy: +techtonik
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4080
___
Serhiy Storchaka added the comment:
The json module already has too many options. No need for yet one such
specialized.
class number_str(float):
... def __init__(self, o):
... self.o = o
... def __repr__(self):
... return str(self.o)
...
def decimal_serializer(o):
Changes by Kristján Valur Jónsson krist...@ccpgames.com:
--
nosy: +kristjan.jonsson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13475
___
___
Changes by Kristján Valur Jónsson krist...@ccpgames.com:
--
nosy: +kristjan.jonsson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14803
___
___
Serhiy Storchaka added the comment:
How about ipaddress.IPv4Network((3232235520, 16)),
ipaddress.IPv4Network((3232235520, 65535)) and
ipaddress.IPv4Network((3232235520, 4294901760))?
ipaddress.IPv4Address(3232235520)
IPv4Address('192.168.0.0')
ipaddress.IPv4Address(65535)
Kristján Valur Jónsson added the comment:
Butting in here:
Early on in the startup, a search is made for site.py using automatic
sys.path settings. Do the suggestions here propose to override this? I know
there is a -s flag, but all these flags start to be confusing.
I have been looking for
Mark Dickinson added the comment:
Judging by the discussion that Éric points to, and by the various stackoverflow
questions on the topic ([1], [2]), this is a common enough need that I think it
would make sense to have some support for it in the std. lib.
There's a sense in which Decimal is
Berker Peksag added the comment:
Here's a patch that adds tests and updates the documentation.
--
nosy: +berker.peksag
Added file: http://bugs.python.org/file28084/issue11797.diff
___
Python tracker rep...@bugs.python.org
Jeremy Kloth added the comment:
On Thu, Nov 22, 2012 at 3:11 PM, Antoine Pitrou rep...@bugs.python.org wrote:
The AMD64 Windows 7 buildbot shows weird build failures in ctypes:
http://buildbot.python.org/all/buildslaves/kloth-win64
The _ctypes_d.pyd was considered to be in use by the system
Lorenzo M. Catucci added the comment:
OK, I'm uploading poplib_03_starttls_v5.diff; I only changed the
caps=self.capa() into caps = self.capa() in the @@ -352,21 +360,42 @@
class POP3: hunk.
Thank you for pointing at the line; I tried to run pep8.py on poplib.py, but
failed to find the line,
Changes by Lorenzo M. Catucci lore...@sancho.ccd.uniroma2.it:
Removed file: http://bugs.python.org/file28026/poplib_03_starttls_v4.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4473
___
Ezio Melotti added the comment:
Can you paste the traceback you get with IDLE and also try the same from the
command line?
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16491
New submission from Daniel Urban:
The documentation of the dis module describes the MAKE_CLOSURE opcode
incorrectly. The description of MAKE_FUNCTION was updated in 242d3f8e8c50
(issue14349) to include the qualified name, but MAKE_CLOSURE wan't. A patch is
attched.
--
assignee:
Roundup Robot added the comment:
New changeset 5d1e7912e23e by Andrew Svetlov in branch '3.3':
Issue #16538: correctly describe MAKE_CLOSURE in docs.
http://hg.python.org/cpython/rev/5d1e7912e23e
New changeset 8fff40a7c5b5 by Andrew Svetlov in branch 'default':
Merge issue #16538: correctly
Andrew Svetlov added the comment:
Fixed. Thanks.
--
nosy: +asvetlov
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16538
Mark Dickinson added the comment:
I wonder whether adding -fpeval=float to the CFLAGS would fix this. There's
a lot of information at
http://h21007.www2.hp.com/portal/site/dspp/menuitem.863c3e4cbcdc3f3515b49c108973a801?ciid=0008a22194f02110a22194f02110275d6e10RCRD
but I don't know whether
New submission from anatoly techtonik:
It is very annoying. Take this as an example. 'patch' is a module (library)
that is meant to be used from other programs. Therefore it can not (should not)
setup handlers for itself.
import patch
patch.PatchSet().parse('7745')
No handlers could be
Changes by Serhiy Storchaka storch...@gmail.com:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16511
___
___
anatoly techtonik added the comment:
Forgot to mention that bundled NullHandler doesn't work in Python 2.7 and from
what I can see it is not covered with tests for this version.
Traceback (most recent call last):
File stdin, line 1, in module
File patch.py, line 124, in fromstring
Meador Inge added the comment:
I'm not sure how much this is needed considering hashlib has been around,
since 2.5.
I hope people aren't having to port from before then.
Martin alluded to that when he opened the issue saying this wasn't necessary,
but a nice
to have. However, it has been
anatoly techtonik added the comment:
Nevermind the last message - I was specifying NullHandler as a class, not as an
instance.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16539
___
anatoly techtonik added the comment:
More specifically, you need to copy NullHandler code if you want to run it with
Python 2.x 2.7
--
nosy: +techtonik
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14273
Ezio Melotti added the comment:
The new patch doesn't seem to be correct:
without the patch:
$ ./python -a -z
Unknown option: -a
Unknown option: -z
usage: ./python [option] ... [-c cmd | -m mod | file | -] [arg] ...
with the patch:
$ ./python -a -z
Unknown option: -a
usage: ./python [option]
Vinay Sajip added the comment:
This is not a valid issue. The approach to use is documented:
http://docs.python.org/2.6/library/logging.html#configuring-logging-for-a-library
http://docs.python.org/2.7/howto/logging.html#configuring-logging-for-a-library
--
resolution: - invalid
Serhiy Storchaka added the comment:
Thanks, Ezio, for point.
without the patch:
$ ./python -a -z
Unknown option: -a
Unknown option: -z
usage: ./python [option] ... [-c cmd | -m mod | file | -] [arg] ...
This behavior isn't correct. Try also -E -a -z and -a -E -z (also with
3.3.0).
Changes by Serhiy Storchaka storch...@gmail.com:
Added file: http://bugs.python.org/file28088/test_unknown_option_2-2.7.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16306
___
Ezio Melotti added the comment:
This behavior isn't correct.
Shouldn't python report all the invalid flags passed?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16306
___
Serhiy Storchaka added the comment:
Should not. It happened unintentionally (and inconsistently).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16306
___
Jesús Cea Avión added the comment:
Could you possibly locate the problematic changeset? Could be doable by
bisection.
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16529
___
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5765
___
___
Python-bugs-list mailing list
Marc-Andre Lemburg added the comment:
On 23.11.2012 17:02, Jesús Cea Avión wrote:
Could you possibly locate the problematic changeset? Could be doable by
bisection.
I'll try to find the changeset. There were only 4 checkins
related to ceval.c since the 3.3.0 release, so one of those
will
Marc-Andre Lemburg added the comment:
On 23.11.2012 17:24, M.-A. Lemburg wrote:
On 23.11.2012 17:02, Jesús Cea Avión wrote:
Could you possibly locate the problematic changeset? Could be doable by
bisection.
I'll try to find the changeset. There were only 4 checkins
related to ceval.c
New submission from Neil Girdhar:
When using sequence types polymorphically, range, list, and tuple are both
iterable and subscriptable. Unfortunately, itertools.count, cycle, and repeat
objects are not subscriptable, although this is not a hard change.
Please consider making these objects
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +rhettinger
stage: - needs patch
versions: -Python 3.1, Python 3.2, Python 3.3, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16540
Serhiy Storchaka added the comment:
Range, list, and tuple are iterables, but itertools.count, cycle, and repeat
objects are iterators. Subscripting is not a part of iterator protocol.
--
nosy: +serhiy.storchaka
___
Python tracker
Roundup Robot added the comment:
New changeset 6a79e3beb854 by Ezio Melotti in branch '2.7':
#16306: report only the first unknown option and add more tests. Patch by
Serhiy Storchaka.
http://hg.python.org/cpython/rev/6a79e3beb854
New changeset 654a628f5f00 by Ezio Melotti in branch '3.2':
Neil Girdhar added the comment:
Apologies if this is a bad question, but why do count, cycle, and repeat return
iterators rather than iterables?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16540
Changes by Andrew Svetlov andrew.svet...@gmail.com:
--
nosy: +asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16474
___
___
Éric Araujo added the comment:
LGTM.
--
nosy: +eric.araujo
title: setup.py throws a ValueError when self.extensions is empty - Python’s
setup.py raises a ValueError when self.extensions is empty
___
Python tracker rep...@bugs.python.org
Éric Araujo added the comment:
See also:
http://bugs.python.org/issue3754
cross-compilation support for python build
http://bugs.python.org/issue1006238
cross compile patch
http://bugs.python.org/issue1597850
Cross compiling patches for MINGW (superseder of
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo, vinay.sajip
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16519
___
___
Andrew Svetlov added the comment:
LGTM
--
nosy: +asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16477
___
___
Python-bugs-list mailing
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16508
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ghaering
stage: - needs patch
versions: +Python 3.2, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16509
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16518
___
___
Éric Araujo added the comment:
The point of itertools is to implement building blocks for iterators, which are
memory-efficient and can sometimes be infinite, contrary to sequences.
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
anatoly techtonik added the comment:
I'd say this is a pretty valid issue with won't fix or workaround available
resolution.
The question - is the same behavior preserved for Python 3?
--
resolution: invalid - wont fix
status: closed - languishing
Andrew Svetlov added the comment:
+0 for patch
--
nosy: +asvetlov
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16488
___
___
Python-bugs-list
New submission from Helmut Jarausch:
import tkinter as Tk
root= Tk.Tk()
root.tk_setPalette(background = 'AntiqueWhite1', foreground = 'blue')
but python-3.3:0+ (3.3:27cb1a3d57c8+) gives
Traceback (most recent call last):
File Matr_Select.py, line 174, in module
New submission from joko suwito:
thank you
--
messages: 176194
nosy: joko.suwito
priority: normal
severity: normal
status: open
title: http//bugs.python/joko.suwito
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16542
Serhiy Storchaka added the comment:
There are two ways to fix this issue:
1. Fix tk_setPalette() (just wrap kw.items() with list() or tuple()).
2. Fix C implementation of _flatten() for work with any iterators.
--
nosy: +gpolo, serhiy.storchaka
stage: - needs patch
type: compile error
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +patch
nosy: +chris.jerdonek
stage: needs patch - patch review
versions: +Python 3.2
Added file: http://bugs.python.org/file28089/issue16523.diff
___
Python tracker rep...@bugs.python.org
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
resolution: - invalid
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16542
___
Serhiy Storchaka added the comment:
Apologies if this is a bad question, but why do count, cycle, and repeat
return iterators rather than iterables?
Actually they are iterables too.
--
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset a2038edb51cd by Ezio Melotti in branch '2.7':
#16530: the options arg of os.wait3 is required.
http://hg.python.org/cpython/rev/a2038edb51cd
New changeset 1cf1194a443e by Ezio Melotti in branch '3.2':
#16530: the options arg of os.wait3 is
Ezio Melotti added the comment:
Fixed, thanks for the report!
--
assignee: docs@python - ezio.melotti
nosy: +ezio.melotti
resolution: - fixed
stage: - committed/rejected
status: open - closed
versions: -Python 2.6, Python 3.1
___
Python tracker
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16531
___
Guilherme Polo added the comment:
If doing list(kw.items()) works, I'm fine with that. If it does not, then
ttk._format_optdict(kw) should.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16541
Amaury Forgeot d'Arc added the comment:
Python 3 has exactly the same documentation:
http://docs.python.org/3.3/howto/logging.html#configuring-logging-for-a-library
--
nosy: +amaury.forgeotdarc
resolution: wont fix - works for me
status: languishing - closed
Chris Jerdonek added the comment:
+.. function:: attrgetter(attr[, attr2, attr3, ...])
Why not reword to use the *attr notation? It is even already being used below:
+ The function is equivalent to::
def attrgetter(*items):
if any(not isinstance(item, str) for item in
New submission from Ezio Melotti:
This came up in #16515.
While using PyArg_UnpackTuple to parse the positional arguments in a function
that receives both positional and keyword arguments, the error message returned
when the number of arguments is incorrect is misleading, e.g.:
max(foo=1)
Ezio Melotti added the comment:
I thought about that, but wanted to make a distinction between the form that
accepts only 1 arg and returns an item and the form that receives 2+ args and
returns a tuple.
--
nosy: +ezio.melotti
___
Python tracker
Ezio Melotti added the comment:
I created #16543 for PyArg_UnpackTuple.
Once that is fixed we can continue with this.
--
dependencies: +Use positional arguments in PyArg_UnpackTuple
___
Python tracker rep...@bugs.python.org
Changes by Mark Dickinson dicki...@gmail.com:
--
nosy: +mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16543
___
___
Serhiy Storchaka added the comment:
+(min == 1 ? : s), l);
In second part of patch should be max. Reformat the code so that `min` and
`(min == 1 ? : s)` will be in one line and it will be more clear.
--
nosy: +serhiy.storchaka
Chris Jerdonek added the comment:
You can also make that distinction using *. For example:
.. function:: attrgetter(attr, *attrs)
or
.. function:: attrgetter(attr)
attrgetter(attr1, attr2, *attrs)
(cf. http://docs.python.org/dev/library/functions.html#max )
Elsewhere we
Mark Dickinson added the comment:
Now that I look at uses of PyArg_UnpackTuple, I'm wondering whether this needs
to be fixed at all. Apart from `max` and `min`, do you know of any other cases
where this gives a misleading error message?
Almost all the uses I can find are for simple
Mark Dickinson added the comment:
Of course, the 'arguments' - 'argument' fix would still be nice to have.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16543
___
Ezio Melotti added the comment:
do you know of any other cases where this gives a misleading error message?
Actually my concern was about cases where the new error might be
wrong/misleading, but I haven't checked yet. If there are no such cases I
think we should fix it; the error message
Mark Dickinson added the comment:
One more thing: I'm not sure this is the right terminology. Here we're using
'positional' to refer to parameters that PEP 362 calls POSITIONAL_ONLY,
whereas the regular TypeErrors (e.g. produced for user-defined functions) use
'positional' to mean what PEP
Roundup Robot added the comment:
New changeset 31bb42754962 by Chris Jerdonek in branch 'default':
Clarify that only the latest maintenance branches are rebuilt (issue #16528).
http://hg.python.org/devguide/rev/31bb42754962
--
nosy: +python-dev
___
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
keywords: +easy
resolution: invalid - fixed
type: behavior - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16528
___
Mark Dickinson added the comment:
If there are no such cases I think we should fix it.
Okay, but what exactly is this fixing? I can't find any examples apart from
max and min where the new error messages seem any better than the old. Your
first message talks about a function that receives
Ezio Melotti added the comment:
Okay, but what exactly is this fixing?
If the function parses positional args, it should say so in the error message.
If the function is never used (except for min/max) or if the error is never
reported, then we have a different problem.
Even if this code
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
nosy: +chris.jerdonek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16543
___
___
Antoine Pitrou added the comment:
Thank you Lorenzo. Your patch lacks a couple of details, such as versionadded
and versionchanged tags, but I can handle this myself.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4473
Ezio Melotti added the comment:
Buildbots are happy, closing.
Thanks Serhiy for the patches!
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16306
___
Roundup Robot added the comment:
New changeset 79e33578dc05 by Antoine Pitrou in branch 'default':
Issue #4473: Ensure the socket is shutdown cleanly in POP3.close().
http://hg.python.org/cpython/rev/79e33578dc05
New changeset d30fd9834cec by Antoine Pitrou in branch 'default':
Issue #4473: Add
Antoine Pitrou added the comment:
Patches committed. Thank you very much!
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4473
Chris Jerdonek added the comment:
Here we're using 'positional' to refer to parameters that PEP 362 calls
POSITIONAL_ONLY, whereas the regular TypeErrors (e.g. produced for
user-defined functions) use 'positional' to mean what PEP 362 calls
POSITIONAL_OR_KEYWORD.
Here the error message
Roundup Robot added the comment:
New changeset fe2200c1c2d3 by Vinay Sajip in branch '3.3':
Issue #16519: Used os.path.abspath, removed unnecessary code for
executable_name.
http://hg.python.org/cpython/rev/fe2200c1c2d3
New changeset a874c4a6ad5f by Vinay Sajip in branch 'default':
Closes
Antoine Pitrou added the comment:
Ah, thank you! There is a test failure on 3.2, but it's probably unrelated.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16532
Neil Girdhar added the comment:
My suggestion is then to update collection.abc to have an InfiniteSequence,
which inherits from Iterable, and adds abstract methods __getitem__ and mixin
methods __iter__.
Then, itertools count, cycle, and repeat could implement
Serhiy Storchaka added the comment:
What kind of problem you want to solve? I'm sure there is a simple enough
solution without changing itertools objects.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16540
Chris Jerdonek added the comment:
This can be fixed by adding positional before arguments in the error
message.
Do we know for sure that the values in the args argument in a call to
PyArg_UnpackTuple always correspond to the positional arguments of a call to a
Python function? Can
Vinay Sajip added the comment:
IIUC, Debian Experimental is not a complete distribution. Are there other,
non-experimental OS variants where posix_local is used with Python 3.x?
On my Ubuntu Oneiric and Precise 64-bit machines, the default install scheme on
the official Python 3.2 - as
Neil Girdhar added the comment:
My code looks like this:
presignal_abd = [[], [0.1, 0.6], []]
tarsignal_abd = [[], [0.4, 0.9], []]
diagsignal_abd = [[], [0.1, 0.6, 0.7, 0.8], []]
# etc.
for (filename,
observations,
presignals,
tarsignals,
diagsignals,
diagram_type) in
Mark Dickinson added the comment:
Here the error message is about positional arguments, which are
different from parameters.
Okay. So is it also planned to change the existing error messages for
user-defined functions? E.g.:
def f(a, b=1):
... pass
...
f()
Traceback (most recent
Terry J. Reedy added the comment:
I marked this as 3.3+ bug because double reporting is new in 3.x and 'from
None' is new in 3.3 (it causes a TypeError in the raise statement ;-).
Command prompt output appears 'correct' (as intended).
[I added blank lines before each try: for reading ease]
Serhiy Storchaka added the comment:
Why not use `dummy = [[]] * 3` as dummy?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16540
___
___
Ezio Melotti added the comment:
Maybe we should follow a more systematic approach and collect the different
errors raised in the different situations, and then come up with error messages
that are accurate and follow the terminology that we are adopting in #15990.
--
Changes by Piotr Dobrogost p...@bugs.python.dobrogost.net:
--
nosy: +piotr.dobrogost
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8109
___
___
Chris Jerdonek added the comment:
TypeError: f() missing 1 required positional argument: 'a'
Yes, I think this should also be changed because passing a as a keyword
argument is okay:
f(a=1)
I would suggest something like--
TypeError: f() missing argument for parameter 'a'
--
Serhiy Storchaka added the comment:
On Linux the result is the same.
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16491
___
Ezio Melotti added the comment:
I would be fine with just dropping positional there, and say required
argument. With no further specification it means the default type of
argument, i.e. positional or keyword. See also the end of msg170876.
--
___
Gregory P. Smith added the comment:
Any code conversion is useful. This will help with old libraries and is
even good for just updating old 2.4 code to 2.7 best practices.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2454
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +gregory.p.smith
versions: +Python 3.3, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10712
___
1 - 100 of 142 matches
Mail list logo
