[issue45328] http.client.HTTPConnection doesn't work without TCP_NODELAY
Change by Rodrigo : -- nosy: +rtobar nosy_count: 1.0 -> 2.0 pull_requests: +27014 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28646 ___ Python tracker <https://bugs.python.org/issue45328> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45386] xmlrpc.client unimportable due to strfmt ValueError
Change by Rodrigo : -- keywords: +patch nosy: +rtobar nosy_count: 1.0 -> 2.0 pull_requests: +27105 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28765 ___ Python tracker <https://bugs.python.org/issue45386> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45790] Inaccurate phrasing in extending/newtypes_tutorial
Change by Rodrigo : -- keywords: +patch nosy: +rtobar nosy_count: 2.0 -> 3.0 pull_requests: +27779 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29529 ___ Python tracker <https://bugs.python.org/issue45790> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12023] non causal behavior
New submission from Rodrigo Ventura : Consider these two functions: --- def nok(): a = None def f(): if a: a = 1 f() def ok(): a = None def f(): if a: b = 1 f() --- Function ok() executes fine, but function nok() trigger an exception: Traceback (most recent call last): File "pb.py", line 20, in nok() File "pb.py", line 7, in nok f() File "pb.py", line 5, in f if a: UnboundLocalError: local variable 'a' referenced before assignment There is no reason for this to happen Regards, Rodrigo Ventura -- messages: 135380 nosy: Rodrigo.Ventura priority: normal severity: normal status: open title: non causal behavior type: behavior versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue12023> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12023] non causal behavior
Rodrigo Ventura added the comment: Ezio, thank you for the explanation. Is it possible to access variable a in nok's scope from function f without using the global keyword in f? (so that variable a remains local to nok, rather than global to python) Rodrigo -- ___ Python tracker <http://bugs.python.org/issue12023> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue45790] Inaccurate phrasing in extending/newtypes_tutorial
New submission from Rodrigo Tobar : In `extending/newtypes_tutorial.rst` the following phrase appears: "[...], containing a pointer to a type object and a reference count (these can be accessed using the macros :c:macro:`Py_REFCNT` and c:macro:`Py_TYPE` respectively)." I believe it should read "using the macros :c:macro:`Py_TYPE` and c:macro:`Py_REFCNT` respectively" to follow the same order in which the fields are described. I'll put forward a patch. It seems this phrase goes way back a few python versions, but I'm tagging 3.11 here only. -- assignee: docs@python components: Documentation messages: 406185 nosy: docs@python, rtobar2 priority: normal severity: normal status: open title: Inaccurate phrasing in extending/newtypes_tutorial versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue45790> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20392] Inconsistency with uppercase file extensions in MimeTypes.guess_type
New submission from Rodrigo Parra:
The functions looks up for the file extension in three maps: types_map,
suffix_map and encodings_map.
Lookup in types_map is case insensitive (by calling lower() first).
Lookup in both suffix_map and encodings_map is case sensitive.
These can lead to some seemingly counterintuitive results, like:
a)
guess_type("foo.tar") == ("application/x-tar", None)
guess_type("foo.TAR") == ("application/x-tar", None)
b)
guess_type("foo.tgz") == ("application/x-tar", "gzip")
guess_type("foo.TGZ") == (None, None)
c)
guess_type("foo.tar.gz") == ("application/x-tar", "gzip")
guess_type("foo.TAR.GZ") == (None, None)
Lookup should be case insensitive at least for the suffix_map, in which case
(b) would be solved. The submitted patch implements this change.
As for the encodings_map, I am not so sure, in particular because of the tar.Z
extension. I found that the compress command expects the uppercase 'Z'. If
someone is relying in the results of guess_type to call compress, errors could
occur.
--
components: Library (Lib)
files: case_guess_type.patch
keywords: patch
messages: 209218
nosy: Rodrigo.Parra, tim.golden
priority: normal
severity: normal
status: open
title: Inconsistency with uppercase file extensions in MimeTypes.guess_type
type: behavior
versions: Python 3.4
Added file: http://bugs.python.org/file33703/case_guess_type.patch
___
Python tracker
<http://bugs.python.org/issue20392>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25333] .1 + .2 == .3 should be True
New submission from Rodrigo Souto: print(.1 + .2 == .3) should be True like the others >>> print(.1 + .2 == .3) False >>> print(.1 + .3 == .4) True >>> print(.1 + .4 == .5) True >>> print(.1 + .1 == .2) True -- messages: 252470 nosy: Rodrigo Souto priority: normal severity: normal status: open title: .1 + .2 == .3 should be True type: behavior versions: Python 3.4 ___ Python tracker <http://bugs.python.org/issue25333> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9891] Minor doc typo at datamodel.rst: "list" -> "alist"
New submission from Rodrigo Bernardo Pimentel : The "Built-in methods" item of the "The standard type hierarchy" section of Doc/reference/datamodels.rst uses a list instance called "alist" as an example, and it says "__self__ is set to the object denoted by *list*." It should read "the object denoted by *alist*" This affects all releases, so I've marked them all. But I suppose we don't care about 2.5 anymore. All the others are listed on docs.python.org (or are "trunk"), and I think should be fixed. It's a trivial fix, and a single patch works 2.x and another for 3.x. -- assignee: d...@python components: Documentation files: alist_doc-2.x.patch keywords: patch messages: 116757 nosy: d...@python, rbp priority: normal severity: normal status: open title: Minor doc typo at datamodel.rst: "list" -> "alist" versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file18914/alist_doc-2.x.patch ___ Python tracker <http://bugs.python.org/issue9891> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9891] Minor doc typo at datamodel.rst: "list" -> "alist"
Changes by Rodrigo Bernardo Pimentel : Added file: http://bugs.python.org/file18915/alist_doc-3.x.patch ___ Python tracker <http://bugs.python.org/issue9891> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10047] python-2.6.6 coredump running newspipe
Rodrigo Bernardo Pimentel added the comment: Does this always happen with a particular feed? Could you provide us with a configuration that reproduces the problem? Also, as R. David Murray asked, does this happen with 2.7? -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10047> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10017] pprint.pprint raises TypeError on dictionaries with user-defined types as keys
Rodrigo Bernardo Pimentel added the comment: FWIW, the problem still occurs on the most recent release31-maint checkout (as of r85323), and does not happen on py3k (3.2a2). -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10017> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10017] pprint.pprint raises TypeError on dictionaries with user-defined types as keys
Rodrigo Bernardo Pimentel added the comment:
If I'm understanding this correctly, this fails on 3.1 and not (although,
actually, it does) on py3k/3.2 because:
* pprint._safe_key.__lt__ checks "rv = self.obj.__lt__(other.obj)" and falls
back to id comparison if rv is NotImplemented
* If the object passed to _safe_key is a class, self.obj.__lt__ will expect
*self* as well as the other object. Therefore the verification above fails with
"TypeError: expected 1 arguments, got 0". You can see that pprint works with an
instance:
>>> pprint.pprint({A(): 1, 1: 2})
{<__main__.A object at 0x8594d4c>: 1, 1: 2}
* Finally, this works on py3k *for your example* because, for some reason, on
py3k the comparison is being based on the 1 key. That is, the comparison on
_safe_key.__lt__ happens to be 1.__lt__(A), instead of A.__lt__(1). Perhaps
hashing changed after the 3.1 release?
Anyway, py3k still fails when you force the comparison to happen on the class:
>>> class B(object): pass
...
>>> pprint.pprint({A: 1, B: 2})
Traceback (most recent call last):
File "", line 1, in
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 55, in pprint
printer.pprint(object)
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 132, in pprint
self._format(object, self._stream, 0, 0, {}, 0)
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 155, in _format
rep = self._repr(object, context, level - 1)
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 245, in _repr
self._depth, level)
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 257, in format
return _safe_repr(object, context, maxlevels, level)
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 299, in _safe_repr
items = sorted(object.items(), key=_safe_tuple)
File "/home/rbp/python/dev/py3k/Lib/pprint.py", line 89, in __lt__
rv = self.obj.__lt__(other.obj)
TypeError: expected 1 arguments, got 0
>>>
So, basically, the fix on issue 3976 does't (always) work when there are
classes as dict keys. I think switching from
rv = self.obj.__lt__(other.obj)
if rv is NotImplemented:
to something like
try:
rv = self.obj < other.obj
except TypeError:
rv = (str(type(self.obj)), id(self.obj)) < \
(str(type(other.obj)), id(other.obj))
solves this. Or we can check first whether self.obj is a 'type', but I think it
gets convoluted.
If anyone can confirm that that's the way to go, I can produce one (though it's
a trivial one). Raymond?
--
___
Python tracker
<http://bugs.python.org/issue10017>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3976] pprint._safe_repr is not general enough in one instance
Rodrigo Bernardo Pimentel added the comment: Armin: this has the problem that, if the object you're trying to compare is a class, self.obj.__lt__ expects a different number of parameters (i.e., it expects the instance). See issue 10017 . Testing with "<" works. -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue3976> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5131] pprint doesn't know how to print a defaultdict
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue5131> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9305] Don't use east/west of UTC in date/time documentation
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue9305> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9305] Don't use east/west of UTC in date/time documentation
Rodrigo Bernardo Pimentel added the comment: 1. Done (it's on the patch I'm uploading). Sorry. 3. Ok, we've rewritten that sentence. As Henrique mentioned, we're working on a larger patch to make datetime documentation clearer, and we can include a definition of "standard time" there. 2. I assume you're talking about sentences like "(negative for west of UTC)". We removed that wording because it inevitably leads to associating UTC with a geographical reference. Even if we disregard that, it's not true that "utcoffset is negative west of UTC", since it will we zero for for UTC-1 (and even +1 for places physically "west of UTC" but at timezone UTC+0) when DST is effective. It seems that any sentence we add to that effect will be simply restating the definitions of UTC, timezones and DST (and their mathematical relationships). That is, "utcoffset will be negative when dt.tzinfo + dst() is negative". Perhaps we could include a more detailed discusion about the sign of utcoffset() on the larger doc patch I've mentioned? Or do you have any suggestions? -- Added file: http://bugs.python.org/file19709/datetime_doc_remove_east_west_2.diff ___ Python tracker <http://bugs.python.org/issue9305> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10220] Make generator state easier to introspect
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10220> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10351] Add autocompletion for keys in dictionaries
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10351> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10427] 24:00 Hour in DateTime
Rodrigo Bernardo Pimentel added the comment: I was writing tests for this issue, when something struck me: ok, datetime(year, month, day, 24) is valid. But is datetime(year, month, day, 24, 1) valid? Or datetime(year, month, day, 24, 0, 0, 1)? I would say those aren't valid, although that makes checking forvalid hour values slightly weird (as in not straightforward): 24 is valid if minutes, seconds and microseconds are all 0, but invalid otherwise. What do you think? -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10427> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9063] TZ examples in datetime.rst are incorrect
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue9063> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3417] make the fix_dict fixer smarter
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: I haven't managed to successfully complete the summer of code, due to some personal problems, but I'm still working on 2to3 and on confidence ranking for it. There's a bzr branch with its current implementation at http://isnomore.net/bzr/2to3 . I did an initial implementation of confidence penalties on fix_dict for special contexts. I'm still working on it (and on confidence ranking in general), but please take a look and let me know what you think. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3417> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3417] make the fix_dict fixer smarter
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: (I've just realized it's not working properly for fix_dict; I'm fixing it and will drop a note here when it is) ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3417> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7583] Improve explanation of tab expansion in doctests
Rodrigo Bernardo Pimentel added the comment: I've just been bitten by this, and I agree the language in the docs is very inappropriate (made me angry for a minute :)). One suggestion: "While not everyone might believe tabs should mean that, doctests are primarily aimed at documentation, and, since it's very hard to get tabs to look consistent, keeping hard tabs would be potentially confusing. If you absolutely need to test for the presence of tabs at the output, you can capture it and use string comparison, or write your own DocTestParser class." -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue7583> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2532] file that breaks 2to3 (despite being correct python)
Changes by Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]>: -- nosy: +rbp __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2532> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2805] 2to3 doesn't correct divisions
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: +1 for going ahead and writing a fixer. -- nosy: +rbp __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2805> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2803] heapq.heappush called with too few arguments in sched.py
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: +1 on the patch. IIRC, there won't be any more bugfix releases for 2.5.x, but, just in case: the patch doesn't work on 2.5 (though the issue lists it as an affected version - and it is!), so I'm uploading a patch for it (svn tag r252). I started writing a test for it, but it's such an obvious and trivial patch that I think it's unnecessary. -- nosy: +rbp Added file: http://bugs.python.org/file10244/sched.py.patch-r252 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2803> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2798] Crash on non-Windows if Python runs from a non-ASCII directory
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: The patch works for me, and I agree the test_xmlrpc is an xmlrpc issue. Perhaps unrelated to this issue, but I think it makes this whole unicode getargs situation fragile: I could not understand why the 'z' case (on the switch where this patch applies, starting on line 879 on the patched file) does a PyString_Check(arg) and a PyUnicode_Check(arg), while the corresponding section on case 's' (line 813) only does PyUnicode_Check(arg). Is this really an inconsistency? Maybe this should go into an issue to cleanup this switch, according to the comment at its beginning: /* XXX WH! 's', 'y', 'z', 'u', 'Z', 'e', 'w', 't' codes all need to be cleaned up! */ -- nosy: +rbp __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2798> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2723] Truncate __len__() at sys.maxsize
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment:
I think returning sys.{maxint,maxsize} in this case is a plain lie.
That's not practicality, that's giving back false information.
Barring drastic language changes (such as having objects representing
"infinity" or "greater than" - which, of course, won't happen), I think
the current behaviour of raising an exception is the correct one. But,
although I think OverflowError is good enough, the current exception
message is a bit cryptic, especially for anyone who doesn't know C:
"""OverflowError: Python int too large to convert to C ssize_t"""
I've attached a simple patch (modified from Alexander's) to raise:
"""OverflowError: Length too large"""
(I thought about "Object too large", but our problem is actually that
the *length* itself is too large)
--
nosy: +rbp
Added file: http://bugs.python.org/file10270/len_message.patch
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue2723>
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1713041] fix for 1712742: corrects pprint's handling of 'depth'
Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: It seems that somewhere along the road between revision 55144 (where the first patch was generated) and current trunk (revision 63129), PrettyPrinter._format has stopped handling depth! I've attached a patch that fixes this, along with the fixes this issue originally proposed (including the tests and documentation updates). With this patch, unit tests and the documentation's doctests all pass. BTW, doctesting Doc/library/pprint.rst with optionflags=doctest.ELLIPSIS erroneously interprets pprint's '...' (indicating depth exceeded) as doctest ellipses! Testing without ELLIPSIS gives an error on output with something like "[]", testing with it hides errors. Ugh! -- nosy: +rbp -errebepe Added file: http://bugs.python.org/file10302/pprint-r63129.patch _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1713041> _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1293741] doctest runner cannot handle non-ascii characters
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue1293741> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20208] Clarify some things in porting HOWTO
Rodrigo Bernardo Pimentel added the comment: I've created a patch that addresses the first criticism (explaining unicode_literals), as well as the first mention of print_function. It also addresses a small concern regarding "map", which I've mentioned in my G+ comment: """ Also, a friend was confused by http://docs.python.org/dev/howto/pyporting.html#update-map-for-imbalanced-input-sequences , until I understood that he didn't know map can take several sequences. I assume a lot of less experienced Python programmers only use map with a single sequence, and might be confused as well. A sentence mentioning that might help. """ I see that the current version of the doc on hg already addresses the 2to3 mention. -- keywords: +patch nosy: +rbp Added file: http://bugs.python.org/file33408/pyporting.patch ___ Python tracker <http://bugs.python.org/issue20208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20208] Clarify some things in porting HOWTO
Rodrigo Bernardo Pimentel added the comment: BTW, there remains another concern I mentioned on G+: """ A note on formatting: I found some of 4th- and 5th-level headings too subtle. For instance, http://docs.python.org/dev/howto/pyporting.html#from-future-import-absolute-import got me thinking for a second if it was part of the previous paragraph or a new heading. Maybe underlining, or a bullet-like marker, or some indentation could help there. """ But I don't know enough of the formatting standards, so I haven't addressed this in the patch. -- ___ Python tracker <http://bugs.python.org/issue20208> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6582] test_telnetlib doesn't test Telnet.write
Rodrigo Steinmuller Wanderley added the comment: Did only minor modifications to TelnetSocketSendall class. Please review the following patch. -- keywords: +patch nosy: +rwanderley Added file: http://bugs.python.org/file14668/write_test.patch ___ Python tracker <http://bugs.python.org/issue6582> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2637] urllib.quote() escapes characters unnecessarily and contrary to docs
Rodrigo Steinmuller Wanderley added the comment: > Unreserved characters can be escaped without changing the semantics > of the URI, but this should not be done unless the URI is being used > in a context that does not allow the unescaped character to appear. How can we identify "a context that does not allow the unescaped character to appear"? -- nosy: +rwanderley ___ Python tracker <http://bugs.python.org/issue2637> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6582] test_telnetlib doesn't test Telnet.write
Changes by Rodrigo Steinmuller Wanderley : Removed file: http://bugs.python.org/file14668/write_test.patch ___ Python tracker <http://bugs.python.org/issue6582> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6582] test_telnetlib doesn't test Telnet.write
Changes by Rodrigo Steinmuller Wanderley : Added file: http://bugs.python.org/file14686/telnetlib_writetest.diff ___ Python tracker <http://bugs.python.org/issue6582> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6582] test_telnetlib doesn't test Telnet.write
Rodrigo Steinmuller Wanderley added the comment: On Thu, 03 Sep 2009 20:38:49 + Jack Diederich wrote: > > Jack Diederich added the comment: > > applied in r74638 > and I've added you to Misc/ACKS > Thanks again for the patch! No problem, Anything I can do to improve telnetlib further? I'm currently with plenty of time available and would appreciate the opportunity to learn more Python. Rodrigo > -- > resolution: -> accepted > status: open -> closed > > ___ > Python tracker > <http://bugs.python.org/issue6582> > ___ -- ___ Python tracker <http://bugs.python.org/issue6582> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6583] 2to3 fails to fix test.test_support
Rodrigo Bernardo Pimentel added the comment: Pascal is correct, trunk Doc/library/test.rst still says: "The 2to3 tool will automatically adapt imports when converting your sources to 3.0." Perhaps this should simply be changed to "The 2to3 tool will not automatically convert this, so make sure you do, manually, if you port your code to Python 3." Please let me know if you require a patch for this (but I think it's trivial enough), or if you think this should raise a -3 warning. -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue6583> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2516] Instance methods are misreporting the number of arguments
Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue2516> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34087] Segmentation fault on visit_decref
New submission from Rodrigo Pinheiro Marques de Araújo :
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x656d6f6e2236)
frame #0: 0x00010014c819 python3`visit_decref(op=0x656d6f6e222e,
data=0x) at gcmodule.c:271 [opt]
268 visit_decref(PyObject *op, void *data)
269 {
270 assert(op != NULL);
-> 271 if (PyObject_IS_GC(op)) {
272 PyGC_Head *gc = AS_GC(op);
273 /* We're only interested in gc_refs for objects in the
274 * generation being collected, which can be recognized
Target 0: (python3) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x656d6f6e2236)
* frame #0: 0x00010014c819 python3`visit_decref(op=0x656d6f6e222e,
data=0x) at gcmodule.c:271 [opt]
frame #1: 0x00010003af38 python3`list_traverse(o=0x000116971608,
visit=(python3`visit_decref at gcmodule.c:269), arg=0x) at
listobject.c:2574 [opt]
frame #2: 0x00010014aca3 python3`collect [inlined] subtract_refs at
gcmodule.c:296 [opt]
frame #3: 0x00010014ac72 python3`collect(generation=2,
n_collected=0x7ffeefbff0a8, n_uncollectable=0x7ffeefbff0b0, nofail=0)
at gcmodule.c:853 [opt]
frame #4: 0x00010014a8f5 python3`PyGC_Collect [inlined]
collect_with_callback(generation=2) at gcmodule.c:1028 [opt]
frame #5: 0x00010014a8cc python3`PyGC_Collect at gcmodule.c:1573 [opt]
frame #6: 0x00010011f7a8 python3`Py_FinalizeEx at pylifecycle.c:1087
[opt]
frame #7: 0x000100149605 python3`pymain_main(pymain=) at
main.c:2664 [opt]
frame #8: 0x00010014a280 python3`_Py_UnixMain(argc=5,
argv=0x7ffeefbff4b8) at main.c:2697 [opt]
frame #9: 0x7fff5869a015 libdyld.dylib`start + 1
frame #10: 0x7fff5869a015 libdyld.dylib`start + 1
--
components: Interpreter Core
messages: 321394
nosy: fenrrir
priority: normal
severity: normal
status: open
title: Segmentation fault on visit_decref
type: crash
versions: Python 3.7
___
Python tracker
<https://bugs.python.org/issue34087>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34087] Segmentation fault on visit_decref
Rodrigo Pinheiro Marques de Araújo added the comment: Sorry for that. I’m not able to make a little example to reproduce this bug. It’s happens during Django tests on a very large code base. A interest thing is that not happens with “-X dev” parameters. Please, any suggestions how I can get more details about this bug? -- ___ Python tracker <https://bugs.python.org/issue34087> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34087] Segmentation fault on visit_decref
Rodrigo Pinheiro Marques de Araújo added the comment: Running with `-X faulthandler` Fatal Python error: Segmentation fault Current thread 0x7fff89cf2380 (most recent call first): File "/Users/rodrigo/root/lib/python3.7/site-packages/django/urls/resolvers.py", line 526 in resolve File "/Users/rodrigo/root/lib/python3.7/site-packages/django/urls/resolvers.py", line 500 in resolve File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/base.py", line 113 in _get_response File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/reversion/views.py", line 43 in do_revision_view File "/Users/rodrigo/root/lib/python3.7/site-packages/reversion/middleware.py", line 51 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/utils/deprecation.py", line 95 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/exception.py", line 35 in inner File "/Users/rodrigo/root/lib/python3.7/site-packages/django/core/handlers/base.py", line 81 in get_response File "/Users/rodrigo/root/lib/python3.7/site-packages/django/test/client.py", line 138 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/test/client.py", line 467 in request File "/Users/rodrigo/root/lib/python3.7/site-packages/django/test/client.py", line 404 in generic File "/Users/rodrigo/root/lib/python3.7/site-packages/django/test/client.py", line 332 in get File "/Users/rodrigo/root/lib/python3.7/site-packages/django/test/client.py", line 517 in get File "/Users/rodrigo/root/lib/python3.7/unittest/case.py", line 615 in run File "/Users/rodrigo/root/lib/python3.7/unittest/case.py", line 663 in __call__ File "/Users/rodrigo/root/lib/python3.7/site-packages/django/test/testcases.py", line 206 in __call__ File "/Users/rodrigo/root/lib/python3.7/unittest/suite.py", line 122 in run File "/Users/rodrigo/root/lib/python3.7/unittes
[issue34087] django: segmentation fault on garbage collection in visit_decref()
Rodrigo Pinheiro Marques de Araújo added the comment: Unfortunately with 'PYTHONMALLOC=debug' the segmentation fault do not happen. -- ___ Python tracker <https://bugs.python.org/issue34087> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34087] django: segmentation fault on garbage collection in visit_decref()
Rodrigo Pinheiro Marques de Araújo added the comment: Extensions: ./_cffi_backend.cpython-37m-darwin.so ./_mssql.cpython-37m-darwin.so ./_yaml.cpython-37m-darwin.so ./Crypto/Cipher/_AES.cpython-37m-darwin.so ./Crypto/Cipher/_ARC2.cpython-37m-darwin.so ./Crypto/Cipher/_ARC4.cpython-37m-darwin.so ./Crypto/Cipher/_Blowfish.cpython-37m-darwin.so ./Crypto/Cipher/_CAST.cpython-37m-darwin.so ./Crypto/Cipher/_DES.cpython-37m-darwin.so ./Crypto/Cipher/_DES3.cpython-37m-darwin.so ./Crypto/Cipher/_XOR.cpython-37m-darwin.so ./Crypto/Hash/_MD2.cpython-37m-darwin.so ./Crypto/Hash/_MD4.cpython-37m-darwin.so ./Crypto/Hash/_RIPEMD160.cpython-37m-darwin.so ./Crypto/Hash/_SHA224.cpython-37m-darwin.so ./Crypto/Hash/_SHA256.cpython-37m-darwin.so ./Crypto/Hash/_SHA384.cpython-37m-darwin.so ./Crypto/Hash/_SHA512.cpython-37m-darwin.so ./Crypto/PublicKey/_fastmath.cpython-37m-darwin.so ./Crypto/Util/_counter.cpython-37m-darwin.so ./Crypto/Util/strxor.cpython-37m-darwin.so ./cryptography/hazmat/bindings/_constant_time.abi3.so ./cryptography/hazmat/bindings/_openssl.abi3.so ./cryptography/hazmat/bindings/_padding.abi3.so ./Cython/Compiler/Code.cpython-37m-darwin.so ./Cython/Compiler/FlowControl.cpython-37m-darwin.so ./Cython/Compiler/FusedNode.cpython-37m-darwin.so ./Cython/Compiler/Lexicon.cpython-37m-darwin.so ./Cython/Compiler/Parsing.cpython-37m-darwin.so ./Cython/Compiler/Pythran.cpython-37m-darwin.so ./Cython/Compiler/Scanning.cpython-37m-darwin.so ./Cython/Compiler/Visitor.cpython-37m-darwin.so ./Cython/Plex/Actions.cpython-37m-darwin.so ./Cython/Plex/Scanners.cpython-37m-darwin.so ./Cython/Runtime/refnanny.cpython-37m-darwin.so ./Cython/StringIOTree.cpython-37m-darwin.so ./Cython/Tempita/_tempita.cpython-37m-darwin.so ./lazy_object_proxy/cext.cpython-37m-darwin.so ./lxml/_elementpath.cpython-37m-darwin.so ./lxml/builder.cpython-37m-darwin.so ./lxml/etree.cpython-37m-darwin.so ./lxml/html/clean.cpython-37m-darwin.so ./lxml/html/diff.cpython-37m-darwin.so ./lxml/objectify.cpython-37m-darwin.so ./markupsafe/_speedups.cpython-37m-darwin.so ./PIL/_imaging.cpython-37m-darwin.so ./PIL/_imagingcms.cpython-37m-darwin.so ./PIL/_imagingmath.cpython-37m-darwin.so ./PIL/_imagingmorph.cpython-37m-darwin.so ./PIL/_imagingtk.cpython-37m-darwin.so ./psycopg2/_psycopg.cpython-37m-darwin.so ./pymssql.cpython-37m-darwin.so ./reportlab/graphics/_renderPM.cpython-37m-darwin.so ./reportlab/lib/_rl_accel.cpython-37m-darwin.so ./setproctitle.cpython-37m-darwin.so ./simplejson/_speedups.cpython-37m-darwin.so ./wrapt/_wrappers.cpython-37m-darwin.so requirements.txt alabaster==0.7.11 amqp==2.2.2 appnope==0.1.0 arrow==0.12.0 asn1crypto==0.24.0 astroid==1.6.5 Babel==2.6.0 beautifulsoup4==4.6.0 billiard==3.5.0.3 boto3==1.7.24 botocore==1.10.24 celery==4.1.0 certifi==2018.4.16 cffi==1.11.2 chardet==3.0.4 colorama==0.3.9 colorful==0.4.0 configparser==3.5.0 coreapi==2.3.3 coreschema==0.0.4 cryptography==2.2.2 cssselect==1.0.3 Cython==0.28.2 decorator==4.3.0 dj-database-url==0.4.2 Django==2.0.6 django-braces==1.12.0 django-celery-beat==1.1.1 django-celery-results==1.0.1 django-ckeditor==5.2.1 django-colorful==1.2 django-crispy-forms==1.6.1 django-extensions==1.9.8 django-extra-views==0.9.0 django-filter==1.0.4 django-filters==0.2.1 django-formset-js==0.5.0 django-formtools==2.1 django-fsm==2.6.0 django-jquery-js==3.1.1 django-js-asset==1.1.0 django-localflavor==1.6.2 django-model-utils==3.1.1 django-mptt==0.9.0 django-pagination==1.0.10 django-querysetsequence==0.8 django-recaptcha2==1.0.3 django-rest-swagger==2.1.2 django-reversion==2.0.13 django-reversion-compare==0.8.4 django-storages==1.6.6 django-tables2==1.17.1 django-tables2-reports==0.1.3 django-taggit==0.22.1 django-wkhtmltopdf==3.1.0 djangorestframework==3.7.3 djangorestframework-filters==0.10.2 djangorestframework-jwt==1.11.0 docutils==0.14 feedparser==5.2.1 google-api-python-client==1.6.4 gunicorn==19.7.1 html5lib==1.0.1 httplib2==0.10.3 idna==2.6 imagesize==0.7.1 ipaddress==1.0.19 ipdb==0.10.3 ipython==6.2.1 ipython-genutils==0.2.0 isort==4.2.15 itypes==1.1.0 jedi==0.12.1 Jinja2==2.10 jmespath==0.9.3 kombu==4.2.1 lazy-object-proxy==1.3.1 ldap3==2.4 lxml==4.1.1 MarkupSafe==1.0 mccabe==0.6.1 MechanicalSoup==0.10.0 minio==4.0.0 model-mommy==1.5.0 oauth2client==4.1.2 olefile==0.45.1 openapi-codec==1.3.2 parso==0.3.1 pathlib2==2.3.0 pbr==3.1.1 pdfrw==0.4 pexpect==4.3.1 pickleshare==0.7.4 Pillow==4.3.0 prompt-toolkit==1.0.15 psycopg2==2.7.3.2 ptyprocess==0.5.2 pyasn1==0.4.2 pyasn1-modules==0.2.1 pycparser==2.18 pycpfcnpj==1.2 pycrypto==2.6.1 Pygments==2.2.0 PyJWT==1.6.4 pylint==1.8.1 pyOpenSSL==17.5.0 PyPDF2==1.26.0 pyquery==1.3.0 python-dateutil==2.6.1 python-logstash==0.4.6 python-magic==0.4.15 python-memcached==1.58 pytz==2018.4 PyYAML==3.13 qrcode==5.3 raven==6.4.0 reportlab==3.4.0 requests==2.18.4 rsa==3.4.2 s3transfer==0.1.13 setproctitle==1.1.10 simplegeneric==0.8.1 simplejson==3.13.2 six==1.11.0 snowballstemmer==1.2.1 Sphinx==1.6.5 sphinxcontrib-websupport==1.1.0 suds-py3==1.3.3.0
[issue34087] django: segmentation fault on garbage collection in visit_decref()
Rodrigo Pinheiro Marques de Araújo added the comment: I did remove PyYAML, lxml and Pillow here but segfault still happen -- ___ Python tracker <https://bugs.python.org/issue34087> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34087] django: segmentation fault on random places
Rodrigo Pinheiro Marques de Araújo added the comment: I can reproduce the segmentation fault using 'testproj.tar.gz' with homebrew and compiled from source. MacOS X High Sierra 10.13.5 (17F77). -- ___ Python tracker <https://bugs.python.org/issue34087> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
