PEP: XXX
Title: Postfix type declarations
Version: $Revision: $
Last-Modified: $Date: $
Author: Georg Brandl <[EMAIL PROTECTED]>
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 01-Apr-2007
Python-Version: 3.0
Abstract
This PEP proposes the addition of a postfix typ
Brilliant!
On 4/1/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> def foo${LATIN SMALL LETTER LAMBDA WITH STROKE}$(x${DOUBLE-STRUCK
> CAPITAL C}$):
> return None${ZERO WIDTH NO-BREAK SPACE}$
>
> This is still easy to read and makes the full power of type-annotated Python
> available t
On 4/1/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
[...]
Example
===
This is the standard ``os.path.normpath`` function, converted to type
declaration
syntax::
def normpathƛ(path✎)✎:
"""Normalize path, eliminating double slashes, etc."""
if path✎ == '':
On 4/1/07, Gustavo Carneiro <[EMAIL PROTECTED]> wrote:
On 4/1/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
[...]
> Example
> ===
>
> This is the standard ``os.path.normpath`` function, converted to type
> declaration
> syntax::
>
> def normpathƛ(path✎)✎:
> """Normalize path, el
Johann C. Rocholl wrote:
> Brilliant!
>
> On 4/1/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> def foo${LATIN SMALL LETTER LAMBDA WITH STROKE}$(x${DOUBLE-STRUCK
>> CAPITAL C}$):
>> return None${ZERO WIDTH NO-BREAK SPACE}$
>>
>> This is still easy to read and makes the full power of
on 31.03.2007 22:39 Guido van Rossum said the following:
> If you ask me, having it hosted by Trent is probably more helpful for
> its popularity than putting it in the Python source distro; the Tools
> directory is mostly a poorly-maintained collection of trivia I wrote
> many years ago that is no
Eric Huss wrote:
> Some subclasses of Exception are no longer pickleable in Python 2.5. An
> example:
>
[snip]
>
> Does anyone have any thoughts about this? Is it a bug?
>
> I can imagine one could argue that exceptions should call the base
> __init__ method to properly set args, but there are
It's out of character for the standard library, since (regardless of
whether it's implemented in Python or part of the standard library)
it's a stand-alone utility. I don't see much use for this as a library
module.
On 4/1/07, Stefan Rank <[EMAIL PROTECTED]> wrote:
> on 31.03.2007 22:39 Guido van
Python Doc Problem Example: os.path.split()
Xah Lee, 20050918
Quote from: http://www.python.org/doc/2.4.1/lib/module-os.path.html
«
split(path)
Split the pathname path into a pair, (head, tail) where tail is
the last pathname component and head is everything leading up to
that. The
Raymond Hettinger schrieb:
> [Stephen Hansen=
>> I just wanted to offer a gentle prod to see if a decision can be made;
>> if any decision requires an adjustment to patches, tests and documentation,
>> I'm willing to do them.
>
> We should get a pronouncement on this or else whatever goes out in
on 01.04.2007 17:23 Guido van Rossum said the following:
> It's out of character for the standard library, since (regardless of
> whether it's implemented in Python or part of the standard library)
> it's a stand-alone utility. I don't see much use for this as a library
> module.
I use it as a lib
On 4/1/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
[snip several pages of excellent ideas]
>
> The mapping between types and declarators is not static. It can be completely
> customized by the programmer, but for convenience there are some predefined
> mappings for some built-in types:
>
>
Stefan> I use it as a library, because it encodes knowledge about
Stefan> locating executables on different platforms, especially Windows.
Stefan> Unixoids have which and the search is relatively
Stefan> straightforward. Windows searches paths in PATH and in the
Stefan> regist
> I think that this is a bug, but removing those methods is not the right
> solution. The __reduce__ method is needed because builtin exceptions
> don't store their attributes in the __dict__ anymore; if you remove it,
> then those attributes will be lost during pickling. The __setstate__
> metho
Ok, sorry, that *is* a valid use case. Since Trent on his webpage
suggests his code as a stdlib replacement I support this now. (But I'm
not going to take further action -- I hope you can get one of the
regular 2.6 dev guys to adopt this case. Also, the PSF needs to have a
contribution form on file
+18446744073709551616 from me too.
This also fits nicely in with my plan to abandon the python-dev and
python-3000 mailing lists. Mailing lists are so 20th century! I
propose that from now on, all Python development should be carried out
on blogs, so that readers can use customized RSS feeds to re
Has anyone heard the Python+XUL community cry "I'm not dead yet!" or are
they really dead? I haven't seen mentions of new work in these areas
lately. XUL in general seems to have died (so many broken links on XUL
pages). Was this just a fad? If not, and if there's some really useful
of it (
> Has anyone heard the Python+XUL community cry "I'm not dead
> yet!" or are
> they really dead? I haven't seen mentions of new work in these areas
> lately. XUL in general seems to have died (so many broken
> links on XUL
> pages). Was this just a fad? If not, and if there's some
> really usef
18 matches
Mail list logo
