require Python 3.10, update project metadata - #610
Open
minrk wants to merge 5 commits into
Open
Conversation
PEP 639 expects SPDX in license field license files with standard names are picked up automatically # Conflicts: # jupyter_server_proxy/config.py
prevents re-run from being able to download
not sure why connection is getting refused on unix socket _sometimes_
passed when debug info was added, maybe it'll pass again
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
What does this PR do?
Type of change:
updates required Python to 3.10, removes pre-3.10 compatibility
PEP 639 expects SPDX in license field
license files with standard names are picked up automatically
Is this PR related to an issue, or is it part of a larger body of work?
Does this PR introduce a breaking change?
no, bumping minimum Python version is not a breaking change
How can this PR be tested?
What should a reviewer concentrate their feedback on?
Other information