Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ jobs:
run: |
mkdir -p ~/locales/fr/LC_MESSAGES/
cp -uv --parents *.po */*.po ~/locales/fr/LC_MESSAGES/
git -C ~/cpython checkout 895591c1f0bdec5ad357fe6a5fd0875990061357
git -C ~/cpython checkout $(grep ^CPYTHON_CURRENT_COMMIT Makefile| cut -d= -f2)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sinon, peut-être pourrait-on ajouter une cible dans le Makefile pour synchroniser les deux sans effort ?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Proposition idiote : ne pourrait-on pas avoir un fichier CPYTHON_CURRENT_COMMIT à la racine dont le contenu est le hash du commit ?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Je n'aime pas avoir trop de fichiers à la racine :D

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sinon, peut-être pourrait-on ajouter une cible dans le Makefile pour synchroniser les deux sans effort ?

Qu'on va oublier aussi, je préfère n'avoir qu'une source de vérité.

- name: Prepare venv
run: |
# If the venv exists but is broken, drop it (happens on Python upgrades):
Expand Down