Changes by Luiz Poleto :
--
nosy: +luiz.poleto
___
Python tracker
<http://bugs.python.org/issue5996>
___
___
Python-bugs-list mailing list
Unsubscribe:
Luiz Poleto added the comment:
binascii.Error is used throughout the module for most of the validations, with
only a few of them using TypeError/ValueError. I guess it would make more sense
to update these to raise binascii.Error (unless they were left on purpose) to
make it consistent with
Luiz Poleto added the comment:
This seems to be related to issues #5996 and #26306.
--
nosy: +luiz.poleto
___
Python tracker
<http://bugs.python.org/issue24
Luiz Poleto added the comment:
Same as reported on issue #5996. Apparently this happens not only with tuple
but with any builtin type.
There is a patch on that issue but there hasn't been any activity since 2011.
--
nosy: +luiz.poleto
___
P
Luiz Poleto added the comment:
The change to os.rst is already committed so I modified the patch to remove it
and keep only the change to os.py, which looks good and ready to be committed.
--
Added file: http://bugs.python.org/file42635/issue25461.patch
Luiz Poleto added the comment:
As for urlparse_empty_bad_arg_disallow.patch, I didn't go too deep into testing
it but I found that calling urlparse with different non-str args are producing
different results:
urlparse({})
TypeError: unhashable type: 'slice'
urlparse([])
Attrib
Luiz Poleto added the comment:
I am seeing some results when running urlparse with patch
urlparse_empty_bad_arg_deprecation2.patch applied:
>>> urllib.parse.urlparse({})
__main__:1: DeprecationWarning: Use of {} is deprecated
__main__:1: DeprecationWarning: Use of '&
Luiz Poleto added the comment:
As discussed on the Mentors list, the attached patch (issue22234_37.patch)
changes the urlparse function to handle non-str and non-bytes arguments and
adds a new test case for it.
--
Added file: http://bugs.python.org/file42592/issue22234_37.patch
Luiz Poleto added the comment:
As discussed on the Mentors list, the attached patch (issue22234_36.patch)
includes the deprecation warning (and related test) on the urlparse function.
--
keywords: +patch
versions: +Python 3.6 -Python 3.4
Added file: http://bugs.python.org/file42591
Changes by Luiz Poleto :
--
nosy: +luiz.poleto
___
Python tracker
<http://bugs.python.org/issue22234>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Luiz Poleto :
--
nosy: +luiz.poleto
___
Python tracker
<http://bugs.python.org/issue26041>
___
___
Python-bugs-list mailing list
Unsubscribe:
Luiz Poleto added the comment:
The Doc/library/os.rst bit in the current patch fails to apply in all versions
specified in this bug report (it seems that it was generated before the commit
that included an earlier version of it).
--
nosy: +luiz.poleto
Luiz Poleto added the comment:
Based on the example provided by the OP, it appears that he would expect
the output to be:
{'family': ['citrus'], 'fruits': ['lemon;lime']}
Since the W3C recommendation for the application/x-www-form-urlencoded type
specify
Luiz Poleto added the comment:
The attached patch fixes 2 of the main issues reported:
- Missing header values
- Missing newline at the end of the header line
I thought about the suggestion to include the response headers with the reply
but considering that they are two different elements in
Changes by Luiz Poleto :
--
nosy: +luiz.poleto
___
Python tracker
<http://bugs.python.org/issue17233>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Luiz Poleto:
urllib.parse has two methods, parse_qs and parse_qsl to parse a query string
and return its parameters/values as a dictionary or a list, respectively.
However, the unit tests only tests parse_qsl, which is also incomplete since
both parse_qs and parse_qsl
Luiz Poleto added the comment:
If this bug is to be moved forward, we should consider this:
The RFC 3986 defines that a query can have any of these characters:
/?:@-._~!$&'()*+,;= ALPHA DIGIT %HH (encoded octet)
But does not define how the data should be interpreted, leaving th
Luiz Poleto added the comment:
Nice! Thanks!
On Thu, Apr 14, 2016, 5:16 AM Berker Peksag wrote:
>
> Berker Peksag added the comment:
>
> Committed in 0ed2497e5aa4. Thanks for the patch, Luiz.
>
> --
> components: +Devguide -Documentation
> nosy: +berker.peksag
Luiz Poleto added the comment:
The attached patch contains the instructions on how to use DNF to install the
system headers.
--
keywords: +patch
Added file: http://bugs.python.org/file42457/issue26749.patch
___
Python tracker
<h
New submission from Luiz Poleto:
Starting with Fedora 22, yum is no longer the default packaging tool, being
replaced by the new DNF (Dandified Yum).
Section 1.1.3.1 of the devguide, Build dependencies, has instructions to
install system headers using popular Linux distributions, including
Changes by Luiz Poleto :
--
keywords: +patch
Added file: http://bugs.python.org/file42440/issue26699.patch
___
Python tracker
<http://bugs.python.org/issue26
Changes by Luiz Poleto :
Added file: http://bugs.python.org/file34995/issue_19771.patch.v2
___
Python tracker
<http://bugs.python.org/issue19771>
___
___
Python-bug
Luiz Poleto added the comment:
As suggested by Nick, the fix is done be verifying the name attribute of the
raised ImportError exception; the exception is then re-raised with the
appropriate description.
--
Added file: http://bugs.python.org/file34989/issue_19771.patch
Luiz Poleto added the comment:
The attached patch provide test cases to validate this error. As noted by R.
David Murray in a discussion in the Core-Mentorship list, this error in fact
happens then __init__.py throws an ImportError.
--
keywords: +patch
nosy: +poleto
Added file: http
24 matches
Mail list logo
