This Package contains tools for interacting with the Cell Science Airtable
- Store values and retain the prior value in memory
- ... some other functionality
from airtable_core import Example
a = Example()
a.get_value() # 10
Stable Release: pip install airtable_core
Development Head: pip install git+https://github.com/BrianWhitneyAI/airtable_core.git
For full package documentation please visit BrianWhitneyAI.github.io/airtable_core.
See CONTRIBUTING.md for information related to developing the code.
-
pip install -e .[dev]
This will install your package in editable mode with all the required development dependencies (i.e.
tox
). -
make build
This will run
tox
which will run all your tests in both Python 3.7 and Python 3.8 as well as linting your code. -
make clean
This will clean up various Python and build generated files so that you can ensure that you are working in a clean environment.
-
make docs
This will generate and launch a web browser to view the most up-to-date documentation for your Python package.
- Turn your project into a GitHub repository:
- Make an account on github.com
- Go to make a new repository
- Recommendations:
- It is strongly recommended to make the repository name the same as the Python package name
- A lot of the following optional steps are free if the repository is Public, plus open source is cool
- After a GitHub repo has been created, run the commands listed under: "...or push an existing repository from the command line"
- Register your project with Codecov:
- Make an account on codecov.io(Recommended to sign in with GitHub) everything else will be handled for you.
- Ensure that you have set GitHub pages to build the
gh-pages
branch by selecting thegh-pages
branch in the dropdown in the "GitHub Pages" section of the repository settings. (Repo Settings) - Register your project with PyPI:
- Make an account on pypi.org
- Go to your GitHub repository's settings and under the
Secrets tab,
add a secret called
PYPI_TOKEN
with your password for your PyPI account. Don't worry, no one will see this password because it will be encrypted. - Next time you push to the branch
main
after usingbump2version
, GitHub actions will build and deploy your Python package to PyPI.
main
is for the most up-to-date development, very rarely should you directly commit to this branch. GitHub Actions will run on every push and on a CRON to this branch but still recommended to commit to your development branches and make pull requests to main. If you push a tagged commit with bumpversion, this will also release to PyPI.- Your day-to-day work should exist on branches separate from
main
. Even if it is just yourself working on the repository, make a PR from your working branch tomain
so that you can ensure your commits don't break the development head. GitHub Actions will run on every push to any branch or any pull request from any branch to any other branch. - It is recommended to use "Squash and Merge" commits when committing PR's. It makes
each set of changes to
main
atomic and as a side effect naturally encourages small well defined PR's.
Allen Institute Software License