[issue33972] AttributeError in email.message.iter_attachments()

2019-06-25 Thread Abhilash Raj
Change by Abhilash Raj : -- pull_requests: +14195 pull_request: https://github.com/python/cpython/pull/14381 ___ Python tracker <https://bugs.python.org/issue33

[issue29412] IndexError thrown on email.message.Message.get

2019-06-25 Thread Abhilash Raj
Change by Abhilash Raj : -- pull_requests: +14201 pull_request: https://github.com/python/cpython/pull/14387 ___ Python tracker <https://bugs.python.org/issue29

[issue37491] IndexError in get_bare_quoted_string

2019-07-03 Thread Abhilash Raj
New submission from Abhilash Raj : from email.parser import BytesParser, Parser from email.policy import default payload = 'Content-Type:x;\x1b*="\'G\'\\"""""' msg = Parser(policy=default).parsestr(payload) print(msg.get('content-ty

[issue37491] IndexError in get_bare_quoted_string

2019-07-09 Thread Abhilash Raj
Abhilash Raj added the comment: Thanks for the explanation Terry! In this case, value becomes None (I think), which causes the IndexError. -- ___ Python tracker <https://bugs.python.org/issue37

[issue37491] IndexError in get_bare_quoted_string

2019-07-09 Thread Abhilash Raj
Abhilash Raj added the comment: I just wanted to report before I forgot and hence missed some details, turns out the bug report was slightly wrong too. The testcase I provided wasn't right. Here is the right test case to reproduce the exception with master: # bpo_37491.py from email.p

[issue37461] email.parser.Parser hang

2019-07-16 Thread Abhilash Raj
Change by Abhilash Raj : -- pull_requests: +14588 pull_request: https://github.com/python/cpython/pull/14794 ___ Python tracker <https://bugs.python.org/issue37

[issue37461] email.parser.Parser hang

2019-07-17 Thread Abhilash Raj
Abhilash Raj added the comment: I have proposed a PR for this: https://github.com/python/cpython/pull/14794 Reviews are welcome. -- ___ Python tracker <https://bugs.python.org/issue37

[issue37491] IndexError in get_bare_quoted_string

2019-07-17 Thread Abhilash Raj
Change by Abhilash Raj : -- pull_requests: +14607 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14813 ___ Python tracker <https://bugs.python.org/issu

[issue32178] Some invalid email address groups cause an IndexError instead of a HeaderParseError

2019-07-30 Thread Abhilash Raj
Change by Abhilash Raj : -- pull_requests: +14799 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/15044 ___ Python tracker <https://bugs.python.org/issu

[issue37764] email.Message.as_string infinite loop

2019-08-09 Thread Abhilash Raj
Abhilash Raj added the comment: This does look like a side-effect of the commit mentioned by mytran. The issues seems to be that email._header_value_parser.get_unstructured wrongfully assumes that anything leading with '=?' would be a valid rfc 2047 encoded word. This is a sm

[issue37764] email.Message.as_string infinite loop

2019-08-09 Thread Abhilash Raj
Change by Abhilash Raj : -- versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issue37764> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34155] email.utils.parseaddr mistakenly parse an email

2019-08-10 Thread Abhilash Raj
Abhilash Raj added the comment: Closing this since teh PRs are merged. -- stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/i

[issue37764] email.Message.as_string infinite loop

2019-08-10 Thread Abhilash Raj
Abhilash Raj added the comment: Adding security label since this can cause DOS. -- type: -> security ___ Python tracker <https://bugs.python.org/issu

[issue37826] Document PEP 3134 in tutorials/errors.rst

2019-08-11 Thread Abhilash Raj
New submission from Abhilash Raj : Looking at the docs, I couldn't find the `raise from` documentation anywhere in the Errors and Exceptions page (https://docs.python.org/3/tutorial/errors.html) page, which seems to be the landing page for Python Exceptions. I do see however that

[issue32178] Some invalid email address groups cause an IndexError instead of a HeaderParseError

2019-08-11 Thread Abhilash Raj
Change by Abhilash Raj : -- stage: patch review -> resolved status: open -> closed versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.4, Python 3.5, Python 3.6 ___ Python tracker <https://bugs.python.org/i

[issue37826] Document PEP 3134 in tutorials/errors.rst

2019-08-12 Thread Abhilash Raj
Abhilash Raj added the comment: Yes, I am gonna work on a PR. -- ___ Python tracker <https://bugs.python.org/issue37826> ___ ___ Python-bugs-list mailin

[issue37826] Document PEP 3134 in tutorials/errors.rst

2019-08-12 Thread Abhilash Raj
Change by Abhilash Raj : -- keywords: +patch pull_requests: +14964 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15243 ___ Python tracker <https://bugs.python.org/issu

[issue30483] urllib.parse.parse_qsl does not handle unicode data properly

2017-05-26 Thread Abhilash Raj
New submission from Abhilash Raj: After decoding percentage encoded `name` and `values` in the query string, it tries to `_coerce_result` or encode the result to ascii (which is the value of _implicit_encoding). ``` File "/usr/lib/python3.6/urllib/parse.py", line 691, in parse_qsl

[issue36564] Infinite loop with short maximum line lengths in EmailPolicy

2019-05-16 Thread Abhilash Raj
Abhilash Raj added the comment: Moving the conversation here from https://github.com/python/cpython/pull/12732 for David. I previously suggested HeaderParseError because of the fact that we could fail to parse a value into a Header Object in the above scenario. @r.david.murray Would it be

[issue32975] mailbox: It would be nice to move mailbox.Message from legacy email.message.Message API to new EmailMessage API

2018-02-28 Thread Abhilash Raj
New submission from Abhilash Raj : Since Python 3.6 the new EmailMessage API seems to be the default but mailbox.Message still subclasses from the old email.message.Message API. It would be nice to get EmailMessage from mailbox so that one can rely on the new methods and content managers

[issue32975] mailbox: It would be nice to move mailbox.Message from legacy email.message.Message API to new EmailMessage API

2018-02-28 Thread Abhilash Raj
Abhilash Raj added the comment: I should also mention probably that I went ahead and made changes to make this work and I can pass most of the tests, one is failing due to missing `\n` character in the header's value obtained from `msg.get_all('Received')`. I can make a

[issue32975] mailbox: It would be nice to move mailbox.Message from legacy email.message.Message API to new EmailMessage API

2018-03-01 Thread Abhilash Raj
Abhilash Raj added the comment: Can you suggest what would be the best way go about doing that? Given that mailbox.Message subclasses from Message, I am not sure how to proceed about this to make this configurable with a flag. I haven't yet made a PR, but this[1] is the URL to the cha

[issue32144] email.policy.SMTP and SMTPUTF8 doesn't honor linesep's value

2017-11-26 Thread Abhilash Raj
New submission from Abhilash Raj : According to the documentation, email.policy.SMTP and .SMTPUTF8 should have CRLF (`\r\n`) as line endings for text/plain parts. However, a new message parsed using message_from_binary_file with policy.SMTPUTF8 has `\n` as line endings for text/plain parts

[issue32144] email.policy.SMTP and SMTPUTF8 doesn't honor linesep's value

2017-11-27 Thread Abhilash Raj
Abhilash Raj added the comment: I understand that the line endings are meant for "outputs", but what constitutes as output in this case? I now see that `EmailMessage.as_string()` gives me `\r\n` as line endings and, which is probably what you mean by output and `get_content()

[issue32144] email.policy.SMTP and SMTPUTF8 doesn't honor linesep's value

2017-11-29 Thread Abhilash Raj
Abhilash Raj added the comment: Well, I myself missed the "serialization" part, so it probably was my mistake. Maybe a :note: saying line endings are only added in serialized outputs like the one obtained from `as_string()` or `as_bytes()` but not for other methods that return the

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

2018-05-29 Thread Abhilash Raj
New submission from Abhilash Raj : When using `urllib.parse.urlencode` it is impossible to pass an empty list when doseq=True. So, I see the following behavior when using urlencode: In [3]: urlencode({'key': ['value']}, doseq=True) Out[3]: 'key=value' In [4]

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

2018-05-30 Thread Abhilash Raj
Abhilash Raj added the comment: Would it then make sense to add a similar flag, keep_blank_values, in urlencode to achieve similar behavior as parse_qas? -- ___ Python tracker <https://bugs.python.org/issue33

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

2018-05-30 Thread Abhilash Raj
Abhilash Raj added the comment: Ah! But blank lists aren't. That makes sense! Thank you! -- ___ Python tracker <https://bugs.python.org/issue33690> ___ ___

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

2018-05-30 Thread Abhilash Raj
Change by Abhilash Raj : -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue33690> ___ ___ Python-bugs-list

[issue18854] is_multipart and walk should document their treatment of 'message' parts.

2014-05-07 Thread Abhilash Raj
Abhilash Raj added the comment: I have tried to document the issue in the patch as discussed. David: Do you think I should also add an example in walk() method to demonstrate that it does not iterate over a 'message/rfc822' part even though it is multipart? -- keywords: +

[issue18854] is_multipart and walk should document their treatment of 'message' parts.

2014-05-07 Thread Abhilash Raj
Abhilash Raj added the comment: Sorry, my bad. I was a little confused. I have updated the patch and also added the example explicitly. -- Added file: http://bugs.python.org/file35174/email-1.patch ___ Python tracker <http://bugs.python.

[issue21083] Add get_content_disposition() to email.message.Message

2014-05-07 Thread Abhilash Raj
Abhilash Raj added the comment: I read the discussion on issue #21079. Does this issue still needs a patch? If yes I am willing to write one. -- nosy: +abhilash.raj ___ Python tracker <http://bugs.python.org/issue21

[issue21083] Add get_content_disposition() to email.message.Message

2014-05-07 Thread Abhilash Raj
Abhilash Raj added the comment: I have attached my patch. Reviews? -- keywords: +patch Added file: http://bugs.python.org/file35177/c_d.patch ___ Python tracker <http://bugs.python.org/issue21

[issue21083] Add get_content_disposition() to email.message.Message

2014-05-07 Thread Abhilash Raj
Abhilash Raj added the comment: I have updated the patch. The header with mime parameter 'filename' in addition to header value is already added, will that not be enough? -- Added file: http://bugs.python.org/file35178/c_d-revised.patch

[issue634412] RFC 2387 in email package

2014-05-16 Thread Abhilash Raj
Abhilash Raj added the comment: I would like to work on this issue, but I would need a little help to start working on this feature. -- nosy: +abhilash.raj ___ Python tracker <http://bugs.python.org/issue634

[issue634412] RFC 2387 in email package

2014-06-02 Thread Abhilash Raj
Abhilash Raj added the comment: David: I had a look at the examples and documentation as you said. I found some support for multipart/related in the form of `add_related` and `set_related` methods. But I am still confused on how to make content_manager recognize miltipart/related messages

[issue634412] RFC 2387 in email package

2014-06-05 Thread Abhilash Raj
Abhilash Raj added the comment: Will the building of that 'dict' really be that difficult? Can we not walk over all the attachments and simply map cid to name of the attachment? All attachments have to have different names if

[issue634412] RFC 2387 in email package

2014-06-09 Thread Abhilash Raj
Abhilash Raj added the comment: David: How does this API look? https://gist.github.com/maxking/2f37bae7875dde027e3c -- ___ Python tracker <http://bugs.python.org/issue634

[issue634412] RFC 2387 in email package

2014-06-11 Thread Abhilash Raj
Abhilash Raj added the comment: David: What about his API then? https://gist.github.com/maxking/b3ed4f54674e5f480275 Here cids are generated behind the scenes when the html part is added and those cids are assigned to the attachments on the first come basis? Like {0} is replaced by the cid

<    1   2