On 2019-01-28 06:18, Travis Scrimshaw wrote:
See possibly https://trac.sagemath.org/ticket/27114.
No, it's https://trac.sagemath.org/ticket/27109
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
See possibly https://trac.sagemath.org/ticket/27114.
On Monday, January 28, 2019 at 6:42:40 AM UTC+10, chris wuthrich wrote:
>
> Hello
> compiling from source for SageMath version 8.7.beta1 on my opensuse leap
> 15.0 caused an error after compiling libffi.
>
> It looks like the problem mentioned
Hi Jeroen,
On 2019-01-27, Jeroen Demeyer wrote:
> On 2019-01-27 22:36, Simon King wrote:
>> But do py3 experts agree that to transform os.path.join(...) to char*
>> (which is not in pickling but in module initialisation), I need
>> PyString_...?
>
> No! Please see src/sage/cpython/string.pyx
Tha
On 2019-01-27 22:36, Simon King wrote:
But do py3 experts agree that to transform os.path.join(...) to char*
(which is not in pickling but in module initialisation), I need
PyString_...?
No! Please see src/sage/cpython/string.pyx
(sorry no time now to answer more)
--
You received this message
PS:
On 2019-01-27, Simon King wrote:
> The funny thing is that 2 years ago, I was told by Jeroen:
> """
> For Python 3 compatibility, you should use bytes instead of str for
> pickling.
>
> This means changing the PyString_... functions to PyBytes_...
> """
To be fair, Jeroen talked abo
Hi,
On 2019-01-27, Simon King wrote:
> Is there a ticket for meataxe on python 3 already? I guess not. So,
> unless someone stops me in the next hour or so, I'll open one...
I created https://trac.sagemath.org/ticket/27152.
First problem: In py2,
PyBytes_AsString(os.path.join(DOT_SAGE,'meataxe'
Hello
compiling from source for SageMath version 8.7.beta1 on my opensuse leap
15.0 caused an error after compiling libffi.
It looks like the problem mentioned at the bottom of #25900.
It started as
[libffi-3.2.1]
[libffi-3.2.1] No record tha
Dear all,
using "git worktree", I now have both python 2 and python 3 versions of
Sage on my computer. Thank you!
Of course, I started to check packages that I care about --- and
immediately found a problem with the "meataxe" optional package.
When trying to create a matrix of type Matrix_gfpn_d
> Is there an apparent common reason for most of these failing tests? Such
> as code that makes assumptions on sorting (which, IIRC, is different in
> Python 2 and Python 3)?
>
Many many methods were relying on sorted list of vertices and edges. We
have done significant progresses to reduce
So this patchbot belongs to nobody ? Too bad. It will then go on forever
spitting polluting reports (not useless reports nevertheless).
Recall to patchbot breeders: you can either use --owner=DiCarpaccio on the
command line or {'owner':'ClintWestwood'} in the patchbot config file to
tell us who
random example, containing both #py2 and #py3 tags
Le dimanche 27 janvier 2019 19:24:08 UTC+1, John Cremona a écrit :
>
>
>
> On Sun, 27 Jan 2019 at 17:10, Frédéric Chapoton > wrote:
>
>> ok, then --optional=sage,py3 is ok (all doctests pass) whereas
>>
>> ./sage -t --optional=sage,py2 src/sage/m
On 2019-01-27 19:23, John Cremona wrote:
On Sun, 27 Jan 2019 at 17:10, Frédéric Chapoton mailto:fchapot...@gmail.com>> wrote:
ok, then --optional=sage,py3 is ok (all doctests pass) whereas
./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py
Is there a particular reason for th
On Sun, 27 Jan 2019 at 17:10, Frédéric Chapoton
wrote:
> ok, then --optional=sage,py3 is ok (all doctests pass) whereas
>
> ./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py
>
Is there a particular reason for this file being used as an example here?
I only say this as it was written by
Le 27/01/2019 à 18:12, Vincent Delecroix a écrit :
PS: without a decent "sage -t" I would not advice any developer
to switch to Python3 Sage...
https://trac.sagemath.org/ticket/27150
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscrib
But I don't understand
- why the py2 / py3 flag is not set correctly in --optional (it
should have been set by sage/doctest/control.py)
- what is this python2 appearing in --optional? where it is set?
Vincent
PS: without a decent "sage -t" I would not advice any developer
to switch to Pyt
ok, then --optional=sage,py3 is ok (all doctests pass) whereas
./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py
runs the py2 doctest and fail as expected
same thing for
./sage -t --optional=sage,py2,py3 src/sage/modular/cusps_nf.py
Le dimanche 27 janvier 2019 18:06:19 UTC+1, vdelecro
This should be
$ ./sage -t --optional=sage,py3 src/sage/modular/cusps_nf.py
ie don't forget "sage". Otherwise the doctest without # are
not run.
Le 27/01/2019 à 18:03, Frédéric Chapoton a écrit :
This clearly needs a cleanup. For example,
./sage -t --optional=py2 src/sage/modular/cusps_nf.py
This clearly needs a cleanup. For example,
./sage -t --optional=py2 src/sage/modular/cusps_nf.py
./sage -t --optional=py3 src/sage/modular/cusps_nf.py
have unexpected effects (when tested using python3)
Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit :
>
> Good question.
Good question. Needs to be checked
Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit :
>
> What about doctests marked # python2 / # python3?
>
> Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit :
> > Strange, but still this runs the correct python
> >
> > ./sage -t --long src/sage
What about doctests marked # python2 / # python3?
Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit :
Strange, but still this runs the correct python
./sage -t --long src/sage/categories/finite_posets.py # 15 doctests failed
F
Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit :
Strange, but still this runs the correct python
./sage -t --long src/sage/categories/finite_posets.py # 15 doctests failed
F
Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit :
>
> Hello,
>
> I wanted to run some doctests with my Python 3 Sage installation.
> However, running "sa
Hello,
I wanted to run some doctests with my Python 3 Sage installation.
However, running "sage -t" results in
Using --optional=dochtml,memlimit,mpir,python2,sage
ie, python2 is in the list. Is that expected? How should I
run the tests?
Vincent
--
You received this message because you are sub
Hi Frédéric,
On 2019-01-27, Frédéric Chapoton wrote:
> Does this mean that everything dependent on python will have to be
> recompiled when you switch ?
My original worktree was ~/Sage/git/sage. I added a new worktree
~/Sage/git/py3 using "git worktree add". The fact that
~/Sage/git/sage/local
Does this mean that everything dependent on python will have to be
recompiled when you switch ?
F
Le dimanche 27 janvier 2019 16:26:17 UTC+1, Timo Kaufmann a écrit :
>
>
>
> Am Sonntag, 27. Januar 2019 14:32:16 UTC+1 schrieb Simon King:
>
>> > *STATEMENT *: I would to advocate that **every devel
Hi Timo,
On 2019-01-27, Timo Kaufmann wrote:
> Git worktrees would be a solution. Essentially you keep one git repository,
> but check out two branches at the same time in different directories. From
> your main repo do this:
>
> $ git worktree add /path/to/the/new/checkout branch-to-checkout
Am Sonntag, 27. Januar 2019 14:32:16 UTC+1 schrieb Simon King:
> > *STATEMENT *: I would to advocate that **every developer switch to
> python3
> > NOW**.
>
> How?
>
Git worktrees would be a solution. Essentially you keep one git repository,
but check out two branches at the same time in d
Le 27/01/2019 à 15:56, Simon King a écrit :
Hi Vincent,
On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
king@klap:~/Sage/py3/sage$ git remote add trac g...@trac.sagemath.org:sage.git
After that, you should see "trac" among your remotes
$ git remote -v
And "origin" sho
It is blocking https://trac.sagemath.org/ticket/26792
Le dimanche 27 janvier 2019 15:56:02 UTC+1, Jeroen Demeyer a écrit :
>
> On 2019-01-27 14:23, Frédéric Chapoton wrote:
> > Some good python3 changes are blocked by the long awaited ticket
> > https://trac.sagemath.org/ticket/23572
>
> What
Hi Vincent,
On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
>> king@klap:~/Sage/py3/sage$ git remote add trac
>> g...@trac.sagemath.org:sage.git
>
> After that, you should see "trac" among your remotes
>
> $ git remote -v
>
> And "origin" should be your local repo.
Correct!
On 2019-01-27 14:23, Frédéric Chapoton wrote:
Some good python3 changes are blocked by the long awaited ticket
https://trac.sagemath.org/ticket/23572
What do you mean with that? It's a ticket adding doctests for a book,
how is that related to Python 3 porting?
--
You received this message be
Hi Simon,
Le 27/01/2019 à 15:19, Simon King a écrit :
On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
This has nothing to do with python 3.
Sure.
You only need to set up
properly your remote and branches.
Exactly. And that's already more than what I can do in git witho
I believe it was added by
What I am unsure about now (too hard to dig using a phone :-)) is how to
switch between different SAGE_LOCAL.
Probably by setting an env. variable.
https://trac.sagemath.org/ticket/21479
On Sun, 27 Jan 2019 14:12 Vincent Delecroix <20100.delecr...@gmail.com
wrote:
> Pl
Hi Vincent,
On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> This has nothing to do with python 3.
Sure.
> You only need to set up
> properly your remote and branches.
Exactly. And that's already more than what I can do in git without
reading tons of documentation.
> After
Please tell us how. None of us claimed that two clones were needed.
Le 27/01/2019 à 15:03, Dima Pasechnik a écrit :
Why does one need two clones? We have functionality to allow a custom build
location. It should be possible to give it to configure as a parameter...
On Sun, 27 Jan 2019 13:58 Vin
Why does one need two clones? We have functionality to allow a custom build
location. It should be possible to give it to configure as a parameter...
On Sun, 27 Jan 2019 13:58 Vincent Delecroix <20100.delecr...@gmail.com
wrote:
>
>
> Le 27/01/2019 à 14:50, Simon King a écrit :
> > Hi Vincent,
> >
PPS: if you intend to have a py2 and py3 installation it is a good
idea to have a shared $SAGE_ROOT/upstream/ repository (where
package tarballs are downloaded). This can be done via a simple
simlink in the py3 installation.
Maybe we could create a configure option --with-upstream=PATH for
this?
Le 27/01/2019 à 14:50, Simon King a écrit :
Hi Vincent,
On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
You need a different clone of your git repo, let say sage-py3.
How to do so most easily, so that "git pull" etc. still referes to trac?
That was part of my question.
git clone git://github.com/sagemath/sage.git sage3
Le dimanche 27 janvier 2019 14:50:22 UTC+1, Simon King a écrit :
>
> Hi Vincent,
>
> On 2019-01-27, Vincent Delecroix <20100.d...@gmail.com >
> wrote:
> > You need a different clone of your git repo, let say sage-py3.
>
> How to do so most eas
Hi Frédéric,
On 2019-01-27, Frédéric Chapoton wrote:
> I am pretty sure you would be rather happy working only with python3.
That's too early. For teaching, I need to know that I have a working
Sage installation, and for research I also have to have a working
installation of my group cohomology
Hi Vincent,
On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> You need a different clone of your git repo, let say sage-py3.
How to do so most easily, so that "git pull" etc. still referes to trac?
That was part of my question. Doing "git pull
/path/to/my/old/installation" wou
>
>
> > *STATEMENT *: I would to advocate that **every developer switch to
> python3
> > NOW**.
>
> How?
>
> To make my question more precise: For production I would like to
> keep a python 2 installation of Sage.
I am pretty sure you would be rather happy working only with python3.
> So
Le 27/01/2019 à 14:32, Simon King a écrit :
Hi Frédéric,
On 2019-01-27, Frédéric Chapoton wrote:
(2) the most badly failing file is "explain_pickle" with 70 failing
doctests. Hopefully, this will be treated very carefully by Erik M. Bray
(3) after that, we still have problems with graph, wher
Hi Frédéric,
On 2019-01-27, Frédéric Chapoton wrote:
> (2) the most badly failing file is "explain_pickle" with 70 failing
> doctests. Hopefully, this will be treated very carefully by Erik M. Bray
>
> (3) after that, we still have problems with graph, where generic_graph.py
> has 50 failing do
Hello everybody,
here is a small progress report on porting sage to python3. Good, but still
too slow for my taste. The sooner we can catch up with jupyter, the better..
(1) with the latest beta (8.7.b1), there are now exactly 200 files having
failing doctests, and a total of 866 failing doctes
44 matches
Mail list logo
