Re: [sage-devel] Re: Importing sage.libs.gap.assigned_names take a very long time

On Fri, Sep 16, 2016 at 10:55 PM, Volker Braun wrote: > For tab completion and so on we want a list of "useful" GAP functions, > excluding internal functions that are not meant for end users. > Unfortunately, there isn't really a good way to get that from GAP. The best >

[sage-devel] Re: Importing sage.libs.gap.assigned_names take a very long time

For tab completion and so on we want a list of "useful" GAP functions, excluding internal functions that are not meant for end users. Unfortunately, there isn't really a good way to get that from GAP. The best approach seems to be to look for the actually documented functions. Downside is that

[sage-devel] Re: Importing patches fails after calling dev.git.am()

Thank you Simon - that did the trick. :-) Am Dienstag, 20. Mai 2014 21:22:13 UTC+2 schrieb Simon King: Hi! On 2014-05-20, Jan Keitel jocalare...@gmail.com javascript: wrote: git: 'am' is not a git command. See 'git --help'. Did you mean one of these? br ci co lg st

[sage-devel] Re: Importing patches fails after calling dev.git.am()

A perhaps easier workaround would be to delete SAGE_LOCAL/bin/git and rely on the system git. On Tuesday, May 20, 2014 8:22:13 PM UTC+1, Simon King wrote: Hi! On 2014-05-20, Jan Keitel jocalare...@gmail.com javascript: wrote: git: 'am' is not a git command. See 'git --help'. Did you

[sage-devel] Re: Importing patches fails after calling dev.git.am()

Hi! On 2014-05-20, Jan Keitel jocalareanetw...@gmail.com wrote: git: 'am' is not a git command. See 'git --help'. Did you mean one of these? br ci co lg st stat Recently I had a similar problem, namely Sage's git (i.e. git in a Sage shell) claiming that pull is not a git

[sage-devel] Re: importing

Some things i would like to have: Orlik-Solomon Algebras Module of logarithmic derivations (and specially, a way to check if it is free). Or at least, its Betti numbers. Maybe arrangements in projective spaces? For the case of line arrangements, wiring diagrams, and fundamental group. -- You

[sage-devel] Re: importing

On Sunday, July 21, 2013 8:35:24 PM UTC-4, davidp wrote: At the moment, I just have Hyperplane as a class deriving from AffineSpace (my version of AffineSpace, that is, which I will change, as noted above), and HyperplaneArrangement deriving from object. Can you spell out your idea a bit

[sage-devel] Re: importing

If the class is just used internally to keep track of intersections of hyperplanes then it doesn't really matter what it is called since it will not be in the global namespace. In fact, you probably only need HyperplaneArrangement constructor and the hyperplane_arrangements factory in the

[sage-devel] Re: importing

On Monday, July 22, 2013 6:58:11 AM UTC-7, Volker Braun wrote: On Sunday, July 21, 2013 8:35:24 PM UTC-4, davidp wrote: At the moment, I just have Hyperplane as a class deriving from AffineSpace (my version of AffineSpace, that is, which I will change, as noted above), and

[sage-devel] Re: importing

center is not a function but a method of Polyhedron_base. I suggest you read up on object-oriented programming and Python if that that doesn't answer your question. I'm definitely interested in hyperplane arrangements, though. Do you have a particular data structure in mind or is your plan to

[sage-devel] Re: importing

I have created three classes: AffineSpace, Hyperplane (inheriting from AffineSpace), and HyperplaneArrangement. The methods in HyperplaneArrangement that I have defined so far are (where 'a', below, is a hyperplane arrangement): a.ambient_space a.num_bounded_regions

[sage-devel] Re: importing

Figured out my problem. I was defining a method for my HyperplaneArrangement class but forgot to include 'self' as an argument. Duh. Dave On Sunday, July 21, 2013 12:58:24 PM UTC-7, davidp wrote: I am working on a Sage package for hyperplane arrangements. In my file

[sage-devel] Re: importing

On Sunday, July 21, 2013 5:14:21 PM UTC-7, Volker Braun wrote: There is already an affine space class (as affine scheme). Whats wrong with using that as ambient space? Thanks for pointing that out. I had chosen AffSpace for the name of the class I need initially because the name

[sage-devel] Re: importing

There is already an affine space class (as affine scheme). Whats wrong with using that as ambient space? sage: AffineSpace(2,QQ) Affine Space of dimension 2 over Rational Field Whats your plan with parent/element relations? It seems Hyperplane should be an element with HyperplaneArrangement

