[issue1859] textwrap doesn't linebreak on "\n"

Chris Jerdonek added the comment: Here is an even simpler failing test case: >>> from textwrap import wrap >>> wrap("a\nb", replace_whitespace=False) ['a\nb'] It should return-- ['a', 'b'] I will start working on this issue by assembling formal test cases. -- nosy: +cjerdonek _

[issue15450] Allow dircmp.subdirs to behave well under subclassing

Changes by Chris Jerdonek : -- nosy: +eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue15231] update PyPI upload doc to say --no-raw passed to rst2html.py

Eli Bendersky added the comment: Feel free to change it, I don't mind. I think the intention is clear anyway. -- ___ Python tracker ___ _

[issue1859] textwrap doesn't linebreak on "\n"

Chris Jerdonek added the comment: > def wrap_paragraphs(text, width=70, **kwargs): > return [line for para in text.splitlines() for line in > textwrap.wrap(para, width, **kwargs)] I just want to point out that, at least for the purposes of this issue, I don't believe the above is equivale

[issue15364] sysconfig confused by relative paths

Roundup Robot added the comment: New changeset c2618b916081 by Ned Deily in branch 'default': Issue #15364: Fix test_srcdir for the installed case. http://hg.python.org/cpython/rev/c2618b916081 -- ___ Python tracker

[issue1859] textwrap doesn't linebreak on "\n"

Serhiy Storchaka added the comment: def wrap_paragraphs(text, width=70, **kwargs): return [line for para in text.splitlines() for line in textwrap.wrap(para, width, **kwargs) or ['']] -- ___ Python tracker ___

[issue15295] Import machinery documentation

Eric Snow added the comment: Awesome addition, Barry! Bless you for slogging through this. Here are some thoughts (prepare one grain of salt for each): * (glossary.rst) finder: should also reference PEP 420. * (glossary.rst) module: s/contain/containing/ * (glossary.rst) path importer: I lik

[issue15457] consistent treatment of generator terminology

Terry J. Reedy added the comment: Up until today, I had assumed that it was the generator.__next__ method that was associated with the compiled body. But in writing my response, I investigated and discovered >>> def gf(): yield None >>> gf().gi_code is gf.__code__ True Then i realized that

[issue15457] consistent treatment of generator terminology

Terry J. Reedy added the comment: I will try to read your new patch when I am fresher. -- ___ Python tracker ___ ___ Python-bugs-list

<    1   2