| 1 |
On 04:03 Tue 08 Jul , Andrey Grozin wrote: |
| 2 |
> On Mon, 7 Jul 2008, Donnie Berkholz wrote: |
| 3 |
>> I actually object to having crap in dev-python, because things should be |
| 4 |
>> categorized functionally instead of by the language they're implemented |
| 5 |
>> in. 90% of the time you don't care about the language. But category |
| 6 |
>> moves are pretty much pointless, so I don't normally bring it up. |
| 7 |
> Then this particular case belongs to the other 10% :-) |
| 8 |
> It is not really important for a user if a library is written in C or |
| 9 |
> fortran, because he can call it from his own programs written in any |
| 10 |
> language. But python modules are only useful for somebody who is going to |
| 11 |
> write his own python code and import them. |
| 12 |
|
| 13 |
Right, sure. Here's the way I see it: chances are that someone realizes |
| 14 |
they want to write a scientific application, and then look to see what |
| 15 |
libraries are available to write it with, instead of deciding they want |
| 16 |
to write some sort of library for an unknown purpose using Python and |
| 17 |
then say, "Hey, I think I'll do something scientific." |
| 18 |
|
| 19 |
> sci-libs/scipi and dev-python/scientificpython are two competing projects |
| 20 |
> which have practically identical aims and descriptions. Do you think this |
| 21 |
> is logical? |
| 22 |
|
| 23 |
Logical? Not particularly. Does it matter, when considering the costs of |
| 24 |
moving packages in CVS and how search tools work? Not particularly. |
| 25 |
|
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Donnie |
| 29 |
|
| 30 |
Donnie Berkholz |
| 31 |
Developer, Gentoo Linux |
| 32 |
Blog: http://dberkholz.wordpress.com |
Archives