public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Achim Gaedke <Achim.Gaedke@uni-koeln.de>
To: "Jochen Küpper" <jochen@jochen-kuepper.de>
Cc: numpy-discussion@lists.sourceforge.net,
	achimgaedke@users.sourceforge.net,
	gsl-discuss@sources.redhat.com
Subject: Re: Numpy2 and GSL
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <3C034BFA.FBB64E94@uni-koeln.de> (raw)
In-Reply-To: <m3herhuk76.fsf@box.home.de>

Ok, there is a clear need for the facility of easy contribution.
Please be patient until Friday, December 7th. Then I have time to let it happen.

It is right that the oficial site for this project is at pygsl.sourcefogrge.net
(Brian Gough, can you change the link on the gsl homepage, thanks :-) )

But I will show some discussion points that must be clear before a cvs release:

- Is the file and directory structure fully expandable, can several persons work
parallel?

- Should classes be created with excellent working objects or should it be a 1:1
wrapper?

- should there be one interface dynamic library or more than one?

- Is there an other way expect that of the GPL (personally prefered, but other
opinions should be discussed before the contribution of source)

Some questions of minor weight:

- Is the tuple return value for (value,error) ok in the sf module?

- Test cases are needed

These questions are the reason, why I do not simply "copy" my code into cvs.

Jochen Küpper wrote:
> 
> It only provides wrapper for the special functions, but more is to
> come. (Hopefully Achim will put the cvs on sf soon.)
> 
> Yes, I agree, PyGSL should be fully integrated with Numpy2, but it
> should probably also remain a separate project -- as Numpy should stay
> a base layer for all kind of numerical stuff and hopefully make it
> into core python at some point (my personal wish, no more, AFAICT!).
> 
> I think when PyGSL will fully go to SF (or anything similar) more
> people would start contributing and we should have a fine general
> numerical algorithms library for python soon!
> 

I agree with Jochen and I'd like to move to the core of Python too. But this is
far away and I hate monolithic distributions.

If there is the need to discuss seperately about PyGSL we can do that here or at
the gsl-discuss list mailto:gsl-discuss@sources.redhat.com . But there is also
the possibility of a mailinglist at pygsl.sourceforge.net . Please let me know.

WARNING: multiple messages have this Message-ID
From: Achim Gaedke <Achim.Gaedke@uni-koeln.de>
To: Jochen Küpper <jochen@jochen-kuepper.de>
Cc: numpy-discussion@lists.sourceforge.net,
	achimgaedke@users.sourceforge.net,
	gsl-discuss@sources.redhat.com
Subject: Re: Numpy2 and GSL
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <3C034BFA.FBB64E94@uni-koeln.de> (raw)
Message-ID: <20011219132000.7RAQklVffpm-6vbvsUATQQ7Gx2jXq1-LqmDP-1AjU3A@z> (raw)
In-Reply-To: <m3herhuk76.fsf@box.home.de>

Ok, there is a clear need for the facility of easy contribution.
Please be patient until Friday, December 7th. Then I have time to let it happen.

It is right that the oficial site for this project is at pygsl.sourcefogrge.net
(Brian Gough, can you change the link on the gsl homepage, thanks :-) )

But I will show some discussion points that must be clear before a cvs release:

- Is the file and directory structure fully expandable, can several persons work
parallel?

- Should classes be created with excellent working objects or should it be a 1:1
wrapper?

- should there be one interface dynamic library or more than one?

- Is there an other way expect that of the GPL (personally prefered, but other
opinions should be discussed before the contribution of source)

Some questions of minor weight:

- Is the tuple return value for (value,error) ok in the sf module?

- Test cases are needed

These questions are the reason, why I do not simply "copy" my code into cvs.

Jochen Küpper wrote:
> 
> It only provides wrapper for the special functions, but more is to
> come. (Hopefully Achim will put the cvs on sf soon.)
> 
> Yes, I agree, PyGSL should be fully integrated with Numpy2, but it
> should probably also remain a separate project -- as Numpy should stay
> a base layer for all kind of numerical stuff and hopefully make it
> into core python at some point (my personal wish, no more, AFAICT!).
> 
> I think when PyGSL will fully go to SF (or anything similar) more
> people would start contributing and we should have a fine general
> numerical algorithms library for python soon!
> 

I agree with Jochen and I'd like to move to the core of Python too. But this is
far away and I hate monolithic distributions.

If there is the need to discuss seperately about PyGSL we can do that here or at
the gsl-discuss list mailto:gsl-discuss@sources.redhat.com . But there is also
the possibility of a mailinglist at pygsl.sourceforge.net . Please let me know.

WARNING: multiple messages have this Message-ID
From: Achim Gaedke <Achim.Gaedke@uni-koeln.de>
To: "Jochen Küpper" <jochen@jochen-kuepper.de>
Cc: numpy-discussion@lists.sourceforge.net,
	achimgaedke@users.sourceforge.net,
	gsl-discuss@sources.redhat.com
