Skip to content

Update github workflows - #5248

Closed
matlads wants to merge 0 commit into
beetbox:masterfrom
matlads:master
Closed

Update github workflows#5248
matlads wants to merge 0 commit into
beetbox:masterfrom
matlads:master

Conversation

@matlads

@matlads matlads commented May 19, 2024

Copy link
Copy Markdown
Contributor

Description

Updates some github workflows to the latest versions

(...)

To Do

  • Documentation.
  • Changelog.
  • Tests.
  • CI

@snejus snejus left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Added a couple of comments regarding python versions and testing

- name: Check external links in docs
run: |
tox -e links

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why is this being removed?

Comment thread .github/workflows/integration_test.yaml Outdated
uses: actions/setup-python@v4
with:
python-version: 3.9-dev
python-version: 3.12

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think it may be best to test the earliest supported version

Comment thread .github/workflows/ci.yaml Outdated
matrix:
platform: [ubuntu-latest, windows-latest]
python-version: ['3.7', '3.8', '3.9', '3.x']
python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Happy to test the most recent python versions here! We probably want to include a note in the changelog as well.

On the other hand, I think we want to continue testing 3.7 before it's been properly removed from the codebase, see the relevant ticket here: #5222

snejus added a commit that referenced this pull request Jun 5, 2024
## Description

Fixes #5222. 

Drop Python 3.7. `pyupgrade` is responsible for most of the changes in
the code. I undid some of the bits it attempted to update that aren't
strictly necessary:

1. Converting `List/Dict/Tuple` -> `list/dict/tuple` in modules that
have `from __future__ import annotations` import. This should be done in
a separate PR, and for all modules
2. Converting some `.format(` calls to f-strings. It didn't do it
consistently, and it should also be done in a separate PR, I believe.

Python upgrade unblocks several other PRs, for example #5266 and #5248.
@snejus

snejus commented Jun 5, 2024

Copy link
Copy Markdown
Member

@matlads Python 3.7 has now been dropped, so try updating your PR!

@Serene-Arc

Copy link
Copy Markdown
Contributor

Might be a tool PR? Sometimes people go through repos with automated tools to make easy commits and open PRs to try and boost their GitHub profile/resume. Showing that you've contributed to a popular repo, seem more active.

Might not be a bad idea to update some workflows though, as long as they don't break anything.

@matlads

matlads commented Jun 9, 2024

Copy link
Copy Markdown
Contributor Author

@matlads Python 3.7 has now been dropped, so try updating your PR!

Will do.

@Serene-Arc

Copy link
Copy Markdown
Contributor

Do you want to reopen this PR?

@matlads

matlads commented Jun 9, 2024

Copy link
Copy Markdown
Contributor Author

Do you want to reopen this PR?

No. I'll make a new one.

@Serene-Arc

Copy link
Copy Markdown
Contributor

Please don't. This has already been created, just reopen and commit changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants