update sagetex to version 3.6.1

[dimpase]

Previous update: #30342, merged 2020-08-20.

Depends on #34219

CC: @kcrisman @mkoeppe @orlitzky @slel @jhpalmieri @EmmanuelCharpentier

Component: packages: standard

Author: Dima Pasechnik, Matthias Koeppe

Branch/Commit: add10cd

Reviewer: Emmanuel Charpentier

Issue created by migration from https://trac.sagemath.org/ticket/32887

[dimpase]

Author: Dima Pasechnik

[dimpase]

New commits:

9e26d0a

update sagetex to version 3.6

[dimpase]

Commit: 9e26d0a

[dimpase]

Branch: u/dimpase/packages/sagetex/v3.6

[mkoeppe]

comment:2

sagetex has a new dependency, pyparsing, that also needs to be added as dependency of the SPKG. - https://github.com/sagemath/sagetex/blob/master/setup.py#L16

And the 3.6 release is defective - it still identifies itself as 3.5 - https://github.com/sagemath/sagetex/blob/master/setup.py#L7

[mkoeppe]

comment:3

Or, rather, what is on https://github.com/sagemath/sagetex/ does not match what is packaged up in the release tarball

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

180f8a1

correct version in setup.py, and deps

[sagetrac-git]

Changed commit from 9e26d0a to 180f8a1

[dimpase]

comment:5

should all be fixed now, sorry. To much different metadata to tie up manually here...

[dimpase]

comment:6

I think I'll eventually add a small configure script to set up all the versions right.
If only there was a way to put tarballs up on GitHub and creating GitHub releases from
the command line.

[mkoeppe]

comment:7

