Re: [Web-SIG] [stdlib-sig] Choosing one of two options for url* in the stdlib reorg

2008-07-28 Thread M.-A. Lemburg
On 2008-03-02 21:11, Brett Cannon wrote: > Well, look at the docs for urllib. There is a list of restrictions > (e.g., does not support the use of proxies which require > authentication). From what I can tell, those items on the list that > are an actual restriction do not carry over to urlli

Re: [Web-SIG] [stdlib-sig] Choosing one of two options for url* in the stdlib reorg

2008-07-28 Thread M.-A. Lemburg
On 2008-03-01 21:13, Brett Cannon wrote: > On Sat, Mar 1, 2008 at 4:34 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: >> On 2008-03-01 05:06, Brett Cannon wrote: >> > Seriously, I just don't want to support two different approaches to >> > the same problem. &

Re: [Web-SIG] [stdlib-sig] Choosing one of two options for url* in the stdlib reorg

2008-07-28 Thread M.-A. Lemburg
On 2008-03-01 05:06, Brett Cannon wrote: > Seriously, I just don't want to support two different approaches to > the same problem. Then what makes you believe that the urllib2 approach is the better one ? Why not move urllib2 to PyPI and keep urllib ? >> It's not really an argument for dropping

Re: [Web-SIG] [stdlib-sig] Choosing one of two options for url* in the stdlib reorg

2008-07-28 Thread M.-A. Lemburg
Brett Cannon wrote: On Fri, Feb 29, 2008 at 11:52 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: On 2008-02-29 20:20, Brett Cannon wrote: >> So, I'd be +1 on the second approach, provided that those >> two classes make the transition into url.request as >> w

Re: [Web-SIG] [stdlib-sig] Choosing one of two options for url* in the stdlib reorg

2008-07-28 Thread M.-A. Lemburg
On 2008-02-29 20:20, Brett Cannon wrote: >> So, I'd be +1 on the second approach, provided that those >> two classes make the transition into url.request as >> well. Otherwise, I'm +1 on the first approach and -1 >> on the second. >> > > Just to make sure I got this straight, as long as the tw

Re: [Web-SIG] [stdlib-sig] Choosing one of two options for url* in the stdlib reorg

2008-07-28 Thread M.-A. Lemburg
On 2008-02-29 01:47, Brett Cannon wrote: > [BCC'ing stdlib-sig and web-sig so that both vote but that I don't > have to clear a bunch of replies in the stdlib-sig mailing list from > people not on both lists =) ] > > With PyCon approaching and having other stuff on my plate to deal with > I want t

Re: [Web-SIG] [DB-SIG] WSGI thread affinity/interleaving

2008-07-28 Thread M.-A. Lemburg
Guido van Rossum wrote: > On 12/19/05, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: >> Ok. In that sense, I think "moving" is not really possible >> with database connections or cursors: these always rely on >> external resources and these may be relying on hav

Re: [Web-SIG] [DB-SIG] WSGI thread affinity/interleaving

2008-07-28 Thread M.-A. Lemburg
James Y Knight wrote: > On Dec 18, 2005, at 6:57 PM, M.-A. Lemburg wrote: > >> Ian Bicking wrote: >> >>> James Y Knight wrote: >>> >>>> I'm worried about database access. Most DBAPI adapters have >>>> threadsafety level 2: "

Re: [Web-SIG] [DB-SIG] WSGI thread affinity/interleaving

2008-07-28 Thread M.-A. Lemburg
Ian Bicking wrote: > James Y Knight wrote: >> I'm worried about database access. Most DBAPI adapters have >> threadsafety level 2: "Threads may share the module and >> connections.". So with those, at least, it should be fine to move a >> connection between threads, since "share OK" implies "