Initial commit of Python Packaging article #707
Merged
Conversation
This file contains 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
I wrote this on my [blog](https://ns-rse.github.io/posts/python-packaging) earlier this year and feel its ready for publishing on the RSE blog (I often use it as a testing ground prior to publishing on the RSE blog). Comments and feedback welcome as whilst I've published a few packages now I still feel like I've a lot to learn and have no doubt made some mistakes (beyond the usual spelling & grammar issues). I've another post on publishing documentation with Sphinx in the pipeline that will follow on nicely from this.
ns-rse
requested review from
davidwilby,
EdwinB12,
mondus,
ptheywood,
Robadob,
Romain-Thomas-Shef,
tartarini,
twinkarma and
ubdbra001
Romain-Thomas-Shef
approved these changes
Sep 15, 2023
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.
I wrote this on my blog earlier this year and feel its ready for
publishing on the RSE blog (I often use it as a testing ground prior to publishing on the RSE blog).
Comments and feedback welcome as whilst I've published a few packages now I still feel like I've a lot to learn and have
no doubt made some mistakes (beyond the usual spelling & grammar issues).
I've another post on publishing documentation with Sphinx in the pipeline that will follow on nicely from this.