[issue15716] Ability to specify the PYTHONPATH via a command line flag

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12370] Use of super overwrites use of __class__ in class namespace

Daniel Urban added the comment: Thanks for the review! Nick, the example with Outer, InnerParent and InnerChild still works (the evaluation happens before we enter the new scope). Of course you're all right about __args__ and __kw__. I'll try to find a way to hide them. -- stage: pat

[issue16568] allow constructors to be documented separately from class

New submission from Chris Jerdonek: This issue is to settle on and provide a way to document the constructor of a class separately from the overall summary/description of a class. This is something that Ezio, Nick, and I discussed briefly on IRC a few hours ago. We all see the value in it. C

[issue16209] add a "class str" entry to the docs

Roundup Robot added the comment: New changeset 0097379df2e1 by Chris Jerdonek in branch '3.3': Add a str class entry to the "Text Sequence Type" section (issue #16209). http://hg.python.org/cpython/rev/0097379df2e1 New changeset 81ac75c64780 by Chris Jerdonek in branch 'default': Merge from 3.3:

[issue16209] add a "class str" entry to the docs

Changes by Chris Jerdonek : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue13475] Add '-p'/'--path0' command line option to override sys.path[0] initialisation

Kristján Valur Jónsson added the comment: before or after running site.py? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue13475] Add '-p'/'--path0' command line option to override sys.path[0] initialisation

Nick Coghlan added the comment: I'd suggest this would be applied at the same time as when sys.path[0] gets set now, but that kind of messy complication is why I decided we really needed to step back and start trying to clean up what we already have before we started layering yet *more* compli

[issue16205] update :class:`str` references to link to the str type section

Chris Jerdonek added the comment: This was addressed by issue #16209 since with that change :class:`str` and :func:`str` now both go to the new str class entry in the string type section. See also the new issue #16568. -- resolution: -> duplicate status: open -> closed superseder: -

[issue13475] Add '-p'/'--path0' command line option to override sys.path[0] initialisation

Kristján Valur Jónsson added the comment: Absolutely, Nick. Perhaps we ought to start gathering a list of real world requirements, i.e. how do people run, or want to run, python? -- ___ Python tracker

[issue16323] Wrong C API documentation for locale encoding

Roundup Robot added the comment: New changeset 11629c14ce1f by Andrew Svetlov in branch '3.3': Issue #16323: Fix wrong C API documentation for locale encoding. http://hg.python.org/cpython/rev/11629c14ce1f New changeset 6f3d3003acf3 by Andrew Svetlov in branch 'default': Merge issue #16323: Fix

[issue16323] Wrong C API documentation for locale encoding

Andrew Svetlov added the comment: Fixed. Thanks. -- nosy: +asvetlov resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue15990] solidify argument/parameter terminology

