[Patches] [ python-Patches-448841 ] Patch for PEP 249

[noreply@sourceforge.net]

Patches item #448841, was opened at 2001-08-07 10:14
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=448841&group_id=5470

Category: Modules
Group: None
Status: Closed
Resolution: None
Priority: 5
Submitted By: Bob Kline (bkline)
Assigned to: M.-A. Lemburg (lemburg)
Summary: Patch for PEP 249

Initial Comment:
This patch is submitted to clarify the usage of the 
executemany() method of the Cursor class.  Language is 
added to make it clear that use of this method for an 
operation which results in one or more result sets 
constitutes undefined behavior, and that in such a 
case the implementation is permitted (but not 
required) to raise an exception.

----------------------------------------------------------------------

>Comment By: Bob Kline (bkline)
Date: 2001-08-08 05:18

Message:
Logged In: YES 
user_id=291529

Thanks very much!

Bob

----------------------------------------------------------------------

Comment By: M.-A. Lemburg (lemburg)
Date: 2001-08-08 01:43

Message:
Logged In: YES 
user_id=38388

Checked in the patch.

----------------------------------------------------------------------

Comment By: M.-A. Lemburg (lemburg)
Date: 2001-08-08 00:54

Message:
Logged In: YES 
user_id=38388

Everything's fine Bob :-)

I'll check in your patch today. Thanks.

----------------------------------------------------------------------

Comment By: Bob Kline (bkline)
Date: 2001-08-08 00:26

Message:
Logged In: YES 
user_id=291529

No problem. :->}

Bob Kline
mailto:bkline@rksystems.com


----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2001-08-08 00:08

Message:
Logged In: YES 
user_id=21627

I wasn't aware that PEP 1 actually suggests to use the patch
manager; it is alright then that you did so. I had the
sentence 

A better strategy is to encourage public feedback directly
to the PEP author, who collects and integrates the comments
back into the PEP.

from the PEP in mind; my apologies.

----------------------------------------------------------------------

Comment By: Bob Kline (bkline)
Date: 2001-08-07 22:47

Message:
Logged In: YES 
user_id=291529

loewis:

OK, I'm very confused.  I originally posted the suggestion 
for this enhancement to the PEP to the DB-SIG, which surely 
qualifies as a public Python forum.  A discussion ensued, I 
asked what the best way to submit the suggested 
modification would be, and Marc-André himself replied 
asking that I submit a patch against the PEP to 
SourceForge.  I then read PEP1, which says, "Please use the 
SourceForge bug manager[6] if you want to report problems 
with PEPs, or better yet, the SourceForge patch manager[2] 
for submitting patches to PEPs."

I followed the link at [2], which took me here, where I 
uploaded the patch and reported back to Marc-André letting 
him know I had done so (and provided him with a copy of the 
patch).

So, where exactly did I screw up, please?

[2] http://sourceforge.net/tracker/?
group_id=5470&atid=305470

[6] http://sourceforge.net/tracker/?
group_id=5470&atid=305470

Bob Kline
mailto:bkline@rksystems.com



----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2001-08-07 21:47

Message:
Logged In: YES 
user_id=21627

Patches to PEPs normally would not need to go through the 
patch manager. According to PEP1, you are supposed to send 
them directly to the PEP author in the initial discussion, 
or sent it as a comment to the PEP in the public 
discussion fora, such as comp.lang.python. The PEP author 
is than supposed to integrate it into the PEP - even if he 
disagrees with the proposal, he is somehow to record in 
the PEP that people have raised this opinion.
Anyway, since this is Marc-Andre's PEP, I'm assigning the 
patch to him.


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=448841&group_id=5470