Permalink
Browse files

[DO NOT MERGE] Release candidate (#2298) (#2299)

Release candidate (#2298)
  • Loading branch information...
josenavas authored and antgonza committed Sep 27, 2017
1 parent 6080742 commit 5b54aa7e445dd38b34373d9aa72481ffa7d214a4
Showing with 3,506 additions and 3,648 deletions.
  1. +2 −3 .gitignore
  2. +30 −18 .travis.yml
  3. +22 −16 CONTRIBUTING.md
  4. +27 −16 INSTALL.md
  5. +1 −18 qiita_core/configuration_manager.py
  6. +14 −86 qiita_core/environment_manager.py
  7. +8 −2 qiita_core/qiita_settings.py
  8. +1 −8 qiita_core/support_files/config_test.cfg
  9. +2 −9 qiita_core/testing.py
  10. +0 −11 qiita_core/tests/test_configuration_manager.py
  11. +1 −2 qiita_core/util.py
  12. +1 −2 qiita_db/__init__.py
  13. +22 −13 qiita_db/artifact.py
  14. +0 −26 qiita_db/commands.py
  15. +2 −1 qiita_db/environment_manager.py
  16. +1 −1 qiita_db/handlers/oauth2.py
  17. +8 −25 qiita_db/handlers/processing_job.py
  18. +1 −1 qiita_db/handlers/tests/oauthbase.py
  19. +1 −1 qiita_db/handlers/tests/test_oauth2.py
  20. +1 −2 qiita_db/meta_util.py
  21. +1 −2 qiita_db/metadata_template/constants.py
  22. +12 −1 qiita_db/metadata_template/test/test_util.py
  23. +10 −12 qiita_db/metadata_template/util.py
  24. +0 −93 qiita_db/private.py
  25. +26 −40 qiita_db/processing_job.py
  26. +1 −0 qiita_db/search.py
  27. +6 −4 qiita_db/software.py
  28. +22 −8 qiita_db/sql_connection.py
  29. +25 −0 qiita_db/study.py
  30. +4 −0 qiita_db/support_files/patches/58.sql
  31. +14 −0 qiita_db/support_files/patches/59.sql
  32. +4 −0 qiita_db/support_files/patches/60.sql
  33. +186 −0 qiita_db/support_files/patches/python_patches/58.py
  34. BIN ...ort_files/test_data/processed_data/1_study_1001_closed_reference_otu_table-for_redbiom_tests.biom
  35. +1 −1 qiita_db/test/test_artifact.py
  36. +1 −81 qiita_db/test/test_commands.py
  37. +1 −2 qiita_db/test/test_meta_util.py
  38. +14 −12 qiita_db/test/test_processing_job.py
  39. +27 −0 qiita_db/test/test_software.py
  40. +14 −0 qiita_db/test/test_study.py
  41. +147 −2 qiita_db/test/test_util.py
  42. +206 −24 qiita_db/util.py
  43. +1 −2 qiita_pet/handlers/analysis_handlers/base_handlers.py
  44. +1 −2 qiita_pet/handlers/analysis_handlers/sharing_handlers.py
  45. +1 −1 qiita_pet/handlers/analysis_handlers/tests/test_base_handlers.py
  46. +11 −0 qiita_pet/handlers/analysis_handlers/tests/test_sharing_handlers.py
  47. +20 −16 qiita_pet/handlers/api_proxy/artifact.py
  48. +38 −52 qiita_pet/handlers/api_proxy/prep_template.py
  49. +62 −62 qiita_pet/handlers/api_proxy/sample_template.py
  50. +44 −14 qiita_pet/handlers/api_proxy/studies.py
  51. +1 −1 qiita_pet/handlers/api_proxy/tests/test_artifact.py
  52. +6 −10 qiita_pet/handlers/api_proxy/tests/test_prep_template.py
  53. +25 −51 qiita_pet/handlers/api_proxy/tests/test_sample_template.py
  54. +4 −35 qiita_pet/handlers/api_proxy/tests/test_studies.py
  55. +17 −10 qiita_pet/handlers/artifact_handlers/base_handlers.py
  56. +16 −4 qiita_pet/handlers/artifact_handlers/tests/test_base_handlers.py
  57. +1 −3 qiita_pet/handlers/auth_handlers.py
  58. +201 −136 qiita_pet/handlers/download.py
  59. +124 −0 qiita_pet/handlers/qiita_redbiom.py
  60. +1 −2 qiita_pet/handlers/stats.py
  61. +6 −0 qiita_pet/handlers/study_handlers/base.py
  62. +24 −21 qiita_pet/handlers/study_handlers/ebi_handlers.py
  63. +5 −5 qiita_pet/handlers/study_handlers/listing_handlers.py
  64. +0 −12 qiita_pet/handlers/study_handlers/tests/test_base.py
  65. +26 −2 qiita_pet/handlers/study_handlers/tests/test_listing_handlers.py
  66. +3 −7 qiita_pet/handlers/study_handlers/tests/test_sample_template.py
  67. +20 −20 qiita_pet/handlers/study_handlers/vamps_handlers.py
  68. +1 −1 qiita_pet/handlers/websocket_handlers.py
  69. +0 −7 qiita_pet/static/css/style.css
  70. +225 −37 qiita_pet/static/js/qiita.js
  71. +1 −1 qiita_pet/support_files/doc/source/tutorials/prepare-information-files.rst
  72. +4 −4 qiita_pet/templates/analysis_description.html
  73. +7 −8 qiita_pet/templates/analysis_selected.html
  74. +0 −17 qiita_pet/templates/analysis_waiting.html
  75. +16 −1 qiita_pet/templates/artifact_ajax/artifact_summary.html
  76. +1 −28 qiita_pet/templates/list_analyses.html
  77. +2 −65 qiita_pet/templates/list_studies.html
  78. +285 −0 qiita_pet/templates/redbiom.html
  79. +51 −14 qiita_pet/templates/sitebase.html
  80. +4 −0 qiita_pet/templates/study_ajax/base_info.html
  81. +3 −1 qiita_pet/templates/study_ajax/prep_summary.html
  82. +24 −38 qiita_pet/templates/study_base.html
  83. +0 −220 qiita_pet/templates/study_description_templates/prep_template_info_tab.html
  84. +0 −82 qiita_pet/templates/study_description_templates/prep_template_tab.html
  85. +1 −1 qiita_pet/templates/upload.html
  86. +1 −1 qiita_pet/test/rest/test_base.py
  87. +106 −3 qiita_pet/test/test_download.py
  88. +2 −3 qiita_pet/test/test_prep_template.py
  89. +153 −0 qiita_pet/test/test_qiita_redbiom.py
  90. +1 −1 qiita_pet/test/test_user_handlers.py
  91. +2 −0 qiita_pet/test/tornado_test_base.py
  92. +4 −6 qiita_pet/uimodules/__init__.py
  93. +2 −194 qiita_pet/uimodules/prep_template_tab.py
  94. +10 −10 qiita_pet/webserver.py
  95. +1 −1 qiita_ware/commands.py
  96. +0 −303 qiita_ware/context.py
  97. +0 −324 qiita_ware/dispatchable.py
  98. +99 −37 qiita_ware/ebi.py
  99. +0 −101 qiita_ware/executor.py
  100. +373 −0 qiita_ware/private_plugin.py
  101. +0 −189 qiita_ware/test/test_dispatchable.py
  102. +136 −10 qiita_ware/test/test_ebi.py
  103. +412 −0 qiita_ware/test/test_private_plugin.py
  104. +0 −420 qiita_ware/test/test_util.py
  105. +0 −154 qiita_ware/util.py
  106. +0 −203 qiita_ware/wrapper.py
  107. +3 −9 scripts/qiita
  108. +2 −61 scripts/qiita-env
  109. +0 −28 scripts/qiita-private
  110. +2 −2 scripts/qiita-private-plugin
  111. +39 −46 scripts/qiita-test-install
  112. +8 −6 setup.py
View
@@ -58,6 +58,5 @@ gg_13_8-*
# sphinx documentation
qiita_pet/static/doc/
# moi static files
qiita_pet/static/vendor/js/moi.js
qiita_pet/static/vendor/js/moi_list.js
# webdis log
webdis.log
View
@@ -1,3 +1,4 @@
dist: precise
language: python
sudo: false
env:
@@ -6,10 +7,10 @@ env:
matrix:
- TEST_ADD_STUDIES=False COVER_PACKAGE=qiita_db
- TEST_ADD_STUDIES=False COVER_PACKAGE=qiita_pet
- TEST_ADD_STUDIES=False COVER_PACKAGE="qiita_core qiita_ware"
- TEST_ADD_STUDIES=True
- TEST_ADD_STUDIES=True COVER_PACKAGE="qiita_core qiita_ware"
before_install:
- redis-server --version
- redis-server --port 7777 &
- wget http://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh -O miniconda.sh
- chmod +x miniconda.sh
- ./miniconda.sh -b
@@ -27,43 +28,54 @@ install:
# install a few of the dependencies that pip would otherwise try to install
# when intalling scikit-bio
- travis_retry conda create --yes -n qiita python=$PYTHON_VERSION pip nose flake8
pyzmq networkx pyparsing natsort mock future libgfortran seaborn
pyzmq networkx pyparsing natsort mock future libgfortran seaborn nltk
'pandas>=0.18' 'matplotlib>=1.1.0' 'scipy>0.13.0' 'numpy>=1.7' 'h5py>=2.3.1'
- source activate qiita
- pip install -U pip
- pip install sphinx sphinx-bootstrap-theme 'ipython[all]==2.4.1' nose-timer codecov
- travis_retry pip install . --process-dependency-links
- pip install sphinx sphinx-bootstrap-theme nose-timer codecov
- 'echo "backend: Agg" > matplotlibrc'
- git clone https://github.com/nicolasff/webdis
- pushd webdis
- make
- ./webdis &
- popd
- travis_retry pip install . --process-dependency-links
# Install the biom plugin so we can run the analysis tests
- pip install https://github.com/qiita-spots/qiita_client/archive/master.zip
- pip install https://github.com/qiita-spots/qtp-biom/archive/master.zip --process-dependency-links
- export QIITA_SERVER_CERT=`pwd`/qiita_core/support_files/server.crt
# loading redbiom with Qiita's test set
# but first let's make sure redis is empty
# following https://github.com/biocore/redbiom/blob/master/Makefile
- export REDBIOM_HOST=http://127.0.0.1:7379
- curl -s http://127.0.0.1:7379/FLUSHALL > /dev/null
- redbiom admin scripts-writable
- redbiom admin create-context --name "qiita-test" --description "qiita-test context"
- redbiom admin load-sample-metadata --metadata `pwd`/qiita_db/support_files/test_data/templates/1_19700101-000000.txt
- redbiom admin load-sample-metadata-search --metadata `pwd`/qiita_db/support_files/test_data/templates/1_19700101-000000.txt
- redbiom admin load-sample-data --table `pwd`/qiita_db/support_files/test_data/processed_data/1_study_1001_closed_reference_otu_table.biom --context qiita-test --tag 4
- redbiom admin load-sample-data --table `pwd`/qiita_db/support_files/test_data/processed_data/1_study_1001_closed_reference_otu_table-for_redbiom_tests.biom --context qiita-test --tag 5
- mkdir ~/.qiita_plugins
- export REDBIOM_HOST=http://127.0.0.1:7379
- cp $PWD/qiita_core/support_files/BIOM\ type_2.1.4.conf ~/.qiita_plugins
before_script:
# Some of the tests rely on the plugin system to complete successfuly.
# Thus, we need a qiita webserver running to be able to execute the tests.
- export MOI_CONFIG_FP=`pwd`/qiita_core/support_files/config_test.cfg
# EBI, see the end of before_install about why this block is commented out
# - if [ ${TRAVIS_PULL_REQUEST} == "false" ]; then
# export QIITA_CONFIG_FP=`pwd`/qiita_core/support_files/config_test_travis.cfg;
# export MOI_CONFIG_FP=`pwd`/qiita_core/support_files/config_test_travis.cfg;
# fi
- ipython profile create qiita-general --parallel
- qiita-env start_cluster qiita-general
- qiita-env make --no-load-ontologies
- |
if [ ${TEST_ADD_STUDIES} == "False" ]; then
qiita pet webserver --no-build-docs start &
fi
- qiita-test-install
script:
# Some of the tests rely on the plugin system to complete successfuly.
# Thus, we need a qiita webserver running to be able to execute the tests.
- qiita pet webserver --no-build-docs start &
- sleep 5
- QIITA_PID=$!
- nosetests $COVER_PACKAGE --with-doctest --with-coverage --with-timer -v --cover-package=$COVER_PACKAGE
- kill $QIITA_PID
- if [ ${TEST_ADD_STUDIES} == "True" ]; then test_data_studies/commands.sh ; fi
- if [ ${TEST_ADD_STUDIES} == "True" ]; then qiita-cron-job ; fi
- if [ ${TEST_ADD_STUDIES} == "False" ]; then qiita-test-install ; fi
- if [ ${TEST_ADD_STUDIES} == "False" ]; then nosetests $COVER_PACKAGE --with-doctest --with-coverage --with-timer -v --cover-package=$COVER_PACKAGE; fi
- flake8 qiita_* setup.py scripts/*
- ls -R /home/travis/miniconda3/envs/qiita/lib/python2.7/site-packages/qiita_pet/support_files/doc/
- qiita pet webserver
addons:
postgresql: "9.3"
View
@@ -1,10 +1,10 @@
#Contributing to Qiita
# Contributing to Qiita
Qiita is an open source software package, and we welcome community contributions. You can find the source code and test code for Qiita under public revision control in the Qiita git repository on [GitHub](http://github.com/biocore/qiita). We very much welcome contributions.
This document covers what you should do to get started with contributing to Qiita. You should read this whole document before considering submitting code to Qiita. This will save time for both you and the Qiita developers.
#General Notes on Development
# General Notes on Development
Adding source code to Qiita, can take place in three different modules:
@@ -17,7 +17,15 @@ always take into consideration how these new features affect users and whether
or not adding a new section or document to the documentation (found under the
`doc` folder) would be useful.
###The Qiita development rules
### Repository branch structure
The Qiita repository contains three branches:
* `master`: This branch reflects the code deployed in our [main Qiita server](http://qiita.microbio.me).
* `dev`: This branch is the active development branch. All new Pull Requests should be performed against this branch.
* `release-candidate`: This branch is used to freeze the code from the `dev` branch, so we can deploy in our test servers and exercise the code extensively before deploying in our main system. Code freezes typically occur one week before the scheduled deployment. Check our [milestones page](https://github.com/biocore/qiita/milestones) to see the scheduled deployments.
### The Qiita development rules
Since Qiita is a package that is continuously growing, we found ourselves in a position where development rules needed to be established so we can reduce both development and reviewer time. These rules are:
@@ -46,49 +54,47 @@ Since Qiita is a package that is continuously growing, we found ourselves in a p
9. Last but not least, you are working as part of a team and you should try to help others when possible.
###Configuration file
### Configuration file
The Qiita configuration file determines how the package interacts with your system’s resources (redis, postgres and the IPython cluster). Thus you should review the documentation detailed [here](https://docs.google.com/document/d/1u7kwLP31NM513-8xwpwvLbSQxYu0ehI6Jau1APR13e0/edit#), but especially bear in mind the following points:
The Qiita configuration file determines how the package interacts with your system’s resources (redis and postgres). Thus you should review the documentation detailed [here](https://docs.google.com/document/d/1u7kwLP31NM513-8xwpwvLbSQxYu0ehI6Jau1APR13e0/edit#), but especially bear in mind the following points:
* An example version of this file can be found here `qiita_core/support_files/qiita_config.txt` and if you don’t set a `QIITA_CONFIG_FP` environment variable, that’s the file that Qiita will use.
* The `[main]` section sets a `TEST_ENVIRONMENT` variable, which determines whether your system will be running unit tests or if it a demo/production system. You will want to set the value to TRUE if you are running the unit tests.
**A note on data accumulation**: Qiita keeps data in the `BASE_DATA_DIR` as the system gets used. When you drop a Qiita environment and create a fresh testing environment, the “old” data that was generated from the previous environment should be **manually** deleted (or, at least, removed from the data directories in the `BASE_DATA_DIR`).
###Unit tests
### Unit tests
Unit tests in Qiita are located inside the tests/test folder of every sub-module, for example `qiita_db/test/test_metadata_template.py`. These can be executed on a per-file basis or using `nosetests` from the base directory.
During test creation make sure the test class is decorated with `@qiita_test_checker()` if database modifications are done during tests. This will automatically drop and rebuild the qiita schema after the entire test class has been executed. This requires to all the tests in a single class be independent of each other, so stochastic failures do not occur due to different test order execution.
Coverage testing is in effect, so run tests using `nosetests --with-coverage [test_file.py]` to check what lines of new code in your pull request are not tested.
###Documentation
### Documentation
The documentation for Qiita is maintained as part of this repository, under the
`qiita_pet/support_files/doc` folder, for more information, see the README.md
file in `qiita_pet/support_files/doc/README.md`.
###Scripts
### Scripts
Scripts in Qiita are located inside the scripts directory, their actions will rely on the settings described in the Qiita config file, for example if you are dropping a database, the database that will be dropped is the one described by the `DATABASE` setting. The following is a list of the most commonly used commands during development:
* `qiita-env make` will create a new environment (as specified by the Qiita config file).
* `qiita-env drop` will delete the environment (as specified by the Qiita config file).
* `qiita-env start_cluster qiita-general`, starts an IPython cluster named ‘qiita-general’. Normally you’ll want to wait a few seconds for the engines to start and become responsive (30-40 seconds depending on your system).
* `qiita-env stop_cluster qiita-general`, terminates a cluster named ‘qiita-general’.
* `qiita pet webserver start`, will start the Qiita web-application running on port 21174, you can change this using the `--port` flag, for example `--port=7532`.
##Making Database Changes
## Making Database Changes
After the initial production release of Qiita, changes to the database schema will require patches; the database can no longer be dropped and recreated using the most recent schema because all the data would be lost! Therefore, patches must be applied instead.
###Approach
### Approach
1. We keep "unpatched" versions of the SQL and DBS files in the repository
2. We keep fully patched versions of the DBS and HTML files in the repository
3. We keep a patch file for each patch as required in the `qiita_db/support_files/patches` directory. Note that **the patches will be applied in order based on the natural sort order of their filename** (e.g., `2.sql` will be applied before `10.sql`, and `10.sql` will be applied before `a.sql`)
###Developer Workflow
### Developer Workflow
1. Load the fully patched DBS file (e.g., `qiita-db.dbs`) in [DBSchema](http://www.dbschema.com/)
2. Make desired changes
@@ -101,17 +107,17 @@ After the initial production release of Qiita, changes to the database schema wi
One drawback is that developers will need to have [DBSchema](http://www.dbschema.com/) to develop for this project.
###Data Patches
### Data Patches
If you need to submit a patch that changes only data but does not alter the schema, you should still create a patch file with the next name (e.g., `2.sql`) with your changes. Note that a patch should *not* be created if the modifications do not apply to Qiita databases in general; data patches are only necessary in some cases, e.g., if the terms in an ontology change.
###Python Patches
### Python Patches
Occasionally, SQL alone cannot effect the desired changes, and a corresponding python script must be run after the SQL patch is applied. If this is the case, a python file should be created in the `patches/python_patches` directory, and it should have the same basename as the SQL file. For example, if there is a patch `4.sql` in the `patches` directory, and this patch requires a python script be run after the SQL is applied, then the python file should be placed at `patches/python_patches/4.py`. Note that not every SQL patch will have a corresponding python patch, but every python patch will have a corresponding SQL patch.
If in the future we discover a use-case where a python patch must be applied for which there *is no corresponding SQL patch*, then a blank SQL patch file will still need to be created.
##SQL coding guidelines
## SQL coding guidelines
Since the `qiita_db` code contains a mixture of python code and SQL code, here are some coding guidelines to add SQL code to Qiita:
1. Any SQL keyword should be written uppercased:
View
@@ -60,6 +60,7 @@ Install the non-python dependencies
* [PostgreSQL](http://www.postgresql.org/download/) (minimum required version 9.3.5, we have tested most extensively with 9.3.6)
* [redis-server](http://redis.io) (we have tested most extensively with 2.8.17)
* [webdis] (https://github.com/nicolasff/webdis) (latest version should be fine but we have tested the most with 9ee6fe2 - Feb 6, 2016)
There are several options to install these dependencies depending on your needs:
@@ -87,6 +88,27 @@ brew update
brew install homebrew/versions/redis28
```
### webdis
Note that this is the only package that assumes that Qiita is already installed (due to library dependencies). Also, that the general suggestion is to have 2 redis servers running, one for webdis/redbiom and the other for Qiita. The reason for multiple redis servers is so that the redbiom cache can be flushed without impacting the operation of the qiita server itself.
The following instructions install, compile and pre-populates the redbiom redis DB so we assume that redis is running on the default port and that Qiita is fully installed as the redbiom package is installed with Qiita.
```
git clone https://github.com/nicolasff/webdis
pushd webdis
make
./webdis &
popd
# note that this assumes that Qiita is already installed
fp=`python -c 'import qiita_db; print qiita_db.__file__'`
qdbd=`dirname $fp`
redbiom admin scripts-writable
redbiom admin create-context --name "qiita-test" --description "qiita-test context"
redbiom admin load-sample-metadata --metadata ${qdbd}/support_files/test_data/templates/1_19700101-000000.txt
redbiom admin load-sample-metadata-search --metadata ${qdbd}/support_files/test_data/templates/1_19700101-000000.txt
redbiom admin load-sample-data --table ${qdbd}/support_files/test_data/processed_data/1_study_1001_closed_reference_otu_table.biom --context qiita-test --tag 1
```
Install Qiita development version and its python dependencies
-------------------------------------------------------------
@@ -110,11 +132,6 @@ Install Qiita (this occurs through setuptools' `setup.py` file in the qiita dire
pip install -e . --process-dependency-links
```
Install the development version of moi:
```bash
pip install https://github.com/biocore/mustached-octo-ironman/archive/master.zip --no-deps
```
At this point, Qiita will be installed and the system will start. However,
you will need to install plugins in order to process any kind of data. For a list
of available plugins, visit the [Qiita Spots](https://github.com/qiita-spots)
@@ -145,22 +162,22 @@ Set your `QIITA_CONFIG_FP` environment variable to point to that file (into `.ba
```bash
echo "export QIITA_CONFIG_FP=$HOME/.qiita_config_test.cfg" >> ~/.bashrc
echo "export MOI_CONFIG_FP=$HOME/.qiita_config_test.cfg" >> ~/.bashrc
source ~/.bashrc
# Re-enable conda environment for qiita
source activate qiita
```
Setup ipython profile for qiita:
Next, make a test environment:
```bash
ipython profile create qiita-general --parallel
qiita-env make --no-load-ontologies
```
Next, make a test environment:
Finally, redbiom relies on the REDBIOM_HOST environment variable to set the URL to query. By default is set to Qiita redbiom public repository. To change it you could do:
```bash
qiita-env make --no-load-ontologies
export REDBIOM_HOST=http://my_host.com:7379
```
## Start Qiita
@@ -173,12 +190,6 @@ Next, start redis server (the command may differ depending on your operating sys
redis-server
```
Start the IPython cluster:
```bash
qiita-env start_cluster qiita-general && sleep 30
```
Start the qiita server:
```bash
@@ -58,18 +58,6 @@ class ConfigurationManager(object):
The host where the database lives
port : int
The port used to connect to the postgres database in the previous host
ipyc_demo : str
The IPython demo cluster profile
ipyc_demo_n : int
The size of the demo cluster
ipyc_reserved : str
The IPython reserved cluster profile
ipyc_reserved_n : int
The size of the reserved cluster
ipyc_general : str
The IPython general cluster profile
ipyc_general_n : int
The size of the general cluster
smtp_host : str
The SMTP host from which mail will be sent
smtp_port : int
@@ -145,7 +133,7 @@ def __init__(self):
config.readfp(conf_file)
_required_sections = {'main', 'redis', 'postgres', 'smtp', 'ebi',
'ipython', 'portal'}
'portal'}
if not _required_sections.issubset(set(config.sections())):
missing = _required_sections - set(config.sections())
raise MissingConfigSection(', '.join(missing))
@@ -155,7 +143,6 @@ def __init__(self):
self._get_postgres(config)
self._get_redis(config)
self._get_ebi(config)
self._get_ipython(config)
self._get_vamps(config)
self._get_portal(config)
@@ -283,10 +270,6 @@ def _get_ebi(self, config):
self.ebi_center_name = sec_get('EBI_CENTER_NAME')
self.ebi_organization_prefix = sec_get('EBI_ORGANIZATION_PREFIX')
def _get_ipython(self, config):
self.ipython_contexts = config.get('ipython', 'context').split(',')
self.ipython_default = config.get('ipython', 'default')
def _get_vamps(self, config):
self.vamps_user = config.get('vamps', 'USER')
self.vamps_pass = config.get('vamps', 'PASSWORD')
Oops, something went wrong.

0 comments on commit 5b54aa7

Please sign in to comment.