Roundup Robot added the comment: New changeset 69d5d834c5cb by Chris Jerdonek in branch '3.2': Improve argument/parameter documentation (issue #15990). http://hg.python.org/cpython/rev/69d5d834c5cb New changeset 40fd26a4206b by Chris Jerdonek in branch '3.3': Merge from 3.2: improve argument/par

[issue15990] solidify argument/parameter terminology

Chris Jerdonek added the comment: I realize now that this would also be good for 2.7. I will try to do that tomorrow. -- versions: +Python 2.7, Python 3.2 ___ Python tracker __

[issue16567] Implementing .= for variable operator

Amaury Forgeot d'Arc added the comment: Please submit this kind of ideas to the python-ideas mailing list, to trigger a discussion and get valuable feedback: http://www.python.org/community/lists/#python-ideas-mailing-list -- nosy: +amaury.forgeotdarc resolution: -> invalid status: ope

[issue16323] Wrong C API documentation for locale encoding

Serhiy Storchaka added the comment: I think the sentence "If a byte sequence can be decoded as a surrogate character and *errors* is not ``"strict"``, then the byte sequence is escaped using the ``"surrogateescape"`` error handler instead of being decoded." is redundant. -- _

[issue16554] The description of the argument of MAKE_FUNCTION and MAKE_CLOSURE is incorrect

Daniel Urban added the comment: Sorry, I won't have time for that in the following weeks. -- ___ Python tracker ___ ___ Python-bugs-li

[issue16566] Structure._anonymous_ should not allow strings

anatoly techtonik added the comment: I agree with you on a generic case, where "Special cases aren't special enough to break the rules.", but this special case in ctypes and _anonymous_ context is where the rule "Although practicality beats purity." should apply. Otherwise I can't see any exam

[issue9720] zipfile writes incorrect local file header for large files in zip64

Serhiy Storchaka added the comment: Patches updated to resolve merge conflict with issue11981. Please review and apply any of this patches. This is needed for some other my zipfile patches. -- Added file: http://bugs.python.org/file28145/zipfile_zip64_always_2.patch Added file: http://b

[issue16566] Structure._anonymous_ should not allow strings

Amaury Forgeot d'Arc added the comment: OTOH, __slots__ also allows a single string, but it is silently converted to a 1-tuple: class C: __slots__ = 'abc' assert 'abc' in C.__dict__ -- nosy: +amaury.forgeotdarc status: pending -> open ___ Python

[issue16323] Wrong C API documentation for locale encoding

Andrew Svetlov added the comment: Really I don't know what's better. Victor, what do you think? -- ___ Python tracker ___ ___ Python-b

[issue16333] Trailing whitespace in json dump when using indent

anatoly techtonik added the comment: > The reason is that people might rely on exact output and it's not nice to > break their code in a bugfix release. This code has a very bad smell. Between supporting people who did that and teaching them a lesson I choose the latter, but I bet the situatio

[issue16547] IDLE raises an exception in tkinter after fresh file's text has been rendered

Lukas Lueg added the comment: @Roger: Triggering the segfault on MacOS 10.6 requires some interaction with the text-window while the text is being rendered. This includes moving the window or just clicking into it's canvas. Carefully leaving the window alone while colorization is going on avoi

[issue15716] Ability to specify the PYTHONPATH via a command line flag

Changes by Martin Dengler : -- nosy: +mdengler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16499] CLI option for isolated mode

Changes by Martin Dengler : -- nosy: +mdengler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16333] Trailing whitespace in json dump when using indent

R. David Murray added the comment: "Code smell" and "Easily fixable on their side" are not an arguments that apply here. We have a strong backward compatibility policy that strives not to break working code in bug fix releases. And yes, this means that there are sometimes bugs that we only f

[issue16569] Preventing errors of simultaneous access in zipfile

New submission from Serhiy Storchaka: If the ZipFile was created by passing in a file-like object as the first argument to the constructor, then simultaneous reading or writing of different file results in an non-consistent state. There is a warning about this in the documentation. The propose

[issue16557] PEP 380 isn't reflected in the Functional Programming HOWTO

Changes by Andrew Svetlov : -- keywords: +easy stage: -> needs patch type: -> enhancement versions: +Python 3.4 ___ Python tracker ___ _

[issue16570] Absolute imports fail to take full path into account?

New submission from Dirkjan Ochtman: This seems confusing: djc@enrai test $ ls -lR .: total 0 drwxr-xr-x 4 djc users 160 Nov 28 15:35 pkg ./pkg: total 4 -rw-r--r-- 1 djc users 39 Nov 28 15:37 http.py -rw-r--r-- 1 djc users 0 Nov 28 15:34 __init__.py drwxr-xr-x 3 djc users 136 Nov 28 15:40 te

[issue16569] Preventing errors of simultaneous access in zipfile

Jesús Cea Avión added the comment: I am -0 to this. We can't prevent programmers for shotting in the foot. -- nosy: +jcea ___ Python tracker ___ _

[issue16323] Wrong C API documentation for locale encoding

STINNER Victor added the comment: "If a byte sequence can be decoded as a surrogate character and *errors* is not ``"strict"``, then the byte sequence is escaped using the ``"surrogateescape"`` error handler instead of being decoded." I don't understand this sentence but it sounds to be wrong. T

[issue16569] Preventing errors of simultaneous access in zipfile

Serhiy Storchaka added the comment: Reading from closed ZipFile or reading from ZipFile opened for write already forbidden. This is a preventing of the same kind. -- ___ Python tracker

[issue16333] Trailing whitespace in json dump when using indent

anatoly techtonik added the comment: The problem with policy and 'common sense' is that not everybody can feel that 'common sense', especially when there is no time to go deep into the issue. Policy is a quick and good 42 no matter that the matter is. The problem that it is also a filter, whic

[issue16565] Increase Py_AddPendingCall array size

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue16333] Trailing whitespace in json dump when using indent

