by Luc Saffre · in Developers · assigned to Luc Saffre

Résumé

Concepts sous-jacents

Commentaires

• 1 année, 6 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : Also etgen and rstgen are now migrated.
• 1 année, 6 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I started migrating getlino to pyproject.toml before using it on bombur.
• 1 année, 6 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I pushed my changes to presto.
• 1 année, 6 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I'll now migrate welfare, welcht, weleup from setup.py to pyproject.toml and then release them to pypi, because I'd like to have the newest version on the weleup1 and welcht1 public demos.
• 1 année, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) (2 replies) : @8lurry presto is failing because pytest is not installed. To fix this, you should migrate the presto repo from setup.py to pyproject.toml and then in the gitlab-ci.yaml say "pip install -e .[testing]" instead of "pip install -e .".
• 1 année, 8 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : Together with @8lurry I migrated commondata-be to pyproject.toml. Because it is a namespace subpackage I had to remove the commondata/__ini__.py file, the name must be "commondata-be" (not "commondata.be") and there must be a [tool.hatch.build.targets.wheel] section with packages = ["commondata/be"] ([url...
• 1 année, 9 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I am migrating the cms package to pyproject.toml, this is a bit work than usual because I had to decide whether CMS is privileged or independent (stand-alone) application. It was already privileged (cms1 is a demo project in the book and the Python AP is in the book, but the repository still had a d...
• 1 année, 11 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I migrated amici
• 1 année, 11 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : "inv mm" no longer specifies the version and project name when it runs "pybabel extract".
• 2 ans ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I migrated algus (before using it for #5762 (Lino Prima first draft)
• 2 ans, 1 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I also migrated xl now.
• 2 ans, 1 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) (1 reply) : How to get the version number (which is in setup_info.py) into the pyproject.toml?
• 2 ans, 3 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I updated all repositories to have a message_extractors.ini file instead of a message_extractors key in their setup_info.py.
• 2 ans, 3 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I changed the atelier command "inv mm" so that it uses the babel CLI instead of the setup.py file.
• 2 ans, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : Today I learned that before running twine upload it is good to run [url twine.readthedocs.io/en/stable/#twine-check twine check] (which checks whether your distribution’s long description will render correctly on PyPI). And thus it's better to git push only when twine upload has succeeded.
• 2 ans, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : Before migrating more packages, I wait for an idea about how to make the "release to pypi" more automatic/systematic.
• 2 ans, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I released commondata 24.3.0 and 24.3.1. Also mentioned this in our [url dev.lino-framework.org/changes/2024.html changelog] (which deserves a bit more activity). Let's see whether book now passes on GL.
• 2 ans, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : After reading [url packaging.python.org/en/latest/guides/packaging-namespace-packages/ this page about namespace packages] I think that commondata actually doesn't want to be a namespace package. I'd rather add a concept of regional extensions.
• 2 ans, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : I did it recently for eid, and now i plan to do it for the commondata packages.
• 2 ans, 7 mois ago by Luc Saffre about #5484 (Migrate from setup.py to pyproject.toml) : Created new Ticket #5484@dev (Migrate from setup.py to pyproject.toml).