Subject: Re: Numpy2 and GSL
Date: Sun, 18 Nov 2001 13:11:00 -0000	[thread overview]
Message-ID: <3C034BFA.FBB64E94@uni-koeln.de> (raw)
Message-ID: <20011118131100.7hzgHMthO1hSGit4GU2uObOm-0Rz3qhlVv7sZZfHM9k@z> (raw)
In-Reply-To: <m3herhuk76.fsf@box.home.de>

Ok, there is a clear need for the facility of easy contribution.
Please be patient until Friday, December 7th. Then I have time to let it happen.

It is right that the oficial site for this project is at pygsl.sourcefogrge.net
(Brian Gough, can you change the link on the gsl homepage, thanks :-) )

But I will show some discussion points that must be clear before a cvs release:

- Is the file and directory structure fully expandable, can several persons work
parallel?

- Should classes be created with excellent working objects or should it be a 1:1
wrapper?

- should there be one interface dynamic library or more than one?

- Is there an other way expect that of the GPL (personally prefered, but other
opinions should be discussed before the contribution of source)

Some questions of minor weight:

- Is the tuple return value for (value,error) ok in the sf module?

- Test cases are needed

These questions are the reason, why I do not simply "copy" my code into cvs.

Jochen Küpper wrote:
> 
> It only provides wrapper for the special functions, but more is to
> come. (Hopefully Achim will put the cvs on sf soon.)
> 
> Yes, I agree, PyGSL should be fully integrated with Numpy2, but it
> should probably also remain a separate project -- as Numpy should stay
> a base layer for all kind of numerical stuff and hopefully make it
> into core python at some point (my personal wish, no more, AFAICT!).
> 
> I think when PyGSL will fully go to SF (or anything similar) more
> people would start contributing and we should have a fine general
> numerical algorithms library for python soon!
> 

I agree with Jochen and I'd like to move to the core of Python too. But this is
far away and I hate monolithic distributions.

If there is the need to discuss seperately about PyGSL we can do that here or at
the gsl-discuss list mailto:gsl-discuss@sources.redhat.com . But there is also
the possibility of a mailinglist at pygsl.sourceforge.net . Please let me know.

WARNING: multiple messages have this Message-ID
From: Achim Gaedke <Achim.Gaedke@uni-koeln.de>
To: Jochen Küpper <jochen@jochen-kuepper.de>
Cc: numpy-discussion@lists.sourceforge.net,
	achimgaedke@users.sourceforge.net,
	gsl-discuss@sources.redhat.com
Subject: Re: Numpy2 and GSL
Date: Tue, 27 Nov 2001 00:19:00 -0000	[thread overview]
Message-ID: <3C034BFA.FBB64E94@uni-koeln.de> (raw)
Message-ID: <20011127001900.NRck15qDcQVrpMXO63NPr0crBM0nSA0uikbazsyZaGk@z> (raw)
In-Reply-To: <m3herhuk76.fsf@box.home.de>

Ok, there is a clear need for the facility of easy contribution.
Please be patient until Friday, December 7th. Then I have time to let it happen.

It is right that the oficial site for this project is at pygsl.sourcefogrge.net
(Brian Gough, can you change the link on the gsl homepage, thanks :-) )

But I will show some discussion points that must be clear before a cvs release:

- Is the file and directory structure fully expandable, can several persons work
parallel?

- Should classes be created with excellent working objects or should it be a 1:1
wrapper?

- should there be one interface dynamic library or more than one?

- Is there an other way expect that of the GPL (personally prefered, but other
opinions should be discussed before the contribution of source)

Some questions of minor weight:

- Is the tuple return value for (value,error) ok in the sf module?

- Test cases are needed

These questions are the reason, why I do not simply "copy" my code into cvs.

Jochen Küpper wrote:
> 
> It only provides wrapper for the special functions, but more is to
> come. (Hopefully Achim will put the cvs on sf soon.)
> 
> Yes, I agree, PyGSL should be fully integrated with Numpy2, but it
> should probably also remain a separate project -- as Numpy should stay
> a base layer for all kind of numerical stuff and hopefully make it
> into core python at some point (my personal wish, no more, AFAICT!).
> 
> I think when PyGSL will fully go to SF (or anything similar) more
> people would start contributing and we should have a fine general
> numerical algorithms library for python soon!
> 

I agree with Jochen and I'd like to move to the core of Python too. But this is
far away and I hate monolithic distributions.

If there is the need to discuss seperately about PyGSL we can do that here or at
the gsl-discuss list mailto:gsl-discuss@sources.redhat.com . But there is also
the possibility of a mailinglist at pygsl.sourceforge.net . Please let me know.

       reply	other threads:[~2001-11-27  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E166tnq-0001g8-00@usw-sf-list1.sourceforge.net>
     [not found] ` <m3herhuk76.fsf@box.home.de>
2001-12-19 13:20   ` Achim Gaedke [this message]
2001-11-18 13:11     ` Achim Gaedke
2001-11-27  0:19     ` Achim Gaedke
2001-12-19 13:20     ` Achim Gaedke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C034BFA.FBB64E94@uni-koeln.de \
    --to=achim.gaedke@uni-koeln.de \
    --cc=achimgaedke@users.sourceforge.net \
    --cc=gsl-discuss@sources.redhat.com \
    --cc=jochen@jochen-kuepper.de \
    --cc=numpy-discussion@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).