added pyparsing

1 view
Skip to first unread message

Robert Cimrman

unread,
May 19, 2009, 10:53:09 AM5/19/09
to spd...@googlegroups.com
FYI: I have just uploaded pyparsing-1.5.2.spkg to google code site. The
description is not very polished though.

cheers,
r.

PS: Ondrej, sfepy can now compute in spd using scipy iterative solvers,
as umfpack is still missing.


Ondrej Certik

unread,
May 19, 2009, 1:18:00 PM5/19/09
to spd...@googlegroups.com
Hi Robert!

2009/5/19 Robert Cimrman <cimr...@ntc.zcu.cz>:


>
> FYI: I have just uploaded pyparsing-1.5.2.spkg to google code site. The
> description is not very polished though.
>
> cheers,

Thanks! Btw, I think this should probably go to the femhub site:

http://code.google.com/p/femhub/

or do you think pyparsing should go to SPD? I think SPD should be just
scipy/matplotlib/sympy/ipython+notebook, so that it can serve as a
base package for lots of people.

> r.
>
> PS: Ondrej, sfepy can now compute in spd using scipy iterative solvers,
> as umfpack is still missing.

Excellent, great job! Yes, we have to create umfpack.spkg.

Ondrej

Brian Granger

unread,
May 19, 2009, 3:11:23 PM5/19/09
to spd...@googlegroups.com
i think that anything generic should go into spd. But this brings up
a bigger question: even if you put all the fem related things on
femhub, I will want to use some/most of them when working on qsnake.
Would we create another SPD based dist for that? The problem is that
many of the spkgs for these things will be shared between the dists.

Hmm, what do you think?

This almost seems like a "toolbox" type of thing. We could have the
base layer of SPD that includes the common components and then provide
toolsboxes for:

* FEM
* Quantum physics/chemistry
* Electrodynamics
* ???

This is nice because it could allow different toolsboxes to share
various spkgs. I don't know how we would do this, but it seems like
it might be a good match conceptually.

What do you think?

Brian

Ondrej Certik

unread,
May 19, 2009, 3:27:15 PM5/19/09
to spd...@googlegroups.com
On Tue, May 19, 2009 at 12:11 PM, Brian Granger <elliso...@gmail.com> wrote:
>
> i think that anything generic should go into spd.  But this brings up
> a bigger question:  even if you put all the fem related things on
> femhub, I will want to use some/most of them when working on qsnake.
> Would we create another SPD based dist for that?  The problem is that
> many of the spkgs for these things will be shared between the dists.
>
> Hmm, what do you think?
>
> This almost seems like a "toolbox" type of thing. We could have the
> base layer of SPD that includes the common components and then provide
> toolsboxes for:
>
> * FEM
> * Quantum physics/chemistry
> * Electrodynamics
> * ???
>
> This is nice because it could allow different toolsboxes to share
> various spkgs.  I don't know how we would do this, but it seems like
> it might be a good match conceptually.

I think Sage wants to do exactly that, in the long term. Am I right Michael?

I need this now, so I'll just keep releasing SPD with minimal
packages, and then release femhub with finite element stuff, and we
can release qsnake, with some other stuff. I guess there is absolutely
no problem in just copying one spkg from femhub to qsnake. Once this
crystallises, we can move the common denominator to SPD itself.

Ondrej

mabshoff

unread,
May 19, 2009, 3:29:32 PM5/19/09
to spd-dev


On May 19, 12:27 pm, Ondrej Certik <ond...@certik.cz> wrote:
> On Tue, May 19, 2009 at 12:11 PM, Brian Granger <ellisonbg....@gmail.com> wrote:

<SNIP>

> > This is nice because it could allow different toolsboxes to share
> > various spkgs.  I don't know how we would do this, but it seems like
> > it might be a good match conceptually.
>
> I think Sage wants to do exactly that, in the long term. Am I right Michael?

Yes, this is kind of the point.

> I need this now, so I'll just keep releasing SPD with minimal
> packages, and then release femhub with finite element stuff, and we
> can release qsnake, with some other stuff. I guess there is absolutely
> no problem in just copying one spkg from femhub to qsnake. Once this
> crystallises, we can move the common denominator to SPD itself.

+1

> Ondrej

Cheers,

Michael

Robert Cimrman

unread,
May 20, 2009, 4:26:20 AM5/20/09
to spd...@googlegroups.com
Ondrej Certik wrote:
> Hi Robert!
>
> 2009/5/19 Robert Cimrman <cimr...@ntc.zcu.cz>:
>> FYI: I have just uploaded pyparsing-1.5.2.spkg to google code site. The
>> description is not very polished though.
>>
>> cheers,
>
> Thanks! Btw, I think this should probably go to the femhub site:
>
> http://code.google.com/p/femhub/
>
> or do you think pyparsing should go to SPD? I think SPD should be just
> scipy/matplotlib/sympy/ipython+notebook, so that it can serve as a
> base package for lots of people.

OK. I was not sure where to upload it, feel free to move it :)

Btw. some version of pyparsing seems to be in matplotlib itself. But I
would rather have a separate spkg.

r.

Reply all
Reply to author
Forward
0 new messages