1) It seems that http://trac.sagemath.org/sage_trac/report/34 , i.e.
"Active tickets I participated in", does not anymore show ticket I have
been CC'd to. Should it? It did before.
Also real un-CC would be nice. I may comment a ticket about just a typo or
something, but would not want to recei
In one computer with newest beta I computed 1+2 in SageNB and got
Python 2.7.10 (default, Jul 19 2016, 10:26:31)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
import os;os.chdir("/tmp/tmpAWi_n0");
execfile("_sage_input_1.py")
START1
impo
Hi Justin,
Thank you for your answer! There was indeed a problem with my java
installation, which I now fixed
and it works now from within Sage!
Best wishes,
Anne
On Monday, August 15, 2016 at 7:04:42 PM UTC-7, Justin C. Walker wrote:
>
>
> On Aug 15, 2016, at 14:36 , Anne Schilling wrote:
>
>
> If a Sage developer builds module B on an @experimental module A, it
> puts no further burden on a developer who wants to later modify A: s/he
> will in either case need to fix B. @experimental modules are often
> introduced, as is the case in #13215, by developers who wish to use it
> th
On Aug 15, 2016, at 14:36 , Anne Schilling wrote:
> Hi!
>
> I get the following bug with
> sage: version()
> 'SageMath version 7.3, Release Date: 2016-08-04'
>
> Any idea what the problem might be? I installed jmol with sage -f jmol
> and do have java installed.
[snip]
> sage: RootSystem(['A',3
There is a new FriCAS interface almost ready for review
at https://trac.sagemath.org/ticket/21231. Comments and help very welcome.
I would especially like to encourage those who use FriCAS in their real
life to tell me at the ticket which bits they use, so I can make sure the
translation from
Hi!
I get the following bug with
sage: version()
'SageMath version 7.3, Release Date: 2016-08-04'
Any idea what the problem might be? I installed jmol with sage -f jmol
and do have java installed.
Thank you!
Anne
sage: RootSystem(['A',3]).ambient_space().plot()
---
On Mon, Aug 15, 2016 at 10:09 AM, Jeroen Demeyer wrote:
> On 2016-08-15 20:25, William Stein wrote:
>>
>> It would be more standard to have an
>> explicit library import, which -- on import -- would print out
>> something about it being experimental and unstable.
>
>
> Whether it's a separate lib
> On Aug 14, 2016, at 21:16 , leif wrote:
>
> Justin C. Walker wrote:
>>
>>> On Aug 14, 2016, at 14:06 , Volker Braun wrote:
>>>
>>> You need the newest git-trac version, presumably you checked out the repo
>>> somewhere. Find it and run "git pull (in the git-trac repo folder)
>>
>> Thanks
On 2016-08-15 20:25, William Stein wrote:
It would be more standard to have an
explicit library import, which -- on import -- would print out
something about it being experimental and unstable.
Whether it's a separate library or part of Sage doesn't really matter
for this discussion. So I rea
> Correct me if I'm wrong, but it then seems to me that you generally
> agree that it makes sense to accept a module into Sage which is somehow
> marked as (temporarily) unstable?
>
Yes, it does address a very real issue. However I differ now in my opinion
about how best to implement this...
> That thread doesn't mention @experimental or decorators explicitly.
Well, you're replying to Daniel Krenn's comment: he points at a public
branch, explicitly mentioning that it introduces
sage.misc.superseded.experimental which "acts like a deprecation, but
giving a FutureWarning stating that th
On Mon, Aug 15, 2016 at 8:14 AM, Johan S. H. Rosenkilde
wrote:
>> Regarding this whole @experimental discussion (I never heard of
>> @experimental until just now), it seems like yet another case of
>> trying to use some awkward mechanism to get around ignorance of Python
>> packaging and modules.
> Regarding this whole @experimental discussion (I never heard of
> @experimental until just now), it seems like yet another case of
> trying to use some awkward mechanism to get around ignorance of Python
> packaging and modules. Python has this amazing thing called
> "Python libraries" and a
On Mon, Aug 15, 2016 at 5:43 AM, leif wrote:
> What Sage IMHO really lacks is a true development (vs. stable) branch,
> along with different releases (for "developers" as opposed to "ordinary"
> users),[...]
This is mostly due to lack of people resources relative to the number
of people and size
Johan S. H. Rosenkilde wrote:
>> leif wrote:
>> Well, depends on /what/ you write there...
>>
>> At least mentioning the different notions of skew polynomial evaluation
>> (and that currently only one, and which, is implemented) shouldn't hurt.
>>
>> And you could clearly state what aspects of the
> leif wrote:
> Well, depends on /what/ you write there...
>
> At least mentioning the different notions of skew polynomial evaluation
> (and that currently only one, and which, is implemented) shouldn't hurt.
>
> And you could clearly state what aspects of the interface are probably
> subject to c
Eric Gourgoulhon wrote:
>
> Le dimanche 14 août 2016 18:28:04 UTC+2, Frédéric Chapoton a écrit :
>
> Happy to hear that you care about the patchbot. Maintenance is
> currently being done (slowly). It will hopefully be resurrected soon.
>
>
> Thanks! As many people, I appreciate very muc
Le dimanche 14 août 2016 18:28:04 UTC+2, Frédéric Chapoton a écrit :
>
> Happy to hear that you care about the patchbot. Maintenance is currently
> being done (slowly). It will hopefully be resurrected soon.
>
Thanks! As many people, I appreciate very much the patchbot reports on trac
tickets.
Well, certainly imports could also be a problem. Is there any possibility
that cython does not require absolute imports ? I have heard the cython can
accept both py2 and py3 syntax. Where can I find documentation ?
I tried to compile sage in Py3 by commenting out all the bad
"cmp(something)" in
On 2016-08-14 14:41, Frédéric Chapoton wrote:
As an intermediate step in our long way to python3, I would like to be
able to compile all the .pyx files in py3.
Except for #21246 (please review)
What about imports? Are all imports in Cython files converted to proper
absolute/relative imports w
21 matches
Mail list logo
