Clean up old files#326
Open
NoodlesNZ wants to merge 1 commit into
Open
Conversation
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
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.
Trying to clean up some of the older/unused files in this project:
.gitbook/- As far as I can see this is no longer being usedCHANGELOG.md- This is out of date and the changes are being tracked in Github releasesCODEOWNERS- The file in the root is duplicative with the one in the.githubdir. I have removed the one in the rootMANIFEST.in- Used with setuptools, but not required if we're using poetry for packagingROADMAP.md- Out of date, we may recreate using the Github project roadmap featureSUMMARY.md- Not sure what this is or why it was hererequirements.txt- Not required when using poetry/pyproject.toml, this is also out of daterequirements-dev.txt- Not required when using poetry/pyproject.toml, this is also out of datesetup.py- Used with setuptools, but not required if we're using poetry for packagingI have migrated the setting from
setup.pytopyproject.tomlTo build and publish the package now:
Build
Produces both a wheel (.whl) and source distribution (.tar.gz) in dist/.
Publish
Prompts for your PyPI username and password (or API token). To combine build and publish in one step: