>> sage-ultralight must have the same name as sage. Then you get into >> copyright/trademark related issues (the name "sage" is already taken). >> Just the same I could create a GUI toolkit named "Qt" that was also >> released under the SACL license, but you can guess what would happen. > > Incorrect. Python doesn't care what you call your program, it only > cares about the filename.
Huh? Your example had two files or modules: foo.py ==== from sage import Integer print Integer(2)+Integer(2) sage.py ====== # Your ultralight-sage implementation with... # Whatever your implementation of Integer was Python doesn't care about the name "foo.py." But Python does care that about the name "sage", otherwise the import of sage in foo.py won't work. To get "from sage import Integer" to work, you *have to* name sage.py,....well, sage.py. But as I recall there is already a "sage" python project somewhere ;-). I think the authors of the real sage project might have a problem with you naming your ultralight sage module "sage.py." Just like Fernando and myself would have a problem if another "IPython" named project came along. > If somebody wants to go to court about a > filename... that'll certainly be interesting. This is called trademark infringement, and it happens all the time. Remember Apple v. Apple? http://en.wikipedia.org/wiki/Apple_Corps_v._Apple_Computer Cheers, Brian > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
