+1
On Tuesday, September 8, 2020 at 7:18:34 AM UTC+10, Matthias Koeppe wrote:
>
> tox (https://tox.readthedocs.io/en/latest/) is a popular package that is
> used by a large number of Python projects as the standard entry point for
> testing and linting.
>
> Sage 9.1 started to use tox for
We're down to 32 tickets with milestone Sage 9.2 in 'needs_review'.
Here is a view grouped by component:
https://trac.sagemath.org/query?status=needs_review=sage-9.2=1=component=800=id=summary=component=time=changetime=author=reviewer=keywords=component
On the other hand, across milestones, 5
+1
--
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...@googlegroups.com.
To view this discussion on the web visit
+1
On Mon, 7 Sep 2020, 22:18 Matthias Koeppe, wrote:
> tox (https://tox.readthedocs.io/en/latest/) is a popular package that is
> used by a large number of Python projects as the standard entry point for
> testing and linting.
>
> Sage 9.1 started to use tox for portability testing of the Sage
+1
Eric.
Le lundi 7 septembre 2020 à 23:18:34 UTC+2, Matthias Koeppe a écrit :
> tox (https://tox.readthedocs.io/en/latest/) is a popular package that is
> used by a large number of Python projects as the standard entry point for
> testing and linting.
>
> Sage 9.1 started to use tox for
On Monday, September 7, 2020 at 2:27:25 PM UTC-7, Nils Bruin wrote:
>
> I think it's possible to write unit tests already, so if you prefer you
> should be able to do that. I know the category framework has some
> standardized testing. It may be able to be triggered from doctests, even!
>
On Monday, September 7, 2020 at 7:13:28 AM UTC-7, tobia...@gmx.de wrote:
>
> As for the advantages of unittests over doctests (given my limited
> experience with the latter):
> - Can easily run and debug single tests
>
For the most part, cut/paste realizes that for doctests too
> - Get full
tox (https://tox.readthedocs.io/en/latest/) is a popular package that is
used by a large number of Python projects as the standard entry point for
testing and linting.
Sage 9.1 started to use tox for portability testing of the Sage
distribution (
yes (I did this) and no (it didn't work).
John H Palmieri schrieb am Montag, 7. September 2020 um 20:54:37 UTC+2:
> Did you do what Dima said, rebuild Python 3?
>
> 1. make
> 2. realize you need to install openssl
> 3. make openssl
> 4. sage -f python3 (to force a rebuild Python 3)
> 5. make
>
>
Did you do what Dima said, rebuild Python 3?
1. make
2. realize you need to install openssl
3. make openssl
4. sage -f python3 (to force a rebuild Python 3)
5. make
should work.
On Monday, September 7, 2020 at 11:48:19 AM UTC-7, Martin R wrote:
>
> Unfortunately, it seems that make clean is
Unfortunately, it seems that make clean is necessary. I tried both to no
avail. Thank you anyway!
John H Palmieri schrieb am Montag, 7. September 2020 um 20:29:07 UTC+2:
>
>
> On Monday, September 7, 2020 at 11:27:15 AM UTC-7, John H Palmieri wrote:
>>
>> You could do
>>
>> ./configure
On Monday, September 7, 2020 at 11:27:15 AM UTC-7, John H Palmieri wrote:
>
> You could do
>
> ./configure --enable-openssl=yes
> make
>
> or atlernatively
>
> make openssl
> make
>
And the second of these (make openssl; make) might be better because it
should ensure that openssl is built
You could do
./configure --enable-openssl=yes
make
or atlernatively
make openssl
make
On Monday, September 7, 2020 at 11:09:07 AM UTC-7, Martin R wrote:
>
> unfortunately, no.
>
> What I don't quite understand: I can do sage -i openssl only *after* I
> built sage, but python3 is built at the
unfortunately, no.
What I don't quite understand: I can do sage -i openssl only *after* I
built sage, but python3 is built at the very beginning. So what am I
supposed to do?
dim...@gmail.com schrieb am Montag, 7. September 2020 um 16:01:59 UTC+2:
> after you rebuild python3,
> simply
>
>
On 07/09/2020 17:13, tobia...@gmx.de wrote:
I wasn't aware of the fact that many contributors to sage are users in
the first place, and contributors second. So they are probably more
familiar with sage's doctests than with unittests. That's good input,
thanks!
For me, it's actually the
I wasn't aware of the fact that many contributors to sage are users in the
first place, and contributors second. So they are probably more familiar
with sage's doctests than with unittests. That's good input, thanks!
For me, it's actually the converse: I didn't know what doctests are, but
was
after you rebuild python3,
simply
make build
should work, no need to clean, IMHO
On Mon, 7 Sep 2020, 13:11 'Martin R' via sage-devel, <
sage-devel@googlegroups.com> wrote:
> I am getting an ssl error when using my fresh sage build.
>
> I admit that I first build sage without thinking about
I am getting an ssl error when using my fresh sage build.
I admit that I first build sage without thinking about ssl, and then did
sage -i openssl and sage -f python3.
Should I rebuild from scratch? If so, what should I do exactly?
Martin
sage: oeis([sum(1 for la in Partitions(n)) for n in
18 matches
Mail list logo
