On Thu, Apr 05, 2007 at 04:24:01PM -0400, Alan G Isaac wrote:
> On Thu, 5 Apr 2007, Gael Varoquaux apparently wrote:
> > Actually I do it the other way around nowadays.
> Except in the tutorial?
Yes, shame on me, I changed policy after writing it. I guess I should
correct it. I'll add this to m
On Thu, 5 Apr 2007, Gael Varoquaux apparently wrote:
> Actually I do it the other way around nowadays.
Except in the tutorial?
But anyway, I'm willing to try anything that gets them moving.
It is true that avoiding the appearance of complexity can
sometimes add complexity.
Cheers,
Alan Isaac
On Thu, Apr 05, 2007 at 01:36:28PM -0400, Alan G Isaac wrote:
> On Thu, 05 Apr 2007, Christopher Barker apparently wrote:
> > I think, in a situation when you are intending the class
> > attribute to be over-ridden by an instance attribute, then
> > it's clearer to define it as an instance attri
On Thu, 05 Apr 2007, Christopher Barker apparently wrote:
> I think, in a situation when you are intending the class
> attribute to be over-ridden by an instance attribute, then
> it's clearer to define it as an instance attribute in the
> first place:
This is true of course.
BUT I am with Ga
Gael Varoquaux wrote:
> I have recently
> started avoided using class attributes when not necessary,
I agree. I use class attributes when I need, well, class attributes.
That is an attribute that is shared by all the instances of the class.
In fact, in the example:
class A:
x = 4
A_instanc
On Wed, Apr 04, 2007 at 04:46:59PM -0700, Sebastian Haase wrote:
> Why do you define e.g. the Point class like this:
> class Point(object):
> """ 3D Point objects """
> x = 0.
> y = 0.
> z = 0.
> and not like this:
> class Point(object):
> """ 3D Point objects """
> def __i
On Wed, Apr 04, 2007 at 05:07:38PM -0500, Robert Kern wrote:
> Ah, sorry, I missed the bit where you said you only built inside
> enthought/traits/. I'd build the whole suite. It'll take a bit,
> building the extension modules for Kiva, but nothing too bad. I don't
> know why you'd get the error, t
Bill Baxter wrote:
> Ok, I got another hopefully easy question:
>
> Why this:
> class Point(object):
> ...
>
> Instead of the style that's used in the Python tutorial in the
> 'classes' chapter:
> class Point:
> ...
Because the former make new-style classes and the latt
Ok, I got another hopefully easy question:
Why this:
class Point(object):
...
Instead of the style that's used in the Python tutorial in the
'classes' chapter:
class Point:
...
--bb
On 4/5/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
>
> > OK, b
Sebastian Haase wrote:
> OK, but what is "wrong" with the first way !? I mean, it somehow
> seems not like "it's usually done" in Python ? Normally there is
> always a __init__(self) that sets up everything referring to self --
> why is this tutorial doing it differently ?
Because it makes the
On 4/4/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
> > Hello Gael,
> >
> > Short question regarding your tutorial -- I'm very intrigued by traits
> > and would like to use them too
> > Why do you define e.g. the Point class like this:
> > class Point(object):
> > ""
Sebastian Haase wrote:
> Hello Gael,
>
> Short question regarding your tutorial -- I'm very intrigued by traits
> and would like to use them too
> Why do you define e.g. the Point class like this:
> class Point(object):
> """ 3D Point objects """
> x = 0.
> y = 0.
> z = 0.
>
Sebastian Haase wrote:
> Is enthought now defaulting to numpy ?
Still set NUMERIX=numpy for now.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
--
Hello Gael,
Short question regarding your tutorial -- I'm very intrigued by traits
and would like to use them too
Why do you define e.g. the Point class like this:
class Point(object):
""" 3D Point objects """
x = 0.
y = 0.
z = 0.
and not like this:
class Point(object):
"
Is enthought now defaulting to numpy ?
-Sebastian
On 4/4/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > --- Discussion of Numerical Python > [EMAIL PROTECTED]
> > wrote:
>
> >>> If I get the latest
> > SVN of the enthought tool suite, go to enthought/src/lib/enthought
[EMAIL PROTECTED] wrote:
> --- Discussion of Numerical Python [EMAIL PROTECTED]
> wrote:
>>> If I get the latest
> SVN of the enthought tool suite, go to enthought/src/lib/enthought/traits,
>
>>> and build with
>>>
>>> python setup.py build_src build_clib build_ext
> --inplace
>>>
>>> as suggest
Gael Varoquaux wrote:
> On Wed, Apr 04, 2007 at 04:36:19PM -0500, Robert Kern wrote:
>>> As you can see, I'm very confused... if only there was a traits Python
>>> egg...
>
>> There are, but only binaries for win32 at the moment. Building from
>> source on OS X should be straightforward, though.
>
--- Discussion of Numerical Python > BTW, I'm using Python 2.4.4 on Macintel, with wxPython-2.8.0.
>
> We require wxPython 2.6 at the moment.
Ah, good to know. This could
explain the errors I get when compiling in place.
> > If I get the latest
SVN of the enthought tool suite, go to enthought/
On Wed, Apr 04, 2007 at 04:36:19PM -0500, Robert Kern wrote:
> > As you can see, I'm very confused... if only there was a traits Python
> > egg...
> There are, but only binaries for win32 at the moment. Building from
> source on OS X should be straightforward, though.
How about linux eggs ? I had
[EMAIL PROTECTED] wrote:
> Hello Gael (numpy friends),
>
> I'd love to use Traits and TraitsUI. It looks
> like a very promising approach. But why is it so difficult to install? If
> I download the source from http://code.enthought.com/traits/, and follow the
> instructions in enthought.traits-1.1
Hello Gael (numpy friends),
I'd love to use Traits and TraitsUI. It looks
like a very promising approach. But why is it so difficult to install? If
I download the source from http://code.enthought.com/traits/, and follow the
instructions in enthought.traits-1.1.0/README, and then run the "code sni
Thanks for the reply I will sure try to use it and so some small software.
Giorgio
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
You can do a script with a GUI front end, as described in the first
chapter of my tutorial
http://gael-varoquaux.info/computers/traits_tutorial/traits_tutorial.html
. You can also build a complete interactive application, as described in
the rest of the tutorial, but this is more work.
If you have
Hello Dear All,
I just have a question for all that uses python/numpy/scipy/matplotlib
for making science.
I use with no problem in my computer python+numpy+scipy+matplotlib and
I'm very satisfied with them.
I was a matlab user. I still not have unearthed the power ot python but
I'm happy to u
24 matches
Mail list logo
