On Thu, 25 May 2017, Travis Scrimshaw wrote:
I sometimes get notifications when a ticket has been closed, but
typically I do not. I think I have to be in cc on the ticket, but even
then, I am not sure. I did like seeing when tickets were closed.
I got a notification from ticket that are close
How many developer does something to highlight **in a particular
release**?
As an example, I could put something like this for 8.0:
- Finite lattices now have function to compute congruence, and several
congruence-related functions like quotient lattice, lattice of congruences
and checks if a
On Thursday, May 25, 2017 at 6:40:18 PM UTC-7, François wrote:
>
> I am a bit surprised you can do that. I have just sent a PR to pynac
> a couple of days ago to have it build with python3.
> https://github.com/pynac/pynac/pull/248
> I have a feeling you still a python2 pynac.
>
> François
>
>
On Thursday, May 25, 2017 at 10:46:22 PM UTC+2, Sébastien Labbé wrote:
>
> For some time, Minh was writing highlighted release notes. Here is the
> last one I found of him (already 8 years ago):
>
> https://mvngu.wordpress.com/2009/08/22/sage-4-1-1-released/
>
>
Wow, that is a great historic exa
I am a bit surprised you can do that. I have just sent a PR to pynac
a couple of days ago to have it build with python3.
https://github.com/pynac/pynac/pull/248
I have a feeling you still a python2 pynac.
François
> On 25/05/2017, at 20:49, Frédéric Chapoton wrote:
>
> ok, now with 8.0.b8, you
On Thursday, May 25, 2017 at 5:07:22 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Thursday, May 25, 2017 at 4:40:01 PM UTC-7, Nils Bruin wrote:
>>
>> incidentally, it would be nice if we could equiv local/bin/ipython with
>> the proper sage-python23 as well. Having a functional shell with an
>> in
On Thursday, May 25, 2017 at 4:36:49 PM UTC-7, Nils Bruin wrote:
>
>
> TypeError: __str__ returned non-string (type bytes)
>
> which happens in the Parent stuff for "rings/infinity.py" somewhere. The
> problem is clear: we end up with some byte string from what should be a
> "str". I don't know
On Thursday, May 25, 2017 at 4:40:01 PM UTC-7, Nils Bruin wrote:
>
> incidentally, it would be nice if we could equiv local/bin/ipython with
> the proper sage-python23 as well. Having a functional shell with an
> interactive debugger is a much nicer way to debug "import sage.all".
>
This is a
incidentally, it would be nice if we could equiv local/bin/ipython with the
proper sage-python23 as well. Having a functional shell with an interactive
debugger is a much nicer way to debug "import sage.all".
--
You received this message because you are subscribed to the Google Groups
"sage-de
Thank you! I can confirm that, after a distclean, building your branch with
`SAGE_PYTHON3=yes` gets me to the same point as you describe. The first few
issues are fairly simple. I've pushed some coarse fixes for them to
trac u/nbruin/py3_compat
(based on your ugly_python3). I consider these mor
>
>
> I've checked my trac preferences and I have "Notify" for all events
> available. Although I cannot see *"Notify: Any ticket changes" *which is
> mentioned in the text around settings. I do not get notifications about
> closed tickets like this one https://trac.sagemath.org/ticket/21066 (I
and some people helped him:
"Rob Beezer, Nathann Cohen, John Cremona, Simon King, Sébastien Labbé, and
Jens Rasch contributed to writing this release tour."
On Thursday, May 25, 2017 at 10:46:22 PM UTC+2, Sébastien Labbé wrote:
>
> For some time, Minh was writing highlighted release notes. Here
For some time, Minh was writing highlighted release notes. Here is the last
one I found of him (already 8 years ago):
https://mvngu.wordpress.com/2009/08/22/sage-4-1-1-released/
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe fro
I have made a git branch (public/ugly_python3) with the ad-hoc
changes..With this, one meets as wanted (this is my aim) a first real
problem in sage-code (namely unicode in sageinspect for the moment).
Frederic
Le jeudi 25 mai 2017 17:37:10 UTC+2, Frédéric Chapoton a écrit :
>
> Hello,
>
> I wo
On Thursday, May 25, 2017 at 10:08:21 AM UTC-7, Kwankyu Lee wrote:
>
> The successful launch with my built of sage with python3 seems well
> explained by John.
>
> On Thursday, May 25, 2017 at 5:37:10 PM UTC+2, Frédéric Chapoton wrote
>>
>> The road towards a full python3 sage is still quite lon
The successful launch with my built of sage with python3 seems well
explained by John.
On Thursday, May 25, 2017 at 5:37:10 PM UTC+2, Frédéric Chapoton wrote
>
> The road towards a full python3 sage is still quite long, and my
> motivation gets weaker, as it seems that not so many people care ab
Hello,
I've checked my trac preferences and I have "Notify" for all events
available. Although I cannot see *"Notify: Any ticket changes" *which is
mentioned in the text around settings. I do not get notifications about
closed tickets like this one https://trac.sagemath.org/ticket/21066 (I
thi
Hello,
I would like the design discussion to take place now, for sure. I would
like that we have a clean way to build and run sage with python3, so that
we can concentrate on fixing the many remaining issues inside sage code
itself, with a python3 build correctly in place. The road towards a fu
On Thursday, May 25, 2017 at 1:49:34 AM UTC-7, Frédéric Chapoton wrote:
>
> ok, now with 8.0.b8, you can just do
>
> "export SAGE_PYTHON3=yes"
>
> and then "make build". This should succeed, with no error message.
>
> Then try "./sage"
>
> This fails with some traceback about not finding sage.rep
ah, indeed, that's a possibility. I hope that I said loud enough not to
play with SAGE_PYTHON in the usual sage install...
Le jeudi 25 mai 2017 17:01:14 UTC+2, John H Palmieri a écrit :
>
>
>
> On Thursday, May 25, 2017 at 7:49:42 AM UTC-7, Kwankyu Lee wrote:
>>
>>
>>
>> On Thursday, May 25, 2017
On Thursday, May 25, 2017 at 7:49:42 AM UTC-7, Kwankyu Lee wrote:
>
>
>
> On Thursday, May 25, 2017 at 4:36:04 PM UTC+2, Frédéric Chapoton wrote:
>>
>> Very surprising that sage starts.. Did you really launch the sage that
>> you just compiled ?
>>
>
> I suspect this as well... I will respond la
On Thursday, May 25, 2017 at 4:36:04 PM UTC+2, Frédéric Chapoton wrote:
>
> Very surprising that sage starts.. Did you really launch the sage that you
> just compiled ?
>
I suspect this as well... I will respond later when I am sure about
everything. I am a bit busy for other things right now.
Very surprising that sage starts.. Did you really launch the sage that you
just compiled ?
I am using Linux, and do not know anything about macs, sorry. Did you check
that "echo $SAGE_PYTHON3" answered yes ?
Yes, another aspect of the same problem is this complete recompilation
every time. It
On Thursday, May 25, 2017 at 10:49:34 AM UTC+2, Frédéric Chapoton wrote:
>
> ok, now with 8.0.b8, you can just do
>
> "export SAGE_PYTHON3=yes"
>
> and then "make build". This should succeed, with no error message.
>
> Then try "./sage"
>
Following your instructions, I built sage on mac. Then sa
ok, now with 8.0.b8, you can just do
"export SAGE_PYTHON3=yes"
and then "make build". This should succeed, with no error message.
Then try "./sage"
This fails with some traceback about not finding sage.repl.interpreter.
Once again, can *please* someone help to fix that ?
Frederic
Le vendred
Hi,
The most powerful ever, a new beta, Sage 8.0.beta8, was just released. But
as always, it is rather dull to look through the "release note". It would
be good that there are "highlights" selected from the many ticket
descriptions.
An author of a ticket might want to advertise the ticket by a
I don't fully understand what you want to do, but please have a look at
src/sage/interacts
There, various interacts are defined which can be called by the user. It
works both in SageNB and Jupyter. I guess your package could do
something similar.
If you only care about Jupyter, there are other
27 matches
Mail list logo
