jupytext v1.2.2

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.
Notes for merging this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
   Checklist before merging this PR:

• Dependencies have been updated if changed
• Tests have passed
• Updated license if changed and license_file is packaged

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one.

_{This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[mwouts]

There is an issue with this build, see mwouts/jupytext#323.

@grst, do you think I could fix the issue on the tar.gz package, publish it to a test repo and change the url in the recipe/meta.yaml? Is that an acceptable hack?

Also, maybe I should make sure on Jupytext's CI that the conda package can be build. Does anyone knows how to do that? Thanks!

[grst]

@grst, do you think I could fix the issue on the tar.gz package, publish it to a test repo and change the url in the recipe/meta.yaml? Is that an acceptable hack?

Sounds ugly. Why would you want to do that?
For testing within the conda-ci it may be ok, but once it's fixed I would just release a new +0.0.1 version.

Also, maybe I should make sure on Jupytext's CI that the conda package can be build. Does anyone knows how to do that? Thanks!

In any case it would be hard to reproduce the exact same build environment they use at conda-forge (they build within a docker container etc.). But maybe the conda-ci can be triggered before creating a new release?

[mwouts]

There won't be a 1.2.2 version on conda, but 1.2.3 is in the pipe, and should fix the issue we had here...