Hi, I posted a problem on ask.sagemath.org a few weeks ago,
https://ask.sagemath.org/question/35698/parallel-interface-to-the-sage-interpreter-20/
but didn't get any reply. I believe I thoroughly documented a potential bug
in psage.py but my python knowledge for system programming is limited an
Dear all,
I have posted this issue on sage-support
(https://groups.google.com/forum/#!topic/sage-support/JIkynCX-N74), but I
post it here again.
I am trying to build Sage 7.5.beta6 inside Docker. Here is the Docker file
(https://gist.github.com/stakemori/2008d4f3480c4c2334ac7133c4f7f0f7).
I c
It works for me too!
On Thursday, 15 December 2016 07:40:11 UTC+1, GK wrote:
>
> Hi again, thanks to the insight. I managed to successfully run sage in
> WSL. notebook(automatic_login='False') triggered indeed a different
> reaction, but again did not work. The trick was to run bash on ubuntu on
It was a typo for "SOS" :-). But it could as well have been "SOA".
--
Emmanuel Charpentier
Le 15 déc. 2016 16:46, "Dima Pasechnik" a écrit :
>
>
> On Thursday, December 15, 2016 at 2:27:33 PM UTC, Samuel Lelievre wrote:
>>
>>
>>
>> Emmanuel Charpentier:
>>
>> the solution was an SOT to the rel
On Thursday, December 15, 2016 at 2:27:33 PM UTC, Samuel Lelievre wrote:
>
>
>
> Emmanuel Charpentier:
>
> the solution was an SOT to the relevant R package author,
>>
>
> For the acronym-unexperts here, could you spell out SOT in full?
>
it could be Same Old Thing, or Sex On Text, or 30+ other
People in this thread might want to note the
ticket https://trac.sagemath.org/ticket/21024
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@
Emmanuel Charpentier:
the solution was an SOT to the relevant R package author,
>
For the acronym-unexperts here, could you spell out SOT in full?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivin
Hi all,
We are seeking applicants for a two and a half year mathematical software
developer/researcher position here in Kaiserslautern, to start as soon as
possible, and certainly by March 1st 2017. This position is funded by the
European Union H2020 OpenDreamKit project.
The successful applicant
Jeroen Demeyer wrote:
> I would prefer to treat these as any other non-Element. I see no
> reason for the special case.
It would catch cases like QQ(1) != ZZ or (going back to the case of
general rich comparison) float(1) < RIF(pi) where Python2 would compare
by type otherwise.
--
Marc
--
Yo
On 2016-12-15 10:58, Marc Mezzarobba wrote:
- (b), i.e. fail, when y is a SageObject or can be converted using
py_scalar_to_element(),
I would prefer to treat these as any other non-Element. I see no reason
for the special case.
--
You received this message because you are subscribed to t
On Wed, Dec 14, 2016 at 9:10 PM, Peter Luschny wrote:
>> I replaced the existing binary with a new one at
>
> BRAVO!
> All works fine.
Great!
> (only plot() gives no output)
That's strange... I thought I fixed that, and it works for me.
All it's doing to determine the image viewer is passing t
Marc Mezzarobba wrote:
> Jeroen Demeyer wrote:
>> Don't forget the option
>>
>> (c) return NotImplemented
>>
>> I would say:
>>
>> Case (i): (b)
>> Case (ii): (c)
>
> Yes, I kept that out because my current patches don't change that part
> of the logic, but I think I agree.
What about making a fi
Marc Mezzarobba wrote:
> I had to touch corners of Sage I'm far for comfortable with; if people
> more familiar with them can have a look at the changes and perhaps
> help with cleaner fixes, that would be more than welcome!
In particular, Nathann sent me a private e-mail to complain that my
patc
Honnêtement je suis content de plus être dev, parce qu'un ticket comme ca
m'aurait re-garanti une engueulade.
Ce que tu fais dans le dossier graphe est complètement irresponsable. Tu es
en train de ralentir le cas d'usage le plus classique pour ne rien pouvoir
garantir de mieux sur le cas génér
Jeroen Demeyer wrote:
> Don't forget the option
>
> (c) return NotImplemented
>
> I would say:
>
> Case (i): (b)
> Case (ii): (c)
Yes, I kept that out because my current patches don't change that part
of the logic, but I think I agree.
--
Marc
--
You received this message because you are s
On 2016-12-15 10:23, Marc Mezzarobba wrote:
Travis Scrimshaw wrote:
We need to be very careful about defining "not knowing". I (stongly)
believe when the objects/types are incomparable (say the rings ZZ and
QQ), then == should return False and != should return True.
Subsequently, when there is n
Travis Scrimshaw wrote:
> We need to be very careful about defining "not knowing". I (stongly)
> believe when the objects/types are incomparable (say the rings ZZ and
> QQ), then == should return False and != should return True.
> Subsequently, when there is no coercion between the parents, they
>
17 matches
Mail list logo