Serhiy Storchaka added the comment: Here is a patch which adds a suggestion to use appropriate separators with indent. It also use they in Lib/json/tool.py. I suggest this patch only for old Python, up to 3.3. For 3.4 this is not needed if my previous suggestion will be accepted. -- A

[issue16571] Iterating over inconsistently-indented code block causes execution of code only on last iteration of loop

New submission from Brian Berard: When a loop (for loop in this case) contains multiple lines of code, if the lines are inconsistently indented, the for loop will only execute those lines on the final pass through the loop with no type of warning regarding indentation error. Ex. for i in r

[issue16571] Iterating over inconsistently-indented code block causes execution of code only on last iteration of loop

Changes by Brian Berard : -- type: behavior -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue16571] Iterating over inconsistently-indented code block causes execution of code only on last iteration of loop

Mark Dickinson added the comment: This is expected behaviour for Python 2.x: Python interprets every TAB character as advancing to the next multiple-of-8 column, regardless of how your editor sees it. It would be too disruptive to change this behaviour in Python 2.x. It's already fixed in P

[issue16571] Iterating over inconsistently-indented code block causes execution of code only on last iteration of loop

Changes by Serhiy Storchaka : -- stage: -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16474] More code coverage for imp module

Andrew Svetlov added the comment: I think nothing bad to push additional tests into 3.3 also. -- ___ Python tracker ___ ___ Python-bug

[issue15990] solidify argument/parameter terminology

Changes by Guido van Rossum : -- nosy: -gvanrossum, python-dev ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15627] Add a method to importlib.abc.SourceLoader for converting source to a code object

Brett Cannon added the comment: It might not be compulsory, but how else are you going to get a code object? Then again, get_code() kind of codifies the use of the word "code" for methods that return a code object. So if you want to do the work to change the name then go ahead. -- __

[issue11076] Iterable argparse Namespace

Roundup Robot added the comment: New changeset bbecbcff0ce4 by Andrew Svetlov in branch '3.2': Issue #11076: document the way to convert argparse.Namespace to a dict. http://hg.python.org/cpython/rev/bbecbcff0ce4 New changeset ee4e31845977 by Andrew Svetlov in branch '3.3': Merge issue #11076: d

[issue16570] Absolute imports fail to take full path into account?

Brett Cannon added the comment: This test example is nonsensical. You are directly executing a package which leads to pkg/tests being put in sys.path first. That means you end up with http in pkg/tests masking the one in the stdlib, which causes your ``from http.clients import HTTPConnection``

[issue11076] Iterable argparse Namespace

Andrew Svetlov added the comment: Sorry, looks like it work already was done. Reverting: c008f070f88a 814403d824a5 ddcf09a348ca -- nosy: +asvetlov resolution: -> duplicate stage: patch review -> committed/rejected status: open -> closed ___ Python t

[issue16570] Absolute imports fail to take full path into account?

Dirkjan Ochtman added the comment: It's not nonsensical. Something exactly like it came up while I was looking into porting couchdb-python to Python 3. couchdb-python has had a couchdb.http module for a while now; it didn't start clashing with the stdlib until Python 3. Also, I don't understan

[issue16570] Absolute imports fail to take full path into account?

Dirkjan Ochtman added the comment: Never mind, I get what you're getting at now. I thought that the cwd was added to the sys.path, not the containing directory for the executed script. I'll look into using __main__. Thanks! -- ___ Python tracker

[issue16570] Absolute imports fail to take full path into account?

Brett Cannon added the comment: When you execute a module on the command line, sys.path[0] is set to that containing directory (e.g. pkg/tests in your example; just have pkg/tests/__init__.py print out sys.path to see what I mean). ``import http`` is going to look on sys.path no matter what, a

[issue16570] Absolute imports fail to take full path into account?

Brett Cannon added the comment: Glad it makes sense now. =) I was writing my reply while you sent yours. Anyway, your PYTHONPATH setting goes on to sys.path *after* the directory containing the script being executed. This is so that when you execute Python code somewhere it will get the local

[issue16571] Iterating over inconsistently-indented code block causes execution of code only on last iteration of loop

Ned Batchelder added the comment: @Brian: Your code doesn't run in Python 2.7 as you've shown it, it produces an IndentationError. If your code is actually different, and does run, try running it with the -tt flag on Python, which will warn about inconsistent indentation. -- nosy: +

[issue16571] Iterating over inconsistently-indented code block causes execution of code only on last iteration of loop

