I agree that you don't have to modify module_list.py (which probably should
be replaced at one point by something that doesn't rely on a single file
having information about all modules, but I digress). Emil mentioned in his
OP that he is editing modules_list for some reason.
On Monday,
Thanks for everyone's help. I decided to make it a package that can be
installed like:
sage -python setup.py install
My setup.py is as follows (except I changed the name of the package).
I arrived at its contents by trial and error, so if anyone could have
a quick look at it to see if there is
On Monday, April 2, 2012 8:32:18 AM UTC-7, Emil wrote:
Thanks for everyone's help. I decided to make it a package that can be
installed like:
sage -python setup.py install
My setup.py is as follows (except I changed the name of the package).
I arrived at its contents by trial and error,
Thanks! Actually, I have a little problem. In setup.py I have:
Extension('thing',
sources=['mypackage/thing.pyx'],
include_dirs = [SAGE_LOCAL +
'/lib/python/site-packages/numpy/core/include',
On Saturday, March 31, 2012 11:42:08 PM UTC+1, Emil wrote:
not pollute the name space (It contains classes with quite generic
names like Problem and Construction.)
Whats wrong with the module foo having a foo.Problem class?
How is your spkg going to add cython modules to module_list.py?
On Sat, Mar 31, 2012 at 3:42 PM, Emil emi...@gmail.com wrote:
On 31 March 2012 12:47, Volker Braun vbraun.n...@gmail.com wrote:
If it is of interest to an academic community then it probably should be
part of Sage ;-)
I'm not against it being incorporated into Sage at some point, but
right
Volker Braun vbraun.n...@gmail.com writes:
How is your spkg going to add cython modules to module_list.py? You can
monkey-patch it in the spkg-install script but thats just a bad idea. For
starters, it is definitely going to break down the road.
Correct me if I'm wrong, but random
On Apr 1, 2012 7:18 PM, Keshav Kini keshav.k...@gmail.com wrote:
Volker Braun vbraun.n...@gmail.com writes:
How is your spkg going to add cython modules to module_list.py? You can
monkey-patch it in the spkg-install script but thats just a bad idea.
For
starters, it is definitely going to
If it is of interest to an academic community then it probably should be
part of Sage ;-)
On Friday, March 30, 2012 11:04:00 PM UTC+1, Emil wrote:
3) probably shouldn't be made part of everyone's Sage, but it would be
good if people could install it easily, as it will be of interest to a
On 31 March 2012 12:47, Volker Braun vbraun.n...@gmail.com wrote:
If it is of interest to an academic community then it probably should be
part of Sage ;-)
I'm not against it being incorporated into Sage at some point, but
right now I'd rather keep it as a separate package that people can
I think you should make it an spkg because that is how people using sage expect
to install it.
Note that the install script in an spkg can contain arbitrary bash code so it
can do everything you want it to.
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe
On 2012-03-31, Emil emi...@gmail.com wrote:
On 31 March 2012 12:47, Volker Braun vbraun.n...@gmail.com wrote:
If it is of interest to an academic community then it probably should be
part of Sage ;-)
I'm not against it being incorporated into Sage at some point, but
right now I'd rather keep
I don't know if this below is a standard way but it works to develop stand
alone packages:
At sage package directory, for example,
/opt/sage-some-version/local/lib/python2.6/site-packages/
execute
ln -s /home/user1/newpackage/
where newpackage is a directory with all files
On Friday, March 30, 2012 10:14:15 AM UTC-7, Emil wrote:
Hi, I'm working on a Sage package. I'm new to Sage, and learning as I
go along...
My source code is a mixture of .py and .spyx files, that (until now) I
have been attaching() at the sage: prompt. This seems to work quite
well.
Pedro, John - thanks for your replies! It is a shame that you can't
recompile bits of Sage from within Sage, but I guess there are good
reasons for this.
My package has the following characteristics:
1) it uses lots of Sage things
2) it is a mixture of Cython and Python
3) probably shouldn't be
15 matches
Mail list logo
