We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

From Research Project to PyPI Release

Formal Metadata

Title
From Research Project to PyPI Release
Title of Series
Number of Parts
115
Author
Contributors
License
CC Attribution - NonCommercial - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Halfway through my first postdoc it was clear it would be very difficult to submit a paper to a journal before my contract ended. How do I make something useful in the time allotted that keeps me motivated enough to finish a paper after my contract ends (and useful on a CV)? Answer: package my code into a tested library via GitHub, The Python Package Index (PyPI) and Zenodo for citations. Goals: - Pros and cons of rearranging a project for public release (5 min) - Python cookiecutter templates (5 min) - Options for testing (standard library unittest vs pytest) (5 min) - Continuous Integration (Travis vs GitHub Actions) (5 min) - Documentation (5 min) - Release on Zotero for citation (5 min) Prerequisites: - Intermediate Python - Command line