Brian Berard added the comment: @nedbat I'm able to run that code as is and receive no such error. With the -tt option, I do receive an indentation error. I will keep that in mind. -- ___ Python tracker __

[issue16570] Absolute imports fail to take full path into account?

Eric Snow added the comment: Things are working as they should here. The key points: * when running a script, sys.path[0] is set to the script's directory (with no script sys.path[0] is set to the CWD, see issue13475), * pkg/tests/__init__.py is loaded and executed twice: once as the script un

[issue16570] Absolute imports fail to take full path into account?

Eric Snow added the comment: oops. too slow. :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue11076] Iterable argparse Namespace

Chris Jerdonek added the comment: Following up Andrew's last comment, for the record, it looks like this was done as part of issue 8982. -- nosy: +chris.jerdonek superseder: -> argparse docs cross reference Namespace as a class but the Namespace class is not documented __

[issue16568] allow constructors to be documented separately from class

Ezio Melotti added the comment: I was wondering if this should be called initializer instead of constructor. Another idea is to keep using the "method" directive and use :initializer: to differentiate it from the others. This might be easier to implement, but OTOH is not consistent with the

[issue16568] allow constructors to be documented separately from class

Changes by Ezio Melotti : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue16565] Increase Py_AddPendingCall array size

Amaury Forgeot d'Arc added the comment: This array would still have a fixed size. Could you arrange your code so that you enqueue pending calls elsewhere, and call Py_AddPendingCall only once until the pending items have been processed? -- nosy: +amaury.forgeotdarc

[issue16565] Increase Py_AddPendingCall array size

Antoine Pitrou added the comment: I just took a look at https://github.com/felipecruz/pyaio/commit/127372ba0a6dbca4045256dcd653789ee35f6a78 and it looks a bit silly to me: if the completion handler is called in a separate thread, then the completion handler can just take the GIL and put the r

[issue4806] Function calls taking a generator as star argument can mask TypeErrors in the generator

Changes by Chris Kaynor : -- nosy: +DragonFireCK ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue16333] Trailing whitespace in json dump when using indent

Ezio Melotti added the comment: > There is no promise of binary compatibility for pretty-printed data. This was the reason that made me consider backporting this on the other branches. After all I expect this feature to be used from the terminal, while printing JSON in a human-friendly format

[issue16333] Trailing whitespace in json dump when using indent

R. David Murray added the comment: Yes, I think the risk of breaking doctests (and breaking them in a very mysterious way...trailing spaces) is high enough that we shouldn't backport the fix, unfortunately. -- ___ Python tracker

[issue10052] Python/dtoa.c:158: #error "Failed to find an exact-width 32-bit integer type" (FreeBSD 4.11 + gcc 2.95.4)

Changes by Trent Nelson : -- nosy: +trent ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue16333] Trailing whitespace in json dump when using indent

Éric Araujo added the comment: I agree with RDM. -- versions: -Python 2.7, Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-b

[issue10052] Python/dtoa.c:158: #error "Failed to find an exact-width 32-bit integer type" (FreeBSD 4.11 + gcc 2.95.4)

Mark Dickinson added the comment: This is also an issue on the Tru64 / alpha on Snakebite: that platform has inttypes.h but no stdint.h, and inttypes.h has typedefs for uint32_t and friends, but no defines for UINT32_MAX, etc. So the pyport.h check: #if (defined UINT32_MAX || defined uint32_

[issue10052] Python/dtoa.c:158: #error "Failed to find an exact-width 32-bit integer type" (FreeBSD 4.11 + gcc 2.95.4)

Changes by Mark Dickinson : -- assignee: -> mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue10052] Python/dtoa.c:158: #error "Failed to find an exact-width 32-bit integer type" (FreeBSD 4.11 + gcc 2.95.4)

Changes by Mark Dickinson : -- versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16333] Trailing whitespace in json dump when using indent

Serhiy Storchaka added the comment: Please left 2.7, 3.2 and 3.3 for documentation changes (the second patch). -- ___ Python tracker ___ _

[issue16333] Trailing whitespace in json dump when using indent

Changes by Éric Araujo : -- components: +Documentation versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python

[issue15990] solidify argument/parameter terminology

Chris Jerdonek added the comment: > Note that I took this from the pep. The pep could get the same clarification > (unless I made it more confusing than it was). Reading the following, it seems that PEPs aren't generally clarified after becoming Final (as is PEP 362): "In general, Standards t

