Le mardi 18 octobre 2005 à 19:17 +0200, Antoine Pitrou a écrit :
> > What would this mythical block statement look like that would make
> > properties easier to write than the above late-binding or the subclass
> > Property recipe?
>
> I suppose something like:
>
Le mardi 18 octobre 2005 à 12:56 -0700, Josiah Carlson a écrit :
> You are saving 3 lines over the decorator/function approach [...]
Well, obviously, the point of a block statement or construct is that it
can be applied to many other things than properties. Otherwise it is
overkill as you imply.
Hi Michele,
> Property p():
> "I am a property"
> def fget(self):
> pass
> def fset(self):
> pass
> def fdel(self):
> pass
In effect this is quite similar to the proposal I've done (except that
you've reversed the traditional assignment order from "p = Pro
> There are many design alternatives: one option would be to support
> *three* internal representations in a single type, generating the
> others from the one operation existing as needed. The default, initial
> representation might be UTF-8, with UCS-4 only being generated when
> indexing occurs,
> Thanks for these data. This mostly reflects my experience with German
> and French users: some people would like to use non-ASCII identifiers
> if they could, other argue they never would as a matter of principle.
> Of course, transliteration is more straight-forward.
FWIW, being French, I don'
Hi,
FWIW, I opened a bug report on Subversion some time ago so that patterns
like "*.pyc" and "*.pyo" are ignored by default in Subversion. Feel free
to add comments or vote for the bug:
http://subversion.tigris.org/issues/show_bug.cgi?id=2415
Regards
Antoine.
> It allows everything in Python to be both mutable and hashable,
I don't understand, since it's already the case. Any user-defined object
is at the same time mutable and hashable.
And if you want the hash value to follow the changes in attribute
values, just define an appropriate __hash__ method
Le dimanche 30 octobre 2005 à 19:08 -0600, [EMAIL PROTECTED] a écrit :
> Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort
> of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built
> from source back in the May timeframe. Should I upgrade to 1.2.3 as a
>
> You are missing a point here: string methods were introduced
> to make switching from plain 8-bit strings to Unicode easier.
Is it the only purpose ?
I agree with the OP that using string methods is much nicer and more
convenient than having to import separate modules.
Especially, it is nice to
4901 - 4909 of 4909 matches
Mail list logo
