[issue13992] Segfault in PyTrash_destroy_chain
Georg Brandl added the comment: Picked as 5aa1bc2f00ad. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13992 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Stefan Krah added the comment: Infinities do not have payloads. It's a bug in decimal.py that it accepts non-empty coefficients when constructing infinities. Since there was a corresponding unit test for as_tuple(), I've kept the wrong representation for _decimal: # XXX non-compliant infinity payload. d = Decimal(Infinity) self.assertEqual(d.as_tuple(), (0, (0,), 'F') ) But this unit test is only executed for the Python version: # XXX coefficient in infinity should raise an error if self.decimal == P: d = Decimal( (0, (4, 5, 3, 4), 'F') ) self.assertEqual(d.as_tuple(), (0, (0,), 'F')) d = Decimal( (1, (0, 2, 7, 1), 'F') ) self.assertEqual(d.as_tuple(), (1, (0,), 'F')) My suggestion is to disallow non-empty tuples for decimal.py and change the infinity tuple to (0, (), 'F'). -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Mark Dickinson added the comment: It's a bug in decimal.py that it accepts non-empty coefficients when constructing infinities. On what grounds is it a bug? I might call it a poor design decision, but it's clearly intentional. There's even a unit test for it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Stefan Krah added the comment: Mark Dickinson rep...@bugs.python.org wrote: On what grounds is it a bug? I might call it a poor design decision, but it's clearly intentional. There's even a unit test for it. Maybe bug is not the right word. I'd call it a deviation from the specification then. Do you happen to know what the intention was? If from_tuple(..., 'F') accepts coefficients, logically Decimal(Infinity0), Decimal(Infinity123) etc. should be accepted as well. But they're not part of the grammar and decimal.py rejects them. http://speleotrove.com/decimal/daconvs.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Mark Dickinson added the comment:
I'd call it a deviation from the specification then.
Do you happen to know what the intention was?
Well, we're kinda outside the specification here.
Rightly or wrongly, Decimal('infinity').as_tuple() was originally implemented
to return (0, (0,), 'F'); I'm fairly sure that was intentional, and I think
that the Decimal constructor should continue to accept that tuple as a
representation of infinity---else we're risking breaking existing code.
I think I may have muddied the waters at some later stage by modifying the
constructor to ignore the second argument on input, so that (0, (), 'F') and
(0, (0,), 'F') both work on input. Or maybe it was already the case that the
second argument was ignored; I'm not sure about that.
I do agree that (0, (), 'F') is a better representation of infinity, and it
would have been a little better if that had been used from the start, but I
don't think it's worth the potential breakage or the deprecation cycles
involved in 'fixing' this.
If it helps at all, it would probably be safe to disallow tuples other than ()
and (0,); I doubt anyone's intentionally passing anything else here.
So:
+1 on allowing ((0, (0,), 'F')) as input in _decimal. I do see this report as
a regression from 3.2 that should be fixed.
-0 on changing Infinity.as_tuple() to (0, (), 'F'), and perhaps then
deprecating ((0, (0,), 'F') as a legal input.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15882
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15629] Add to regrtest the ability to run Lib and Doc doctests
Chris Jerdonek added the comment: Attached is a patch that adds to regrtest the ability to run doctests in both library modules and documentation files (specifically, in the non-test modules in Lib/ and in the *.rst files in Doc/). The syntax to run all doctests is-- python -m test --doctests --docdir path-to-doc If --docdir is left out, only module doctests are run. You can run the doctests for individual files and modules by including test names of the form fdoc:library/builtins.rst and mdoc:html.parser (for file doctests and module doctests, respectively). Doctests for a module are only run if the module has a variable `_doctest_safe` that evaluates to True. I haven't yet added a mechanism to mark a documentation file as doctest safe or to skip importing a library module entirely (when running all tests). -- components: +Tests keywords: +patch title: Run doctests in Doc/*.rst as part of regrtest - Add to regrtest the ability to run Lib and Doc doctests Added file: http://bugs.python.org/file27146/issue-15629-1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15629 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15868] leak in bytesio.c
Roundup Robot added the comment: New changeset df663603e67a by Stefan Krah in branch '3.2': Issue #15868: Fix refleak in bytesio.c (Coverity #715365). http://hg.python.org/cpython/rev/df663603e67a -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15868] leak in bytesio.c
Stefan Krah added the comment: Thanks for taking a look! -- resolution: - fixed stage: - committed/rejected status: open - closed versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Changes by Mark Dickinson dicki...@gmail.com: -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15340] OSError with import random when /dev/urandom doesn't exist (regression from 2.6)
Martin v. Löwis added the comment: It's actually up to Barry (and Benjamin) to decide whether to apply this to 2.6 (and 3.1). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15340 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Stefan Krah added the comment: It's an implementation detail of decimal.py to represent infinity with a coefficient of '0' instead of the empty string: Decimal(inf)._int '0' So IMO the tuple representation exposes that implementation detail. I'm still not sure why that was done or what the benefit was. For cdecimal, initializing a coefficient for infinity is completely meaningless, since infinities simply don't have a coefficient. So the representation DecimalTuple(sign=0, digits=(0,), exponent='F'), which I took over for compatibility, is factually wrong for cdecimal. Of course, exponent='F' is also wrong. I don't mind that as much, because there is a direct mapping to the input strings of the grammar. I think the tuple representation isn't that useful to begin with. In all use cases I've seen, people are a) reading the tuple an b) converting the coefficient tuple back to a Python integer. So, I'd really like to deprecate the whole interface in favor of either a read-only interface: x.sign - 0 or 1 (perhaps even 1 or -1) x.coeff - Python integer x.exp- Python integer If x is special, raise InvalidOperation. People usually need to check for specials anyhow. Or a tuple interface with an integer coefficient (sign=0, coeff=12345, exponent=99), where special numbers are not allowed in accordance with http://speleotrove.com/decimal/damodel.html: Finite numbers are defined by three integer parameters When a number has one of these special values, its coefficient and exponent are undefined. That said, I don't mind if construction continues to work with the implementation specific value of (0,), so let's do that. -- assignee: - skrah type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Mark Dickinson added the comment: So, I'd really like to deprecate the whole interface in favor of either a read-only interface: x.sign - 0 or 1 (perhaps even 1 or -1) x.coeff - Python integer x.exp- Python integer If x is special, raise InvalidOperation. People usually need to check for specials anyhow. Sure; that works for me. I don't like the current interface any more than you do, and I've always found it unnecessarily awkward to turn finite decimals into triples and back again. But I think that's a different issue. What we have here is a real regression that seems likely to break existing code, and I think that should be fixed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Mark Dickinson added the comment: read-only interface: x.sign - 0 or 1 (perhaps even 1 or -1) x.coeff - Python integer x.exp- Python integer The only slightly awkward thing with this (for high-precision decimals) is the quadratic conversion (well, okay, perhaps subquadratic depending on what algorithms are being used, but still ...) required to get from the decimal coefficient to a Python integer, and vice versa. It may be better to use a (byte)string of digits instead of a Python integer for the coefficient. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Stefan Krah added the comment: Mark Dickinson rep...@bugs.python.org wrote: So, I'd really like to deprecate the whole interface in favor of either a read-only interface: But I think that's a different issue. Yep. I was using all this as a rationale that the current tuple interface does not matter all that much. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15822] installed python may fail incorrectly trying to rebuild lib2to3 grammar pickles
Martin v. Löwis added the comment: I think PYTHON_FOR_BUILD includes -E to make sure that if PYTHONPATH (or PYTHONHOME) is set that it then won't affect the build. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15822 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15871] Online docs: make index search always available.
Ezio Melotti added the comment:
If I search for random, at the top of the result lists I want to see at least
the random module and the random.random function.
Currently the random module is the 4th result, and random.random is buried
down in the list (17th place) among all the other random.* functions.
The results are generated by the query() function in searchtools.js, and AFAIU
it generates 3 lists, importantResults, objectResults, unimportantResults, that
get then sorted independently in alphabetic order by the object fullname, and
concatenated.
I experimented a bit and one way to get exact matches to the top is to add
before the switch at line 370 something like
if (fullname == object) {
importantResults.push(result);
continue;
}
This will include random, but not random.random.
Other possible variations are
if ((fullname == object) || (fullname.split('.').pop() == object)) {
or
if ((fullname == object) || $.inArray(object, fullname.split('.')) -1)
Here fullname is e.g. random.random, $.inArray(object, fullname.split('.'))
-1 is the jquery equivalent of Python's object in fullname.split('.').
Another way to address the problem is to change the sorting algorithm to move
near the top results like random and random.random.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15871
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Stefan Krah added the comment: Aaron, did you encounter this problem in a real world application? I'm asking because it would be interesting to know if people use this. Google is pretty silent on Decimal((0, (0,), 'F')), but perhaps that is not an ideal search term. Mark, I'm uploading a minimal patch. I'm OK with that going into 3.3.0, if you manage to convince Georg. :) -- Added file: http://bugs.python.org/file27147/issue15882.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15883] Add Py_errno to work around multiple CRT issue
New submission from Christian Heimes:
errno is usually implemented as thread local variable, more precisely as a
macro that calls a function which returns the memory address of a thread local
variable. Each C runtime library has its own function and TLS which introduces
an issue when a Python extension uses a different CRT than the core. AFAIK that
an issue only an issue on Windows with other versions of Visual Studio.
This means that mixed CRTs break the three PyErr_SetFromErrno* functions as
they always access the errno of the core's CRT. The patch adds a Py_errno macro
that must be used in extensions before a PyErr_SetFromErrno() function is used.
Example:
fd = open(filename, O_RDONLY);
if (fd == -1) {
Py_errno = errno;
return PyErr_SetFromErrnoWithFilename(PyExc_OSError, filename);
}
The issue was discovered by me a about two weeks ago and further analyzed by
Martin. http://mail.python.org/pipermail/python-dev/2012-August/121460.html
--
components: Build, Extension Modules, Interpreter Core
files: pyerrno.patch
keywords: patch
messages: 170050
nosy: christian.heimes, georg.brandl, loewis, pitrou
priority: normal
severity: normal
stage: patch review
status: open
title: Add Py_errno to work around multiple CRT issue
type: behavior
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file27148/pyerrno.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15883
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15814] memoryview: equality-hash invariant
Roundup Robot added the comment: New changeset ca81b9a3a015 by Stefan Krah in branch 'default': Issue #15814: Update whatsnew to the current state of hashing memoryviews. http://hg.python.org/cpython/rev/ca81b9a3a015 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15814 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15814] memoryview: equality-hash invariant
Stefan Krah added the comment: Georg, thanks for including all changes that I've asked for! If you still have the patience for the constant stream of memoryview doc changes, there are three new ones that might be worth including: 3b2597c1fe35 c9c9d890400c ca81b9a3a015 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15814 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15883] Add Py_errno to work around multiple CRT issue
Martin v. Löwis added the comment: Since this is a new feature, it needs to go into 3.4. -- versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15883 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15871] Online docs: make index search always available.
Changes by Ramchandra Apte maniandra...@gmail.com: -- nosy: +ramchandra.apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15871 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15844] weird import errors
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15844 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15845] Fixing some byte-to-string conversion warnings
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15845 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15852] typos in curses argument error messages
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15852 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15851] Lib/robotparser.py doesn't accept setting a user agent string, instead it uses the default.
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15851 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15875] tarfile may not make @LongLink for non-ascii character
Changes by Lars Gustäbel l...@gustaebel.de: -- assignee: - lars.gustaebel nosy: +lars.gustaebel versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10224] Build 3.x documentation using python3.x
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10224 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13922] argparse handling multiple -- in args improperly
Roundup Robot added the comment: New changeset 5d8454fcc629 by R David Murray in branch '3.2': #15847: allow args to be a tuple in parse_args http://hg.python.org/cpython/rev/5d8454fcc629 New changeset 76655483c5c8 by R David Murray in branch 'default': merge #15847: allow args to be a tuple in parse_args http://hg.python.org/cpython/rev/76655483c5c8 New changeset a2147bbf7868 by R David Murray in branch '2.7': #15847: allow args to be a tuple in parse_args http://hg.python.org/cpython/rev/a2147bbf7868 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13922 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15847] parse_args stopped accepting tuples
Roundup Robot added the comment: New changeset 5d8454fcc629 by R David Murray in branch '3.2': #15847: allow args to be a tuple in parse_args http://hg.python.org/cpython/rev/5d8454fcc629 New changeset 76655483c5c8 by R David Murray in branch 'default': merge #15847: allow args to be a tuple in parse_args http://hg.python.org/cpython/rev/76655483c5c8 New changeset a2147bbf7868 by R David Murray in branch '2.7': #15847: allow args to be a tuple in parse_args http://hg.python.org/cpython/rev/a2147bbf7868 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15847 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15847] parse_args stopped accepting tuples
R. David Murray added the comment: Thanks, Zbyszek. I'm glad you caught this. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15847 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15842] Some SocketIO methods can succeed after close()
Antoine Pitrou added the comment: Actually, I've found a couple of issues with the patch: - it doesn't address seekable(); seekable() should also raise ValueError - the test should be done with makefile(..., buffering=0), so that SocketIO is actually tested, rather than the buffered object wrapping it -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15842 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15510] textwrap.wrap('') returns empty list
Roundup Robot added the comment: New changeset 65e5f28801e1 by R David Murray in branch '3.2': #15510: clarify textwrap's handling of whitespace, and add confirming tests. http://hg.python.org/cpython/rev/65e5f28801e1 New changeset 0e9ad455355b by R David Murray in branch 'default': Merge #15510: clarify textwrap's handling of whitespace, and add confirming tests. http://hg.python.org/cpython/rev/0e9ad455355b New changeset fca48971ac35 by R David Murray in branch '2.7': #15510: clarify textwrap's handling of whitespace, and add confirming tests. http://hg.python.org/cpython/rev/fca48971ac35 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15510 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15510] textwrap.wrap('') returns empty list
R. David Murray added the comment: Thanks, Chris. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15510 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15865] reflect bare star * in function signature documentation
Roundup Robot added the comment: New changeset a30b3915228b by Ezio Melotti in branch '3.2': #15865: add * in the signature to document keyword-only args in the docs. Patch by Chris Jerdonek. http://hg.python.org/cpython/rev/a30b3915228b New changeset 694c725f241a by Ezio Melotti in branch 'default': #15865: merge with 3.2. http://hg.python.org/cpython/rev/694c725f241a -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15865] reflect bare star * in function signature documentation
Ezio Melotti added the comment: Fixed, thanks for the patch! -- assignee: docs@python - ezio.melotti resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15884] PEP 3121, 384 Refactoring applied to ctypes module
Changes by Alexander Belopolsky alexander.belopol...@gmail.com: -- assignee: belopolsky nosy: belopolsky priority: normal severity: normal status: open title: PEP 3121, 384 Refactoring applied to ctypes module type: resource usage versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15884 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15787] PEP 3121 Refactoring
Changes by Alexander Belopolsky alexander.belopol...@gmail.com: -- dependencies: +PEP 3121, 384 Refactoring applied to ctypes module ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15787 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15882] _decimal.Decimal constructed from tuple
Aaron added the comment: I did not encounter this in a regular application. I do use the decimal module, and was excited to see the adoption of a faster C version, so I was just reading through the code to see how it worked. I can't think of a situation where I would need to construct a decimal from a tuple and not a string or some other numeric type, though. For what it's worth, I think that as long as construction from tuples is supported, Decimal(d.as_tuple()) should work for all Decimal objects d. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15882 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15222] mailbox.mbox writes without empty line after each message
R. David Murray added the comment: Looks like reitveld doesn't recognize your patch format, Petri. Instead of having the write_line flag, how about doing the newline write in the if body? A 'lastline=line' at the end of the loop in the buffer loop case is probably less expensive than doing the if test every time through that loop. Otherwise, it looks good to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15222 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5088] optparse: inconsistent default value for append actions
Roundup Robot added the comment: New changeset 8c60bb098eff by R David Murray in branch '3.2': #5088: document behavior of optparse defaults with 'append' action. http://hg.python.org/cpython/rev/8c60bb098eff New changeset 0c2bdd2c2032 by R David Murray in branch 'default': Merge #5088: document behavior of optparse defaults with 'append' action. http://hg.python.org/cpython/rev/0c2bdd2c2032 New changeset 79f6d4aff39d by R David Murray in branch '2.7': closes #5088: document behavior of optparse defaults with 'append' action. http://hg.python.org/cpython/rev/79f6d4aff39d -- nosy: +python-dev resolution: accepted - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15744] missing tests for {RawIO,BufferedIO,TextIO}.writelines
Changes by Kyle Roberts roberts...@gmail.com: -- nosy: +kyle.roberts ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15744 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15820] Add additional info to Resources area on Dev Guide
Roundup Robot added the comment: New changeset 18e31605b161 by R David Murray in branch 'default': #15820: Improve the Helping with the Devguide section http://hg.python.org/devguide/rev/18e31605b161 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15820 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15820] Add additional info to Resources area on Dev Guide
R. David Murray added the comment: I incorporated your ideas into the update I made, including at least one that Ezio may have rejected...he can blame me :) Thanks, Mike. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15820 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15871] Online docs: make index search always available.
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15871 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6074] .pyc files created readonly if .py file is readonly, python won't overwrite
Kevin Chen added the comment: Hi Eric, I am happy to install Python 3.3 on Windows and help you test this. Can you please give me some ideas on what I need to do? Do I sync to the latest Python 3.3 branch and compile? Then run some unit-test code? Which test files should I run? What should I be expecting? Also, do you know if anyone is working on adding the fix and test to Python 2.7? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6074 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15842] Some SocketIO methods can succeed after close()
Alessandro Moura added the comment: Fixed seekable(), and amended tests; see patch. -- Added file: http://bugs.python.org/file27149/socket.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15842 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15844] weird import errors
Changes by Ezio Melotti ezio.melo...@gmail.com: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15844 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15848] PEP 3121, 384 Refactoring applied to xxsubtype module
Alexander Belopolsky added the comment: It looks like your patch will result in reference leaks if type creation fails. I think you should add Py_DECREF(m) before error returns. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15848 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15885] @staticmethod __getattr__ doesn't work
New submission from Albert Zeyer:
Code:
```
class Wrapper:
@staticmethod
def __getattr__(item):
return repr(item) # dummy
a = Wrapper()
print(a.foo)
```
Expected output: 'foo'
Actual output with Python 2.7:
Traceback (most recent call last):
File test_staticmethodattr.py, line 7, in module
print(a.foo)
TypeError: 'staticmethod' object is not callable
Python 3.2 does return the expected ('foo').
PyPy returns the expected 'foo'.
--
components: Interpreter Core
messages: 170070
nosy: Albert.Zeyer
priority: normal
severity: normal
status: open
title: @staticmethod __getattr__ doesn't work
versions: Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15885
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15822] installed python may fail incorrectly trying to rebuild lib2to3 grammar pickles
Roundup Robot added the comment: New changeset 2def9ef683da by Ned Deily in branch '2.7': Issue #15822: Fix installation of lib2to3 grammar pickles to ensure http://hg.python.org/cpython/rev/2def9ef683da New changeset adc5e6aca251 by Ned Deily in branch '3.2': Issue #15822: Fix installation of lib2to3 grammar pickles to ensure http://hg.python.org/cpython/rev/adc5e6aca251 New changeset a829889f96b0 by Ned Deily in branch 'default': Issue #15822: Fix installation of lib2to3 grammar pickles to ensure http://hg.python.org/cpython/rev/a829889f96b0 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15822 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15822] installed python may fail incorrectly trying to rebuild lib2to3 grammar pickles
Ned Deily added the comment: I like Martin's suggested approach. It is explicit and much cleaner than the changes we introduced for Issue15645 as well as the original. The applied changes revert the previous changes and instead implement an explicit build of the two pickles directly in the installed lib2to3 during make install regardless of the presence of pickles in the build directory. This also resolves Issue15838. Georg, I think a829889f96b0 should be considered for inclusion in 3.3.0. Ronald, if you want to pursue the $PYTHON_FOR_BUILD -E issue, it would be best to use another specific issue for that. -- resolution: - fixed stage: patch review - committed/rejected status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15822 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15822] installed python may fail incorrectly trying to rebuild lib2to3 grammar pickles
Changes by Ned Deily n...@acm.org: -- status: pending - open Removed file: http://bugs.python.org/file27084/issue15822_33.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15822 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15838] make install tries to create lib2to3 grammar pickles in source directory
Ned Deily added the comment: This problem is resolved by the fixes for Issue15822 which implements a more explicit way of installing the grammar pickles. -- resolution: - duplicate stage: needs patch - committed/rejected status: open - closed superseder: - installed python may fail incorrectly trying to rebuild lib2to3 grammar pickles ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15838 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15645] 2to3 Grammar pickles not created when upgrading to 3.3.0b2
Ned Deily added the comment: Is it really possible that the pickle is created after calculation of the wildcard expansion? With the current GNUmake, it seems it is not possible. GNUmake appears to serializes the individual steps in a target's recipe although I did not find an explicit guarantee in its documentation that that could never happen. (I did find at least one proprietary make replacement that does try to parallelize the individual steps in one target.) In any case, there were other problems with the approach implemented here and these changes have been superseded by those of Issue15822. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15645 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6074] .pyc files created readonly if .py file is readonly, python won't overwrite
Nick Coghlan added the comment: It's still on my list to follow up (along with the other contributions from the PyCon AU sprints). However, if Eric gets a Windows environment up and running before I get to it, I'm happy to hand the issue over (I rely on the buildbots to sanity check Windows fixes). -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6074 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15885] @staticmethod __getattr__ doesn't work
Eric Snow added the comment: In Python 2 the code example generates an old-style class. When I tried it with a new style class, it worked fine: class Wrapper(object): @staticmethod def __getattr__(item): return repr(item) # dummy a = Wrapper() print(a.foo) # 'foo' Chalk this up to another reason to move to Python 3. wink -- nosy: +eric.snow resolution: - rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15873] datetime cannot parse ISO 8601 dates and times
Changes by Chris Rebert pyb...@rebertia.com: -- nosy: +cvrebert ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14649] doctest.DocTestSuite error misleading when module has no docstrings
R. David Murray added the comment: OK, 3.2 passes now, but when I merge to 3.3 I get failures. test_zipimport_support doesn't work on 2.7 either, but there we could just not backport the tests. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14649 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14649] doctest.DocTestSuite error misleading when module has no docstrings
Chris Jerdonek added the comment: I prepared the patch against 3.3 (default), so I wouldn't have expected it to work against 3.2 without further changes. The behavior in 3.3 after merging is also surprising given that it worked in 3.2 (and for me with direct application). I will look into it and report back -- providing 3.2 and a delta patch, if necessary. I just wanted to be sure you were okay with the patch for the default branch before doing that extra work. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14649 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