[issue16572] Bad multi-inheritance support in some libs like threading or multiprocessing

New submission from Thomas Chiroux: when using multi-inheritance and super() in __init__(), super() tries to run each constructor once. For this to work correctly, it is needed to call super() in each constructor, including for Classes directly inherited from object. The sample below does not

[issue9176] module termios doesn't build on HP-UX

Stefan Krah added the comment: This should be fixed now (see #6308). -- nosy: +skrah resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> termios fix for QNX breaks HP-UX ___ Python tracker

[issue15990] solidify argument/parameter terminology

Éric Araujo added the comment: PEP 1 doesn’t reflect current practice then. -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue15990] solidify argument/parameter terminology

Ezio Melotti added the comment: The PEPs don't undergo major changes, but AFAIU typo fixes and minor clarifications/rephrasing are allowed. -- ___ Python tracker ___ ___

[issue16572] Bad multi-inheritance support in some libs like threading or multiprocessing

Serhiy Storchaka added the comment: Can you please provide a diff in unified format? I don't see any super() in Lib/threading.py. -- nosy: +serhiy.storchaka ___ Python tracker _

[issue16572] Bad multi-inheritance support in some libs like threading or multiprocessing

Thomas Chiroux added the comment: updated diff file, unified format -- Added file: http://bugs.python.org/file28151/diff_unified_threading.py_2.7.patch ___ Python tracker ___ ___

[issue16534] -Olimit: unsupported option: warnings and ./configure failures

Stefan Krah added the comment: The issue here is that the BASECFLAGS variable contains the mysterious option -Olimit 1500, which makes the X87_DOUBLE_ROUNDING test fail (i.e. X87_DOUBLE_ROUNDING is set to true when it should be false). When BASECFLAGS is unset, test_float passes. -Olimit giv

[issue16333] Trailing whitespace in json dump when using indent

Roundup Robot added the comment: New changeset 78bad589f205 by Ezio Melotti in branch '2.7': #16333: document a way to get rid of trailing whitespace when indent is used. http://hg.python.org/cpython/rev/78bad589f205 New changeset 2a5b183ac3cd by Ezio Melotti in branch '3.2': #16333: document a

[issue16333] Trailing whitespace in json dump when using indent

Roundup Robot added the comment: New changeset e7919cf9b5e5 by Ezio Melotti in branch 'default': #16333: fix example in docstring. http://hg.python.org/cpython/rev/e7919cf9b5e5 -- ___ Python tracker ___

[issue16333] Trailing whitespace in json dump when using indent

Ezio Melotti added the comment: I committed the patches leaving out the json.tool changes. I will commit those as part of #16476. Thanks Serhiy for the patches! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed

[issue15043] test_gdb is disallowed by default security settings in Fedora 17

Stefan Krah added the comment: The test still seems to fail on Fedora 16: http://buildbot.python.org/all/builders/AMD64%20Fedora%20without%20threads%202.7/builds/906/steps/test/logs/stdio -- nosy: +skrah ___ Python tracker

[issue16534] -Olimit: unsupported option: warnings and ./configure failures

Roundup Robot added the comment: New changeset 5697387b0089 by Stefan Krah in branch '2.7': Issue #16534: On HP-UX ac_cv_olimit_ok=yes is a false positive. http://hg.python.org/cpython/rev/5697387b0089 -- nosy: +python-dev ___ Python tracker

[issue16572] Bad multi-inheritance support in some libs like threading or multiprocessing

Richard Oudkerk added the comment: The patch is liable to break programs which explicitly call base constructors because the constructor will be called more than once. It also assumes that the __init__() method of all base classes should be called with no arguments (other than self). That is

[issue15990] solidify argument/parameter terminology

Chris Jerdonek added the comment: Thanks for the clarification. I will create an issue to clarify that part of PEP 1. It should also say who is allowed to make such changes and whether/from whom approval is necessary, etc. -- ___ Python tracker <

[issue16573] 2to3 should treat enumerate like sorted for zip, map, filter, dict, xrange

New submission from Jonathan Kotta: enumerate() is a "consuming_call", as defined in fixer_util.py, because it takes an iterable (not necessarily a collection). Therefore whenever we have something like enumerate(zip(...)), we don't need to replace it with enumerate(list(zip(...))) in 2to3, b

[issue16476] Trailing spaces in pretty-printed JSON

