Skip to main content

The package is for developing algorithm in prediction.

Project Setup

Here we provide some details about the project setup. Most of the choices are explained in the guide. Links to the relevant sections are included below. Feel free to remove this text when the development of the software package takes off.

For a quick reference on software development, we refer to the software guide checklist.

Version control

Once your Python package is created, put it under version control! We recommend using git and github.

cd deepdata_alpha
git init
git add -A
git commit

To put your code on github, follow this tutorial.

Python versions

This repository is set up with Python versions: * 3.4 * 3.5 * 3.6

Add or remove Python versions based on project requirements. The guide contains more information about Python versions and writing Python 2 and 3 compatible code.

Package management and dependencies

You can use either pip or conda for installing dependencies and package management. This repository does not force you to use one or the other, as project requirements differ. For advice on what to use, please check the relevant section of the guide.

  • Dependencies should be added to setup.py in the install_requires list.

Packaging/One command install

You can distribute your code using pipy or conda. Again, the project template does not enforce the use of either one. The guide can help you decide which tool to use for packaging.

Testing and code coverage

  • Tests should be put in the tests folder.

  • The tests folder contains:

    • Example tests that you should replace with your own meaningful tests (file: test_deepdata_alpha)

    • A test that checks whether your code conforms to the Python style guide (PEP 8) (file: test_lint.py)

  • The testing framework used is PyTest

  • Tests can be run with python setup.py test

    • This is configured in setup.py and setup.cfg

  • Use Travis CI to automatically run tests and to test using multiple Python versions

  • TODO: add something about code quality/coverage tool?

  • Relevant section in the guide

Documentation

  • Documentation should be put in the docs folder. The contents have been generated using sphinx-quickstart (Sphinx version 1.6.5).

  • We recommend writing the documentation using Restructured Text (reST) and Google style docstrings.

  • The documentation is set up with the Read the Docs Sphinx Theme.

  • To generate html documentation run python setup.py build_sphinx

    • This is configured in setup.cfg

    • Alternatively, run make html in the docs folder.

  • The docs/_templates directory contains an (empty) .gitignore file, to be able to add it to the repository. This file can be safely removed (or you can just leave it there).

  • To put the documentation on Read the Docs, log in to your Read the Docs account, and import the repository (under ‘My Projects’).

    • Include the link to the documentation in this README.

  • Relevant section in the guide

Coding style conventions and code quality

  • Check your code style with prospector

  • You may need run pip install .[dev] first, to install the required dependencies

  • You can use yapf to fix the readability of your code style and isort to format and group your imports

  • Relevant section in the guide

Package version number

  • We recommend using semantic versioning.

  • For convenience, the package version is stored in a single place: deepdata_alpha/__version__.py. For updating the version number, you only have to change this file.

  • Don’t forget to update the version number before making a release!

CHANGELOG.rst

CITATION.cff

  • To allow others to cite your software, add a CITATION.cff file

  • It only makes sense to do this once there is something to cite (e.g., a software release with a DOI).

  • Follow the making software citable section in the guide.

CODE_OF_CONDUCT.rst

CONTRIBUTING.rst

MANIFEST.in

NOTICE

Installation

To install deepdata_alpha, do:

git clone https://github.com/John/deepdata_alpha.git
cd deepdata_alpha
pip install .

Run tests (including coverage) with:

python setup.py test

Documentation

Include a link to your project’s full documentation here.

Contributing

If you want to contribute to the development of deepdata_alpha, have a look at the contribution guidelines.

License

Copyright (c) 2018, John J. H. Lin

Credits

This package was created with Cookiecutter and the NLeSC/python-template.

Metadata

Release files for deepdata_alpha 0.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deepdata_alpha 0.2.4
File Size Uploaded
deepdata_alpha-0.2.4.tar.gz 17.9 MB Details

Release files / deepdata_alpha-0.2.4.tar.gz

Download URL deepdata_alpha-0.2.4.tar.gz
Size 17.9 MB
Tags Source
SHA-256 checksum
How to use checksums
96e9eb2257ec0a8d86213009a1d652ac75d1dde1dea80db2dd950da78629bd40
BLAKE2b-256 checksum
How to use checksums
53dc8c49601534ba4fa570a25fcbf03d654a3f88ec3940b5336c547474e0dc4f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.20.0 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7

Release history Release notifications | RSS feed

This release

0.2.4 This release

1 release file

0.2.3

2 release files

0.2.2

2 release files

0.2.1

1 release file

0.2.0

1 release file

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page