On 01/14/2012 10:27 PM, Rick Johnson wrote:
> Face it, Guido has broken Python's cherry. She is no longer pure.
> You're acting like some over- protective father. WAKE UP! Python is a
> promiscuous little whore and she's on girls gone wild (Volume 4000)
> shaking her little money maker. We should a
On 01/15/2012 06:23 AM, Rick Johnson wrote:
So how do we solve this dilemma you ask??? Well, we need to "mark"
method OR variable names (OR both!) with syntactic markers so there
will be NO confusion.
Observe:
def $method(self):pass
self.@instanceveriable
self.@@classvariable
There is
On Sat, 14 Jan 2012 21:27:32 -0800, Rick Johnson wrote:
> On Jan 14, 10:23 pm, Steven D'Aprano +comp.lang.pyt...@pearwood.info> wrote:
>
>> This is not Java, and we prefer Python terminology.
>>
>> A variable holding an int is an int variable. A variable holding a
>> string is a string variable.
On Jan 14, 10:23 pm, Steven D'Aprano wrote:
> This is not Java, and we prefer Python terminology.
>
> A variable holding an int is an int variable.
> A variable holding a string is a string variable.
> A variable holding a list is a list variable.
> A variable holding an instance is an instance v
On Sat, 14 Jan 2012 14:58:26 -0600, Evan Driscoll wrote:
> On 01/14/2012 02:11 PM, Devin Jeanpierre wrote:
>> On Sat, Jan 14, 2012 at 2:23 PM, Rick Johnson
>> wrote:
>>> THAT PISSES ME OFF!!!>:( We should never be forced to guess if a name
>>> is a callable or a variable!
>>>
>>> So how do we so
On Sat, 14 Jan 2012 11:23:29 -0800, Rick Johnson wrote:
> On Jan 14, 1:01 pm, Devin Jeanpierre wrote:
>
>> What's "horrendous" about the datetime module interface? Your listed
>> complaints (OOP etc.) don't seem to have anything to do with it.
>
> Well my immediate complaint about date-time is
On Sat, 14 Jan 2012 10:54:57 -0800, Rick Johnson wrote:
> The interface for these modules is not intuitive. Instead of creating
> true OOP objects we have lists and strings.
Lists and strings are true OOP objects.
--
Steven
--
http://mail.python.org/mailman/listinfo/python-list
On Sun, Jan 15, 2012 at 10:19 AM, Rick Johnson
wrote:
> On Jan 14, 2:58 pm, Evan Driscoll wrote:
>> On 01/14/2012 02:11 PM, Devin Jeanpierre wrote:
>
>> It also has some problems. For instance, if an object has a member which
>> is a type that implements __call__ but is also useful to access "on
On Jan 14, 2:58 pm, Evan Driscoll wrote:
> On 01/14/2012 02:11 PM, Devin Jeanpierre wrote:
> It also has some problems. For instance, if an object has a member which
> is a type that implements __call__ but is also useful to access "on its
> own", is that a field or a function?
Can you site a re
On 01/14/2012 02:11 PM, Devin Jeanpierre wrote:
On Sat, Jan 14, 2012 at 2:23 PM, Rick Johnson
wrote:
THAT PISSES ME OFF!!!>:( We should never be forced to guess if a name
is a callable or a variable!
So how do we solve this dilemma you ask??? Well, we need to "mark"
method OR variable names (
On Sun, Jan 15, 2012 at 6:23 AM, Rick Johnson
wrote:
> Observe:
> def $method(self):pass
> self.@instanceveriable
> self.@@classvariable
Are you deliberately inverting what PHP does, with $variablename?
(Incidentally, that's one of the things that irks me about PHP -
adorned variable names.)
On Jan 14, 1:23 pm, Rick Johnson wrote:
> def $method(self):pass
> self.@instanceveriable
> self.@@classvariable
Actually, class level methods can be accessed through
ClassIdentifier.method, and instance methods through
instanceidentifier.instancemethod. So decorating methods becomes
moot.
On Sat, Jan 14, 2012 at 2:23 PM, Rick Johnson
wrote:
> THAT PISSES ME OFF!!! >:( We should never be forced to guess if a name
> is a callable or a variable!
>
> So how do we solve this dilemma you ask??? Well, we need to "mark"
> method OR variable names (OR both!) with syntactic markers so there
On Jan 14, 1:01 pm, Devin Jeanpierre wrote:
> What's "horrendous" about the datetime module interface? Your listed
> complaints (OOP etc.) don't seem to have anything to do with it.
Well my immediate complaint about date-time is actually a problem with
the syntactic quandaries of the Python lang
On Sat, Jan 14, 2012 at 1:54 PM, Rick Johnson
wrote:
> The interface for these modules is not intuitive. Instead of creating
> true OOP objects we have lists and strings. Any calendar object should
> expose string names of both: days of the week and months of the year.
> It seems one (or possibly
15 matches
Mail list logo