Changes by Ezio Melotti : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue16534] -Olimit: unsupported option: warnings and ./configure failures

Stefan Krah added the comment: ./configure is fixed, sys.float_repr_style is 'short' now. I agree that it's not worth backporting Py_NAN fixes; I guess we can close this then. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed versions: -Python 3.

[issue16572] Bad multi-inheritance support in some libs like threading or multiprocessing

Thomas Chiroux added the comment: That's right. Lets consider this 'patch' was more for illustrating my example (like: this kind of modification may work) than to add directly into python core module... (which i'm not capable of) But I think the problem remains: do you agree that Classes shou

[issue16476] Trailing spaces in pretty-printed JSON

Roundup Robot added the comment: New changeset fa277ab588de by Ezio Melotti in branch '2.7': #16476: Fix json.tool to avoid including trailing whitespace. http://hg.python.org/cpython/rev/fa277ab588de New changeset 6996a53f13ce by Ezio Melotti in branch '3.2': #16476: Fix json.tool to avoid incl

[issue16476] Trailing spaces in pretty-printed JSON

Ezio Melotti added the comment: I fixed this separately from #16333. In the "default" branch this got fixed by #16333 already. Thanks for the report! -- assignee: -> ezio.melotti components: +Library (Lib) resolution: duplicate -> fixed versions: +Python 3.2, Python 3.3, Python 3.4 ___

[issue16549] regression: -m json.tool module is broken

Roundup Robot added the comment: New changeset 08e5973fdc7e by Ezio Melotti in branch '2.7': #16549: Add tests for json.tools. Initial patch by Berker Peksag and Serhiy Storchaka. http://hg.python.org/cpython/rev/08e5973fdc7e New changeset 44c544809e6c by Ezio Melotti in branch '3.2': #16549:

[issue16549] regression: -m json.tool module is broken

Ezio Melotti added the comment: Fixed, thanks for the patches! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: +Python 2.7 ___ Python tracker

[issue16333] Trailing whitespace in json dump when using indent

Roundup Robot added the comment: New changeset 1e3b01c52aee by Ezio Melotti in branch 'default': #16333: add Misc/NEWS entry for e63ac05ccfa8. http://hg.python.org/cpython/rev/1e3b01c52aee -- ___ Python tracker ___

[issue16476] Trailing spaces in pretty-printed JSON

Changes by Ezio Melotti : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue16574] clarify policy on updates to final peps

New submission from Chris Jerdonek: This issue is to clarify the policy in PEP 1 regarding non-substantive changes to PEPs in the Final state (minor clarifications, rephrasings, etc). Currently, PEP 1 says, "In general, Standards track PEPs are no longer modified after they have reached the Fi

[issue15990] solidify argument/parameter terminology

Chris Jerdonek added the comment: I just created issue 16574 to clarify PEP 1 with regard to the above. -- ___ Python tracker ___ ___

[issue16333] Trailing whitespace in json dump when using indent

Éric Araujo added the comment: Ezio, I noticed in the check-in mail that you added the note before the description of the separators argument (specifically, the descrition of what it does when it’s a tuple). Maybe it would flow best to move the note after that part? Also, I don’t think this

[issue16333] Trailing whitespace in json dump when using indent

Ezio Melotti added the comment: > I noticed in the check-in mail that you added the note before > the description of the separators argument The note is just after the description of the indent argument, because it's relevant only when a indent value is specified. > Regular text would have loo

[issue16572] Bad multi-inheritance support in some libs like threading or multiprocessing

Richard Oudkerk added the comment: > But I think the problem remains: do you agree that Classes should include > a super() call in their __init__ ? No, I don't. I think super() is an attractive nuisance which is difficult to use correctly in an __init__() method, except in the trivial case wh

[issue16574] clarify policy on updates to final peps

Martin v. Löwis added the comment: I don't think this needs clarification. The status quo is fine. -- nosy: +loewis ___ Python tracker ___ ___

[issue16574] clarify policy on updates to final peps

Chris Jerdonek added the comment: Are you saying that PEP 1 is correct and that Final PEPs should not be modified, or that the PEP isn't correct but that it shouldn't be modified? If the latter, for someone new it's not clear whether minor clarifications are permitted and if so, how to go abou

[issue16574] clarify policy on updates to final peps

Éric Araujo added the comment: I think Brett edited PEP 302 a decade after its acceptance. -- nosy: +brett.cannon ___ Python tracker ___ _

  1   2   >