On 04/17/09 15:05, mabshoff wrote: > On Apr 17, 2:25 am, Prabhu Ramachandran <pra...@aero.iitb.ac.in> > wrote: >> On 04/17/09 13:37, mabshoff wrote: >> >>> If your plan is still to recreate all scripts to be BSD the above >>> would be more or less pointless, so you need to let us know what you >>> want to do. I really don't want to relicense my code in $SAGE_LOCAL/ >>> bin/sage-$FOO to BSD since the EPD for example has fixes to various >>> python packages that have not been fed back to the community and I >> Just curious, I'm not from Enthought and don't speak for them but do >> know they are trying to push back what they can. So can you elaborate or >> point me to something that has more substantial information?\ > > I think there was something on the scipy or numpy list about this > early this or late last week. It was about setuptools IIRC and might > have been part about the discussion about numpy eggs. It wasn't very > specific and I could be completely wrong. I will try to find out > exactly what was written and report back once I get things I need to > fix today done. If I am wrong I am sorry to have stated the above.
BTW, I wrote to Dave Peterson at Enthought and he replied that "as far as I know, every fix we've put in to the upstream code has been sent upstream as well". So if there is something that wasn't sent, it was accidental. If there is an issue I think you ought to write to them. cheers, prabhu --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