[sage-devel] Re: importing matlab files (.mat) into sage?

Hi Stan, On 2 Nov., 11:02, Stan Schymanski schym...@gmail.com wrote: While looking for a way to import a matlab file into sage, I stumbled over scipy.io.loadmat and found a ticket where this is implemented into sage along with some other useful input/output

[sage-devel] Re: importing matlab files (.mat) into sage?

Hi Simon and Thierry, Thanks for your comments. Yes, I thought that the ticket would need some more work and I guess the incentive is not so high as long as there are quite comfortable ways to do these things by hand as pointed out by Thierry. I just thought that this might be a good one for a

[sage-devel] Re: Importing units into module

Oh, thanks, that helps. I guess I'll have to restructure the code. On Jul 21, 2:06 am, Burcin Erocal bur...@erocal.org wrote: Hi, On Thu, 21 Jul 2011 00:42:38 -0700 (PDT) Eviatar eviatarb...@gmail.com wrote: I am working on a physical constants module, but for whatever reason I

[sage-devel] Re: Importing units into module

I can't see how to solve this. I import units, which import sage_eval, which imports symbolic, which imports physical_constants; thus the circular import. How can this be solved? The only way I can see is to merge the units and physical_constants files, but they don't exactly go together. On

Re: [sage-devel] Re: Importing units into module

One solution to circular imports is to do one of the imports inside a function, rather than at the top level. David On Thu, Jul 21, 2011 at 17:36, Eviatar eviatarb...@gmail.com wrote: I can't see how to solve this. I import units, which import sage_eval, which imports symbolic, which imports

[sage-devel] Re: Importing units into module

Thanks I figured I would have to do that, but it's too complicated in this case. I'll just merge with the units module. On Jul 21, 5:52 pm, David Roe r...@math.harvard.edu wrote: One solution to circular imports is to do one of the imports inside a function, rather than at the top level. David

Re: [sage-devel] Re: Importing C functions though a 1-line command

On Sun, Feb 13, 2011 at 7:11 AM, Nathann Cohen nathann.co...@gmail.com wrote: What about the cython() function? The next version of Sage will get Cython's new inline function, so you can do stuff like {{{ a = math.pi cython.inline( cdef extern from math.h: double sin(double) print sin(a) )

[sage-devel] Re: Importing C functions though a 1-line command

On Sunday, February 13, 2011 9:27:29 AM UTC, Nathann Cohen wrote: I was wondering whether we already had (of if it would be interesting to define) some nice alias to use Cython through Sage. I was wishing for a one-liner to import a method defined in a .c file or in a library.. What about

Re: [sage-devel] Re: Importing C functions though a 1-line command

What about the cython() function? Isn't it only useful to import Cython code? I would like to import a .c file the same way :-) Nathann -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to

[sage-devel] re-importing numpy leaks ~1kb each time

Hello folks, to optimize startup time we did move numpy imports down into individual Cython files. Unfortunately every time we do so we end up leaking anywhere from 700 to 900 bytes or so. Since that import can be in frequently visited operations I would strongly suggest we limit ourselves to

[sage-devel] Re: importing non-sage modules in doctests

On Aug 30, 2008, at 3:33 PM, David Ketcheson wrote: I'm developing a package and trying to use sage -t to automatically test examples I've put in the docstrings. On the documentation page at http://www.sagemath.org/doc/prog/node29.html it says I can do something like EXAMPLES:

[sage-devel] Re: importing non-sage modules in doctests

Sorry for not being clear. myfoo.py is the file with the docstring examples I want to test. foo.py is the file with the modules I need to import. Let me add that sometimes they're the same file, and it doesn't work in that case either. On Aug 30, 8:08 pm, Robert Bradshaw [EMAIL PROTECTED]

[sage-devel] Re: importing non-sage modules in doctests

Apparently the problem here (what I should have thought of first) is that the directory containing foo.py is not in my sage python path. The surprising (to me) part, and the reason I didn't think of it, is that this breaks things even if the file I'm testing is foo.py and I try 'from foo import

[sage-devel] Re: importing non-sage modules in doctests

Sounds good. However, I don't think that modifying sage-env, as the trac ticket suggests, will fix things for the issue I'm discussing here. I changed the appropriate line of sage-env to PYTHONPATH=$SAGE_PATH:$SAGE_ROOT/local/lib/python:$SAGE_PYTHONPATH export PYTHONPATH which works, meaning