This is way above my understanding of "make" matters. So help from Erik or
Jeroen or whoever is knowledgeable in this kind of things, is required.
Le vendredi 9 février 2018 21:24:34 UTC+1, Volker Braun a écrit :
> Can you first set up a makefile target that is supposed to be tested? E.g.
> "make test-python3" builds with py3 and eventually gets extended to test
> things that already work?
> On Friday, February 9, 2018 at 9:15:04 PM UTC+1, fchap...@gmail.com wrote:
>> Volker, it would be great (and I would appreciate) if you could set up a
>> buildbot that checks that sage builds with python3. One can not yet say
>> that vanilla-sage builds and starts with "export SAGE_PYTHON3=yes", but at
>> least it builds (since some time already). Starting is another matter, but
>> maybe not so far.
>> This would help to prevent any regression,as the one that just happened
>> with subprocess32.
>> Le vendredi 9 février 2018 20:15:13 UTC+1, Jeroen Demeyer a écrit :
>>> On 2018-02-09 17:55, fchap...@gmail.com wrote:
>>> > I have a build failure in subprocess32 on a python3 build (using
>>> > SAGE_PYTHON3=yes)
>>> Fixed in https://trac.sagemath.org/ticket/24650
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.