[issue31590] CSV module incorrectly treats escaped newlines as new records if unquoted

Vaibhav Mallya added the comment: Hello R. David & Terry! Appreciate your prompt responses. While experimenting with different test cases I realized that escaped slashes and newlines are intrinsically annoying to reason about as stringy-one-liners, so I threw together a small tarball

[issue31590] CSV module incorrectly treats escaped newlines as new records if unquoted

Vaibhav Mallya (mallyvai) added the comment: If there's any way this can be documented that would be a big help, at least. There have been other folks who run into this, and the current behavior is implicit. On Sep 29, 2017 5:44 PM, "R. David Murray" wrote: R. David Murray ad

[issue31590] CSV module incorrectly treats escaped newlines as new records if unquoted

New submission from Vaibhav Mallya: I'm writing python `csv` based-parsers as part of a data processing pipeline that includes Redshift and other data stores upstream and down. It's easy and expected in all of these data stores (http://docs.aws.amazon.com/redshift/latest/dg/r_U

[issue6009] optparse docs say 'default' keyword is deprecated but uses it in most examples

New submission from Vaibhav Mallya : The first example, and several subsequent examples later on in the optparse docs, use 'default' as an argument, even though it's apparently deprecated in favor of set_defaults. At the risk of overstating the obvious, this seems to be inconsi

[issue5906] Risk of confusion in multiprocessing module - daemonic processes

Vaibhav Mallya added the comment: I understand pakal's line of reasoning. The term 'daemon' in the general Unix sense has a specific meaning that is at odds with the multiprocessing module's usage of 'daemon'. Clarification would be useful, I feel, especially if a

[issue5857] Return namedtuples from tokenize token generator

Vaibhav Mallya added the comment: Well, the reason I put in the inner row/col namedtuple initially was because the first mistake I made with the original module was mixing up the row/col indices for a particular case. It certainly caused all sorts of weird headaches. :o) I mean, it seems like

[issue5857] Return namedtuples from tokenize token generator

New submission from Vaibhav Mallya : Returning an anonymous 5-tuple seems like a suboptimal interface since it's so easy to accidentally confuse, for example, the indices of start and end. I've used tokenize.py for several scripts in the past few weeks and I've always ended up wr

[issue5573] multiprocessing Pipe poll() and recv() semantics.

Vaibhav Mallya added the comment: On second thought, it seems like it shouldn't make sense. This forces a destructive check. Suppose we do child.poll() and then child.recv() but it's legitimate data; that data will be removed from the queue even if we just wanted to check if the pipe

[issue5574] multiprocessing queues.py doesn't include JoinableQueue in its __all__ list

New submission from Vaibhav Mallya : Should __all__ = ['Queue', 'SimpleQueue'] in queues.py have JoinableQueue as part of the list as well? Also, multiprocessing's __init__.py does not appear to have SimpleQueue as part of its __all__ - is this expected? SimpleQue

[issue5573] multiprocessing Pipe poll() and recv() semantics.

Changes by Vaibhav Mallya : -- nosy: +jnoller ___ Python tracker <http://bugs.python.org/issue5573> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5573] multiprocessing Pipe poll() and recv() semantics.

New submission from Vaibhav Mallya : Python 2.6.1 (r261:67515, Mar 22 2009, 05:39:39) [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from multiprocessing import

[issue5570] Bus error when calling .poll() on a closed Connection from multiprocessing.Pipe()

Vaibhav Mallya added the comment: Python 2.6.1 (r261:67515, Mar 22 2009, 05:39:39) [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from multiprocessing import Pipe >>