On Friday, May 13, 2016 at 1:45:52 PM UTC+2, Erik Bray wrote:
>
>
> http://arstechnica.com/information-technology/2016/04/why-microsoft-needed-to-make-windows-run-linux-software/
>
>
> My point is that it is not being supported, at least initially, for
> deployment either in servers or for end u
Hi,
I'm new to Sage too, but I faced this exact same error on a different file
recently. Basically, my understanding is that sometimes Sage is unable to
use a package that is installed on the local system and is not available
within its directory.
Check the following path (or equivalent) in yo
Another note, this is happening on my master branch as well, which is just
an uneditted version of sage 7.1. I try running the command:
./sage-t src/sage/interfaces/maxima_lib.py
and it tells me this:
saad@saad-ThinkPad-X201:~/sage$ ./sage -t src/sage/interfaces/maxima_lib.py
no stored timings
I believe that I pushed my branch to the trac server on here?
http://trac.sagemath.org/ticket/20595#comment:3
Or is that not the same as pushing my branch? Regardless, I've also put it
here under the develop branch(which I believe is the same as the branch
trac made for the ticket):
https://gith
I believe that I pushed my branch to the trac server on here?
http://trac.sagemath.org/ticket/20595#comment:3
Or is that not the same as pushing my branch? Regardless, I've also put it
here under the develop branch:
https://github.com/Babyll/sage/tree/develop
Thanks!
--
You received this messa
it might be the easiest to put your branch somewhere (on trac git server,
or github) so that it can be viewed and tested
On Friday, May 13, 2016 at 8:02:48 PM UTC+1, saad khalid wrote:
>
> Ohhh, I see. Thanks! Unfortunately, I'm still unable to run the doctests
> on the file. I'm getting the sam
Ohhh, I see. Thanks! Unfortunately, I'm still unable to run the doctests on
the file. I'm getting the same error as I mentioned above, and the error
doesn't seem to have anything to do with the file itself. Am I inputting
the command incorrectly?
--
You received this message because you are s
Right. In particular, if you have LaTeX code in your docstring, it should
start with r""". For example, if the docstring starts with """ instead of
r""", then '\to' will end up being converted to TAB (\t in a plain Python
string is a tab) followed by 'o'.
John
On Friday, May 13, 2016 at 11:
Google for python raw strings. The main difference is how they treat
backslashes.
On May 13, 2016 09:34, "saad khalid" wrote:
> Thanks for the help everyone. I've got it submitted here, hopefully I
> followed the procedure properly
>
> http://trac.sagemath.org/ticket/20595#comment:3
>
> Also, sor
When I try running the doctest, here is the error I am getting:
saad@saad-ThinkPad-X201:~/sage$ ./sage -t src/sage/interfaces/maxima_lib.py
no stored timings available
Running doctests with ID 2016-05-13-11-54-59-7d842524.
Git branch: t/20595/setting_besselexpand_to_true_globally
Using --optional=
On Friday, May 13, 2016 at 3:16:28 PM UTC+1, Martin R wrote:
>
> remove_constraint takes as input the index of the constraint to be
> removed! It is unlikely, that add_constraint(variable==0) creates an
> indexed constraint, but perhaps I am mistaken.
>
all the constraints are indexed, surely
Thanks for the help everyone. I've got it submitted here, hopefully I
followed the procedure properly
http://trac.sagemath.org/ticket/20595#comment:3
Also, sorry for this basic question but, when documenting a function, what
is the purpose of starting it with r""" ? Is this some python conventi
Thanks for the help everyone. I've got it submitted here, hopefully I
followed the procedure properly
http://trac.sagemath.org/ticket/20595#comment:3
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivi
remove_constraint takes as input the index of the constraint to be
removed! It is unlikely, that add_constraint(variable==0) creates an
indexed constraint, but perhaps I am mistaken.
Am Freitag, 13. Mai 2016 15:25:17 UTC+2 schrieb Dima Pasechnik:
>
> On Friday, May 13, 2016 at 9:53:13 AM UTC+1,
Dear sage-devel,
Sage Days 75, on coding theory in Sage and related tools will take place at
Inria Saclay (Greater Paris Area, Polytechnique campus), France on August
22-26, 2016.
We'll have introductions to Sage and tutorials in the mornings, and coding
sprints in the afternoons.
We plan to w
On Friday, May 13, 2016 at 9:53:13 AM UTC+1, Martin R wrote:
>
>
> Yes, and then? I don't think I can remove it again, can I?
>
>>
>> sage: p.remove_constraint?
>> Docstring:
>>Removes a constraint from self.
>>
>> I do not thing that this works, because a constraint may (and often will
> b
On Friday, May 13, 2016 at 8:54:43 AM UTC-4, kcrisman wrote:
>
> Yes, +1!
>
>
Though before that we should make the axes appear in the correct location
always and so forth:
http://trac.sagemath.org/ticket/3862
http://trac.sagemath.org/ticket/5229
http://trac.sagemath.org/ticket/9653
http://trac
Yes, +1!
On Wednesday, May 11, 2016 at 4:02:30 AM UTC-4, Eric Gourgoulhon wrote:
>
> It will be great to have axes labels on 3d plots !
> Good luck for your ticket !
>
> Eric.
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe fro
On Tuesday, May 10, 2016 at 4:31:42 PM UTC-4, Nathan Dunfield wrote:
>
> We don't have a buildbot on old OSX machines.
>>
>
> One possible idea: VirtualBox supports running OS X clients on OS X hosts,
> and the OS X versions don't have to match. I know someone who has VB VM's
> of every relea
On Wed, May 11, 2016 at 8:46 AM, Dima Pasechnik wrote:
>
>
> On Wednesday, May 11, 2016 at 7:12:59 AM UTC+1, Rob Beezer wrote:
>>
>> Dear Brian,
>>
>> Appears it is some flavor of Ubuntu Linux running within Windows?
>>
>>
>> https://blogs.windows.com/buildingapps/2016/03/30/run-bash-on-ubuntu-on-
Yes, and then? I don't think I can remove it again, can I?
>
> sage: p.remove_constraint?
> Docstring:
>Removes a constraint from self.
>
> I do not thing that this works, because a constraint may (and often will
be) subsumed by other constraints already there.
--
You received this mes
On Thursday, May 12, 2016 at 12:44:31 PM UTC+2, Johan S. R. Nielsen wrote:
>
> A related warning is that of @experimental. It seems that if one uses
> @experimental in the __init__ of a class, then a FutureWarning message
> is issued every time an element of that class is constructed. Needless
>
On Thursday, May 12, 2016 at 6:17:33 PM UTC+1, Martin R wrote:
>
>
> So, what is the proper way to do it? As I wrote, it's not really an
>>> option to solve the whole problem for each new constraint...
>>>
>>
>> add a constraint, and solve again?
>>
>> Yes, and then? I don't think I can remove
23 matches
Mail list logo