What is the tarball doing on GitHub?
Is it not supposed to be on CTAN (https://ctan.org/pkg/sagetex?lang=en) or on PyPI?

[dimpase]

comment:8

Replying to @mkoeppe:

What is the tarball doing on GitHub?
Is it not supposed to be on CTAN (https://ctan.org/pkg/sagetex?lang=en) or on PyPI?

there is something called sagetex.zip on CTAN - but the process of publishing there is manual, and I have not put this there yet.

And I don't know anything about PyPI publishing.

[kcrisman]

comment:9

Is it not supposed to be on CTAN (https://ctan.org/pkg/sagetex?lang=en) or on PyPI?

Unless something has changed, we do not want it on CTAN, because that will not match versions with Sage. Dan always made sure that the versions matched (indeed, I think this is in the release instructions for SageTeX?) and so one has to manually move the .sty file, or did have to do.

[dimpase]

comment:10

Hmm, what do you mean by "we don't want it on CTAN"? Have you forgotten how we started putting in on CTAN few years ago? (And I did it for versions 3.4 and 3.5, and will do for 3.6)

[saraedum]

comment:11

Replying to @dimpase:

I think I'll eventually add a small configure script to set up all the versions right.
If only there was a way to put tarballs up on GitHub and creating GitHub releases from
the command line.

Have you looked into rever? I use it to create tarballs for autoconfiscated packages, release them on GitHub and on PyPI. See, e.g., https://github.com/flatsurf/flatsurf/blob/master/rever.xsh.

[kcrisman]

comment:12

Unless something has changed,

Apparently it has.

Hmm, what do you mean by "we don't want it on CTAN"? Have you forgotten how we started putting in on CTAN few years ago? (And I did it for versions 3.4 and 3.5, and will do for 3.6)

That is good news, and I hope it will keep track with the Sage versions well.

[dimpase]

comment:13

Replying to @kcrisman:

Unless something has changed,

Apparently it has.

Hmm, what do you mean by "we don't want it on CTAN"? Have you forgotten how we started putting in on CTAN few years ago? (And I did it for versions 3.4 and 3.5, and will do for 3.6)

That is good news, and I hope it will keep track with the Sage versions well.

Karl, it's almost 2 years old news:

Date: Thu, 24 Jan 2019 18:50:56 +0000
References: <CAKqbAeFMwHMHYbOfA7SOXOJuuv6aBU=89R0Cz8iddJxkmg+64g@mail.gmail.com>
In-Reply-To: <CAKqbAeFMwHMHYbOfA7SOXOJuuv6aBU=89R0Cz8iddJxkmg+64g@mail.gmail.com>
Message-ID: <CAAWYfq211+bChdmArcJAPwK62opKnSxEfERmtS_xBbcV3kEH_A@mail.gmail.com>
Subject: Re: are you guys the CTAN maintainers for SageTeX now?
From: Dima Pasechnik <...>
To: Dan Drake <...>
Cc: Karl-Dieter Crisman <...>
Content-Type: text/plain; charset="UTF-8"

Hi Dan,
the update is in! cf https://ctan.org/pkg/sagetex?lang=en
Cheers,
Dima

On Wed, Jan 23, 2019 at 1:45 AM Dan Drake <> wrote:
>
> Hi Karl-Dieter, Dima,
>
> Following up -- I see the reply from the CTAN guy. Are you guys now considered the CTAN maintainers for SageTeX? Can you update or remove it?
>
> --
> Ceci n'est pas une .signature.

[kcrisman]

comment:14

Karl, it's almost 2 years old news:

I give up. I clearly can no longer keep 'Trac'.

[dimpase]

comment:15

Replying to @dimpase:

Replying to @mkoeppe:

What is the tarball doing on GitHub?
Is it not supposed to be on CTAN (https://ctan.org/pkg/sagetex?lang=en) or on PyPI?

there is something called sagetex.zip on CTAN - but the process of publishing there is manual, and I have not put this there yet.

And I don't know anything about PyPI publishing.

The package's Python code (apart from setup.py) is generated by TeX from a .dtx file.
Anyhow, I tried uploading its Makefile-created tarball (one used by Sage) anf got

$ twine upload  dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading sagetex-3.6.tar.gz
100%|████████████████████████| 71.0k/71.0k [00:00<00:00, 73.0kB/s]
Error during upload. Retry with the --verbose option for more details.
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
The name 'sagetex' isn't allowed. See https://pypi.org/help/#project-name for more information.

Perhaps some metadata is missing, I don't know. There is no sagetex project on PyPI as far as I can tell.

Let's get this in as is, and deal with a better distribution mechanism later.

[orlitzky]

comment:17

Is sagetex actually used by sage? TBH I've managed to avoid it until now.

[dimpase]

comment:18

No, sagetex is a !Sage/Latex package.
It's hard to spin it off, cause as a Python package, almost all of it is generated by running TeX on a .dtx file.

[sagetrac-git]

Changed commit from 3c0f87e to 6e5af72

[mkoeppe]

comment:136

[sagetex-3.6]   copying example.tex -> build/bdist.macosx-10.14-x86_64/wheel/sagetex-3.6.data/data/share/doc/sagetex
[sagetex-3.6]   error: can't copy 'sagetex.pdf': doesn't exist or not a regular file

[mkoeppe]

comment:137

OK, that was pointed out in comment:41 already.

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

add10cd

build/pkgs/sagetex: Use 3.6.1 release on PyPI

[sagetrac-git]

Changed commit from 6e5af72 to add10cd

[EmmanuelCharpentier]

comment:141

Replying to @mkoeppe:

Now we need fearless centaur testers

The centaur runs ... and passes ptestlong. Yay !

==> positive_review.

Thanks a lot !

[dimpase]

comment:142

Does

SAGE_CHECK=yes make sagetex

pass?

[EmmanuelCharpentier]

comment:143

Sorry for the wait (family obligations... ;-)

Replying to @dimpase:

Does

SAGE_CHECK=yes make sagetex

pass?

Yep !

HTH,

[mkoeppe]

comment:144

Thanks for the review!

[mkoeppe]

Reviewer: Emmanuel Charpentier

[vbraun]

Changed branch from u/mkoeppe/packages/sagetex/v3.6 to add10cd