Table of Contents
Description
Back to Table of Contents
Description will go here.
Installation
Run the following to install:
$ pip install coimbra_chamber
Getting Started
Back to Table of Contents
We must configure our database before running any analysis:
First, we must decide if we want to use an in-memory SQLite database or point to an instance of a MySQL database. Then we need to create a config file in our working directory to reflect our configuration.
Create a copy of the file example-config.ini from the repository and rename it to config.ini. Move the config.ini file that we just created into your working directory and open the file. Change database_type to memory if we chose an in-memory database above. Otherwise, leave the database_type as MySQL and replace the host, user, and password fields with the host, username, and password for MySQL database we choose.
Then, to run an analysis:
>>> import coimbra_chamber as cc
>>> manager = cc.DataManager()
>>> manager.run()
Follow the prompts in the terminal to complete your analysis.
Python Version
Back to Table of Contents
This module is intended to use Python 3.6. and above.
MySQL Database
Back to Table of Contents
NOTE: In order to run the integration tests, a local version of mySQL must be installed and running.
On OSX you can run the following line to start the mySQL service after installing from LINK
$ sudo launchctl load -F /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
Stopping the mySQL service:
$ sudo launchctl unload -F /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
Preferred Way to Run Tests
Back to Table of Contents
1. From the repo directory; i.e., coimbra_chamber .. code-block:: bash
$ python -m pytest tests -xv –cov=coimbra_chamber –cov-report html tests
The above line requires both pytest and pytest-cov are installed.
Images
Back to Table of Contents
Metadata
Release files for coimbra-chamber 0.0.8
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 | |
|---|---|---|---|---|
| coimbra_chamber-0.0.8.tar.gz | 58.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| coimbra_chamber-0.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 100.1 kB
Release files / coimbra_chamber-0.0.8.tar.gz
| Download URL | coimbra_chamber-0.0.8.tar.gz |
|---|---|
| Size | 58.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
690a221147d21777fdcb64643cc06507e86ae8fc1b0887d6de1d51c9985a9d6b
|
|
BLAKE2b-256 checksum How to use checksums |
9bfeef720c3ccf738d17c7648a71798eeacc49de6f6d1cd874d7702f063629ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.41.0 CPython/3.7.5
|
Release files / coimbra_chamber-0.0.8-py3-none-any.whl
| Download URL | coimbra_chamber-0.0.8-py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b2b5259d02946e24907a15a94992b2d77b72b16da811d23955ab1d46cd8596d
|
|
BLAKE2b-256 checksum How to use checksums |
68857589618a8d926a08a2b25a1c381d016109952c17a69f4caa1c31ecd8875f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.41.0 CPython/3.7.5
|
Security for coimbra-chamber 0.0.8
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.