MSVDD + Bloc
(Microsoft + DataKind AI in Cities Virtual Accelerator - DataDive) + (Bloc)
setup
-
Clone this repository to a directory on your local machine:
$ cd /path/to/your/preferred/directory $ git clone git@github.com:datakind/msvdd_Bloc.git $ cd msvdd_Bloc -
Create a virtual environment to isolate our project's dependencies from your other projects'. Use whichever tool you prefer (e.g.
virtualenv,pyenv,pipenv). Here's an example usingpyenv:msvdd_Bloc(master)$ pyenv virtualenv 3.7.4 bloc-env msvdd_Bloc(master)$ pyenv shell bloc-env -
Install the package in one of two ways.
-
To use the
msvdd_bloccode as-is without further development, installation is simple:(bloc-env) msvdd_Bloc(master)$ pip install . -
To further develop the code, install the package in locally-editable (aka develop) mode, plus a few additional dependencies:
(bloc-env) msvdd_Bloc(master)$ pip install -e . (bloc-env) msvdd_Bloc(master)$ pip install -r requirements-dev.txt
-
-
Create a branch with a descriptive name for you to hack on, as needed:
(bloc-env) msvdd_Bloc(master)$ git pull (bloc-env) msvdd_Bloc(master)$ git checkout -b my-example-branch-name
documentation
Stand-alone doc files live under the top-level docs/ directory and are written in reStructured Text format. They are built using sphinx:
$ cd docs
$ make html
As needed, commit the latest version of the built HTML docs to the project's master branch:
$ git commit -am "Update built HTML docs"
$ git push origin master
These files are automatically published through GitHub Pages, and are accessible via web browser at https://datakind.github.io/msvdd_Bloc.
In-code docstrings follow Google style. These docstrings are automatically incorporated into the main docs via sphinx.ext.sphinx-autodoc. Refer to the sphinx site for details.
tests
Test modules live under the top-level tests/ directory. They are run using pytest:
$ cd tests
$ pytest -vv .
A coverage report may additionally be generated using pytest-cov:
$ pytest -vv --cov=msvdd_bloc --cov-report=term-missing .
Refer to the pytest site for details.
Metadata
Release files for hiphopscrap 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hiphopscrap-0.1.1.tar.gz | 53.4 kB | Without provenance | Details for hiphopscrap-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hiphopscrap-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for hiphopscrap-0.1.1-py3-none-any.whl |
Total release size: 119.1 kB
Release files / hiphopscrap-0.1.1.tar.gz
| Download URL | hiphopscrap-0.1.1.tar.gz |
|---|---|
| Size | 53.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eeee247eaece36f02ff22702b69247a82e56f031a4f0c566115caf0cde5dac60
|
|
BLAKE2b-256 checksum How to use checksums |
b47d6967dfdc826eebf86957b25ea285809b6a72f9ffb05939988c09e4aac8ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/2.7.16
|
Release files / hiphopscrap-0.1.1-py3-none-any.whl
| Download URL | hiphopscrap-0.1.1-py3-none-any.whl |
|---|---|
| Size | 65.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6f615acf23ad4a1d0e10e19ebcf424a450f6676412b521d2ab23517906b32fc
|
|
BLAKE2b-256 checksum How to use checksums |
7b2443575087f72e9f43338e0e2791145583797c6ed4a66f78410eed17f0c13e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/2.7.16
|
Security for hiphopscrap 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.