New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: 8.7.0 removes code-block:: ipython
pygment lexer support
#13845
Comments
I ran into the same problem. I think this is due to the Pygments entry points not being correctly installed with 8.6.0 Compare
to this
I suspect this is related to #13842 as setuptools probably doesn't merge the entry points configured in setup.py with the ones configured in setup.cfg |
Agree that this seems to be a bug that snuck into
in our |
* Disallow ipython v8.7.0 to avoid Pygments warning > WARNING: Pygments lexer name 'ipython3' is not known which arises during the docs build. This is a stopgap measure and this line should be removed as soon as there is a resolution and new ipython release. - c.f. ipython/ipython#13845
* Update docs dependencies * Avoid bug in ipython 8.7.0 See ipython/ipython#13845
I also have the same problem because the not available lexer breaks the build of TestSlide package. Unfortunately, it seems that I won't be able to update ipython in Fedora Linux to 8.7.0 because of this issue. |
I want to prepare a fix for this issue. What should be the single point of truth for the entrypoints? Setup.cfg or setup.py? |
@frenzymadness I think it needs to be setup.py #13842 moved some of the entry points to setup.py since they are dynamically generated and that is apparently only supported in setup.py |
…-pygments-entry-points
…-pygments-entry-points
…-pygments-entry-points
…-pygments-entry-points
…-pygments-entry-points
…-pygments-entry-points
…-pygments-entry-points
ah, was behind on this discussion, this would have been a great first contribution! hopefully that patch will be sufficient for any that would like to ship 8.7.0 with the pygments integration, if your build system allows patches. to that end: i've applied something similar on conda-forge/ipython-feedstock#182, but also had to deal with wanting to do minimal builds, so we've also added the python-minor |
Thanks for the quick fix. Any chance of a point release with the fix? |
The latest ipython=8.7.0 version installed via readthedocs has a bug that raises `WARNING: Pygments lexer name 'ipython' is not known`. This is being tracked at ipython/ipython#13845, and will need to wait for ipython=8.7.1 or later to be released, so keep using ipython=8.6.0 for now.
* ⬆️ Bump certifi from 2022.5.18.1 to 2022.12.7 Bumps [certifi](https://github.com/certifi/python-certifi) from 2022.5.18.1 to 2022.12.7. - [Release notes](https://github.com/certifi/python-certifi/releases) - [Commits](certifi/python-certifi@2022.05.18.1...2022.12.07) --- updated-dependencies: - dependency-name: certifi dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> * 🩹 Relock with poetry 1.2.0 Reverting the hyphen underscore package name normalization for now. * 📌 Temporarily pin ipython!=8.7.0 to prevent warning The latest ipython=8.7.0 version installed via readthedocs has a bug that raises `WARNING: Pygments lexer name 'ipython' is not known`. This is being tracked at ipython/ipython#13845, and will need to wait for ipython=8.7.1 or later to be released, so keep using ipython=8.6.0 for now. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Wei Ji <23487320+weiji14@users.noreply.github.com>
…oints fix pygments.lexers entry_points
|
Installed via pip / PyPI -- previously this RST worked:
but now we get:
At least this is what I think is happening in our CircleCI build today (which fails because we treat warnings as errors), we haven't changed the RST lines in question at all recently:
https://app.circleci.com/pipelines/github/mne-tools/mne-python/17137/workflows/27c6f253-b7a7-4b67-9c2e-db9aa4e925fc/jobs/50745?invite=true#step-112-532
And 8.7.0 is being installed properly in the env:
https://app.circleci.com/pipelines/github/mne-tools/mne-python/17137/workflows/27c6f253-b7a7-4b67-9c2e-db9aa4e925fc/jobs/50745?invite=true#step-112-532
Changing this to
.. code-block:: ipythonconsole
does not seem to help.Is this an intentional change? Or is this lexer meant to be installed a different way? I didn't see anything in these pages at least:
The text was updated successfully, but these errors were encountered: