Re: [Python-Dev] urlparse.urlunsplit should be smarter about +
On Fri, May 7, 2010 at 21:04, Senthil Kumaran wrote:
> On Sat, May 8, 2010 at 8:19 AM, David Abrahams wrote:
> >
> > This is a bug report. bugs.python.org seems to be down.
>
> Tracked here: http://bugs.python.org/issue8656
>
> > >>> urlunsplit(urlsplit('git+file:///foo/bar/baz'))
>
> Is 'git+file' a valid protocol? Or was it just your example?
> I don't see any reason for it to be invalid but I don't find
> authoritative references either.
>
RFC 3986 is pretty clear on allowing '+' in scheme names, in principle if
not necessarily in practice:
http://tools.ietf.org/html/rfc3986#section-3.1
> --
> Senthil
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/ddborowitz%40gmail.com
>
--
It is better to be quotable than to be honest.
-Tom Stoppard
Borowitz
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEP 7 updated
On Mon, May 10, 2010 at 07:09, Ronald Oussoren wrote: > > On 9 May, 2010, at 20:33, Antoine Pitrou wrote: > > > > > Hello, > > > > The untabification of C files didn't produce any noticeable problem on > > the buildbots. I've updated PEP 7 with the mention that all C files > > should be 4-space indented, and removed the obsolete wording about > > some files being indented with tabs. > > Does anyone know of a way to teach vim that C sources in a python checkout > should have 4-space indents without changing the defaults for other C files? > :help autocmd-patterns has this example, which should be easy to adapt: :autocmd BufRead /vim/src/*.c set cindent Set the 'cindent' option for C files in the /vim/src directory. > Ronald > > > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/ddborowitz%40gmail.com > > -- It is better to be quotable than to be honest. -Tom Stoppard Borowitz ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] On quote styles
Python itself doesn't appear to follow that principle: >>> "Ain't nothin' stoppin' this from usin' \"double quotes\"." 'Ain\'t nothin\' stoppin\' this from usin\' "double quotes".' IMHO it's a useful rule of thumb, but like most of the other alternatives presented in this thread, taken to extremes, it can get silly. (Imagine a string with 10 's and 9 "s, and adding two more "s to it...) But I suppose that's another reason these are just guidelines. Dave Borowitz On Mon, May 12, 2008 at 5:00 PM, <[EMAIL PROTECTED]> wrote: > > "Benji" == Benji York <[EMAIL PROTECTED]> writes: > >Benji> One such entry could be "Do what python does.": > >>>> 'I am a string.' >'I am a string.' >>>> "I'm a string" >"I'm a string" > > That would be the principle of fewest backslashes. ;-) > > Skip > ___ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/ddborowitz%40gmail.com > -- It is better to be quotable than to be honest. -Tom Stoppard Borowitz ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
