alanorth/dspace-statistics-api
1
0
Fork 0
mirror of https://github.com/ilri/dspace-statistics-api.git synced 2024-11-22 22:35:06 +01:00
Code Releases Activity
af80c4b447
dspace-statistics-api/Pipfile.lock

302 lines
13 KiB
Plaintext
Raw Normal View History

Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
{
"_meta": {
"hash": {
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"sha256": "b0152688b12e9a7d176f42fd1940613deedc79e6a561edc1d86ed9248cbe4255"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
},
"pipfile-spec": 6,
"requires": {
Use Python 3.7 for pipenv Now that I'm only using pipenv locally it shouldn't create problems for people. They can still just create a vanilla virtualenv and use pip to install the dependencies.
2018-11-12 07:54:54 +01:00
"python_version": "3.7"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
},
"sources": [
{
"name": "pypi",
"url": "https://pypi.org/simple",
"verify_ssl": true
}
]
},
"default": {
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"certifi": {
"hashes": [
"sha256:59b7658e26ca9c7339e00f8f4636cdfe59d34fa37b9b04f6f9e9926b3cece1a5",
"sha256:b26104d6835d1f5e49452a26eb2ff87fe7090b89dfcaee5ea2212697e1e1d7ae"
],
"version": "==2019.3.9"
},
"chardet": {
"hashes": [
"sha256:84ab92ed1c4d4f16916e05906b6b75a6c0fb5db821cc65e70cbd64a3e2a5eaae",
"sha256:fc323ffcaeaed0e0a02bf4d117757b98aed530d9ed4531e3e15460124c106691"
],
"version": "==3.0.4"
},
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
"falcon": {
"hashes": [
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"sha256:18157af2a4fc3feedf2b5dcc6196f448639acf01c68bc33d4d5a04c3ef87f494",
"sha256:24adcd2b29a8ffa9d552dc79638cd21736a3fb04eda7d102c6cebafdaadb88ad",
"sha256:54f2cb4b687035b2a03206dbfc538055cc48b59a953187b0458aa1b574d47b53",
"sha256:59d1e8c993b9a37ea06df9d72cf907a46cc8063b30717cdac2f34d1658b6f936",
"sha256:733033ec80c896e30a43ab3e776856096836787197a44eb21022320a61311983",
"sha256:74cf1d18207381c665b9e6292d65100ce146d958707793174b03869dc6e614f4",
"sha256:95bf6ce986c1119aef12c9b348f4dee9c6dcc58391bdd0bc2b0bf353c2b15986",
"sha256:9712975adcf8c6e12876239085ad757b8fdeba223d46d23daef82b47658f83a9",
"sha256:a5ebb22a04c9cc65081938ee7651b4e3b4d2a28522ea8ec04c7bdd2b3e9e8cd8",
"sha256:aa184895d1ad4573fbfaaf803563d02f019ebdf4790e41cc568a330607eae439",
"sha256:e3782b7b92fefd46a6ad1fd8fe63fe6c6f1b7740a95ca56957f48d1aee34b357",
"sha256:e9efa0791b5d9f9dd9689015ea6bce0a27fcd5ecbcd30e6d940bffa4f7f03389",
"sha256:eea593cf466b9c126ce667f6d30503624ef24459f118c75594a69353b6c3d5fc",
"sha256:f93351459f110b4c1ee28556aef9a791832df6f910bea7b3f616109d534df06b"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
],
"index": "pypi",
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"version": "==2.0.0"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
},
"gunicorn": {
"hashes": [
"sha256:aa8e0b40b4157b36a5df5e599f45c9c76d6af43845ba3b3b0efe2c70473c2471",
"sha256:fa2662097c66f920f53f70621c6c58ca4a3c4d3434205e608e121b5b3b71f4f3"
],
"index": "pypi",
"version": "==19.9.0"
},
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"idna": {
"hashes": [
"sha256:c357b3f628cf53ae2c4c05627ecc484553142ca23264e593d327bcde5e9c3407",
"sha256:ea8b7f6188e6fa117537c3df7da9fc686d485087abf6ac197f9c46432f7e4a3c"
],
"version": "==2.8"
},
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
"psycopg2-binary": {
"hashes": [
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"sha256:007ca0df127b1862fc010125bc4100b7a630efc6841047bd11afceadb4754611",
"sha256:03c49e02adf0b4d68f422fdbd98f7a7c547beb27e99a75ed02298f85cb48406a",
"sha256:0a1232cdd314e08848825edda06600455ad2a7adaa463ebfb12ece2d09f3370e",
"sha256:131c80d0958c89273d9720b9adf9df1d7600bb3120e16019a7389ab15b079af5",
"sha256:2de34cc3b775724623f86617d2601308083176a495f5b2efc2bbb0da154f483a",
"sha256:2eddc31500f73544a2a54123d4c4b249c3c711d31e64deddb0890982ea37397a",
"sha256:484f6c62bdc166ee0e5be3aa831120423bf399786d1f3b0304526c86180fbc0b",
"sha256:4c2d9369ed40b4a44a8ccd6bc3a7db6272b8314812d2d1091f95c4c836d92e06",
"sha256:70f570b5fa44413b9f30dbc053d17ef3ce6a4100147a10822f8662e58d473656",
"sha256:7a2b5b095f3bd733aab101c89c0e1a3f0dfb4ebdc26f6374805c086ffe29d5b2",
"sha256:804914a669186e2843c1f7fbe12b55aad1b36d40a28274abe6027deffad9433d",
"sha256:8520c03172da18345d012949a53617a963e0191ccb3c666f23276d5326af27b5",
"sha256:90da901fc33ea393fc644607e4a3916b509387e9339ec6ebc7bfded45b7a0ae9",
"sha256:a582416ad123291a82c300d1d872bdc4136d69ad0b41d57dc5ca3df7ef8e3088",
"sha256:ac8c5e20309f4989c296d62cac20ee456b69c41fd1bc03829e27de23b6fa9dd0",
"sha256:b2cf82f55a619879f8557fdaae5cec7a294fac815e0087c4f67026fdf5259844",
"sha256:b59d6f8cfca2983d8fdbe457bf95d2192f7b7efdb2b483bf5fa4e8981b04e8b2",
"sha256:be08168197021d669b9964bd87628fa88f910b1be31e7010901070f2540c05fd",
"sha256:be0f952f1c365061041bad16e27e224e29615d4eb1fb5b7e7760a1d3d12b90b6",
"sha256:c1c9a33e46d7c12b9c96cf2d4349d783e3127163fd96254dcd44663cf0a1d438",
"sha256:d18c89957ac57dd2a2724ecfe9a759912d776f96ecabba23acb9ecbf5c731035",
"sha256:d7e7b0ff21f39433c50397e60bf0995d078802c591ca3b8d99857ea18a7496ee",
"sha256:da0929b2bf0d1f365345e5eb940d8713c1d516312e010135b14402e2a3d2404d",
"sha256:de24a4962e361c512d3e528ded6c7480eab24c655b8ca1f0b761d3b3650d2f07",
"sha256:e45f93ff3f7dae2202248cf413a87aeb330821bf76998b3cf374eda2fc893dd7",
"sha256:f046aeae1f7a845041b8661bb7a52449202b6c5d3fb59eb4724e7ca088811904",
"sha256:f1dc2b7b2748084b890f5d05b65a47cd03188824890e9a60818721fd492249fb",
"sha256:fcbe7cf3a786572b73d2cd5f34ed452a5f5fac47c9c9d1e0642c457a148f9f88"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
],
"index": "pypi",
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"version": "==2.8.2"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
},
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"requests": {
"hashes": [
"sha256:502a824f31acdacb3a35b6690b5fbf0bc41d63a24a45c4004352b0242707598e",
"sha256:7bf2a778576d825600030a110f3c0e3e8edc51dfaafe1c146e39a2027784957b"
],
"index": "pypi",
"version": "==2.21.0"
},
"urllib3": {
"hashes": [
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"sha256:2393a695cd12afedd0dcb26fe5d50d0cf248e5a66f75dbd89a3d4eb333a61af4",
"sha256:a637e5fae88995b256e3409dc4d52c2e2e0ba32c42a6365fee8bbd2238de3cfb"
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
],
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"version": "==1.24.3"
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
}
},
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
"develop": {
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
"atomicwrites": {
"hashes": [
Pipfile.lock: Run pipenv update
2019-02-07 16:03:36 +01:00
"sha256:03472c30eb2c5d1ba9227e4c2ca66ab8287fbfbbda3888aa93dc2e28fc6811b4",
"sha256:75a9445bac02d8d058d5e1fe689654ba5a6556a1dfd8ce6ec55a0ed79866cfa6"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: Run pipenv update
2019-02-07 16:03:36 +01:00
"version": "==1.3.0"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
},
"attrs": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:69c0dbf2ed392de1cb5ec704444b08a5ef81680a61cb899dc08127123af36a79",
"sha256:f0b870f674851ecbfbbbd364d6b5cbdff9dcedbc7f3f5e18a6891057f21fe399"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==19.1.0"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
},
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
"backcall": {
"hashes": [
"sha256:38ecd85be2c1e78f77fd91700c76e14667dc21e2713b63876c0eb901196e01e4",
"sha256:bbbf4b1e5cd2bdb08f915895b51081c041bac22394fdfcfdfbe9f14b77c08bf2"
],
"version": "==0.1.0"
},
"decorator": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:86156361c50488b84a3f148056ea716ca587df2f0de1d34750d35c21312725de",
"sha256:f069f3a01830ca754ba5258fde2278454a0b5b79e0d7f5c13b3b97e57d4acff6"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==4.4.0"
Pipfile.lock: Run pipenv update
2019-02-07 16:03:36 +01:00
},
"entrypoints": {
"hashes": [
"sha256:589f874b313739ad35be6e0cd7efde2a4e9b6fea91edcc34e58ecbb8dbe56d19",
"sha256:c70dd71abe5a8c85e55e12c19bd91ccfeec11a6e99044204511f9ed547d48451"
],
"version": "==0.3"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
"flake8": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:859996073f341f2670741b51ec1e67a01da142831aa1fdc6242dbf88dffbe661",
"sha256:a796a115208f5c03b18f332f7c11729812c8c3ded6c46319c59b53efd3819da8"
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
],
"index": "pypi",
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==3.7.7"
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
},
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
"ipython": {
"hashes": [
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"sha256:54c5a8aa1eadd269ac210b96923688ccf01ebb2d0f21c18c3c717909583579a8",
"sha256:e840810029224b56cd0d9e7719dc3b39cf84d577f8ac686547c8ba7a06eeab26"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
"index": "pypi",
Pipfile: Use falcon 2.0.0 See: https://github.com/falconry/falcon/releases/tag/2.0.0
2019-05-03 15:31:06 +02:00
"version": "==7.5.0"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"ipython-genutils": {
"hashes": [
"sha256:72dd37233799e619666c9f639a9da83c34013a73e8bbc79a7a6348d93c61fab8",
"sha256:eb2e116e75ecef9d4d228fdc66af54269afa26ab4463042e33785b887c628ba8"
],
"version": "==0.2.0"
},
"jedi": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:2bb0603e3506f708e792c7f4ad8fc2a7a9d9c2d292a358fbbd58da531695595b",
"sha256:2c6bcd9545c7d6440951b12b44d373479bf18123a401a52025cf98563fbd826c"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==0.13.3"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
"mccabe": {
"hashes": [
"sha256:ab8a6258860da4b6677da4bd2fe5dc2c659cff31b3ee4f7f5d64e79735b80d42",
"sha256:dd8d182285a0fe56bace7f45b5e7d1a6ebcbf524e8f3bd87eb0f125271b8831f"
],
"version": "==0.6.1"
},
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
"more-itertools": {
"hashes": [
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"sha256:2112d2ca570bb7c3e53ea1a35cd5df42bb0fd10c45f0fb97178679c3c03d64c7",
"sha256:c3e4748ba1aad8dba30a4886b0b1a2004f9a863837b8654e7059eebf727afa5a"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"markers": "python_version > '2.7'",
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"version": "==7.0.0"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
},
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
"parso": {
"hashes": [
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"sha256:17cc2d7a945eb42c3569d4564cdf49bde221bc2b552af3eca9c1aad517dcdd33",
"sha256:2e9574cb12e7112a87253e14e2c380ce312060269d04bd018478a3c92ea9a376"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"version": "==0.4.0"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"pexpect": {
"hashes": [
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"sha256:2094eefdfcf37a1fdbfb9aa090862c1a4878e5c7e0e7e7088bdb511c558e5cd1",
"sha256:9e2c1fd0e6ee3a49b28f95d4b33bc389c89b20af6a1255906e90ff1262ce62eb"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
"markers": "sys_platform != 'win32'",
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"version": "==4.7.0"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"pickleshare": {
"hashes": [
"sha256:87683d47965c1da65cdacaf31c8441d12b8044cdec9aca500cd78fc2c683afca",
"sha256:9649af414d74d4df115d5d718f82acb59c9d418196b7b4290ed47a12ce62df56"
],
"version": "==0.7.5"
},
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
"pluggy": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:19ecf9ce9db2fce065a7a0586e07cfb4ac8614fe96edf628a264b1c70116cf8f",
"sha256:84d306a647cc805219916e62aab89caa97a33a1dd8c342e87a37f91073cd4746"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==0.9.0"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
},
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
"prompt-toolkit": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:11adf3389a996a6d45cc277580d0d53e8a5afd281d0c9ec71b28e6f121463780",
"sha256:2519ad1d8038fd5fc8e770362237ad0364d16a7650fb5724af6997ed5515e3c1",
"sha256:977c6583ae813a37dc1c2e1b715892461fcbdaa57f6fc62f33a528c4886c8f55"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==2.0.9"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"ptyprocess": {
"hashes": [
"sha256:923f299cc5ad920c68f2bc0bc98b75b9f838b93b599941a6b63ddbc2476394c0",
"sha256:d7cc528d76e76342423ca640335bd3633420dc1366f258cb31d05e865ef5ca1f"
],
"version": "==0.6.0"
},
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
"py": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:64f65755aee5b381cea27766a3a147c3f15b9b6b9ac88676de66ba2ae36793fa",
"sha256:dc639b046a6e2cff5bbe40194ad65936d6ba360b52b3c3fe1d08a82dd50b5e53"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==1.8.0"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
},
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
"pycodestyle": {
"hashes": [
Pipfile.lock: Run pipenv update
2019-02-07 16:03:36 +01:00
"sha256:95a2219d12372f05704562a14ec30bc76b05a5b297b21a5dfe3f6fac3491ae56",
"sha256:e40a936c9a450ad81df37f549d676d127b1b66000a6c500caa2b085bc0ca976c"
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
],
Pipfile.lock: Run pipenv update
2019-02-07 16:03:36 +01:00
"version": "==2.5.0"
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
},
"pyflakes": {
"hashes": [
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"sha256:17dbeb2e3f4d772725c777fabc446d5634d1038f234e77343108ce445ea69ce0",
"sha256:d976835886f8c5b31d47970ed689944a0262b5f3afa00a5a7b4dc81e5449f8a2"
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
],
Pipfile.lock: run pipenv update
2019-03-17 21:46:39 +01:00
"version": "==2.1.1"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"pygments": {
"hashes": [
Pipfile.lock: update dependencies Updated with `pipenv update`.
2019-01-15 09:22:46 +01:00
"sha256:5ffada19f6203563680669ee7f53b64dabbeb100eb51b61996085e99c03b284a",
"sha256:e8218dd399a61674745138520d0d4cf2621d7e032439341bc3f647bff125818d"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Pipfile.lock: update dependencies Updated with `pipenv update`.
2019-01-15 09:22:46 +01:00
"version": "==2.3.1"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
"pytest": {
"hashes": [
Use falcon 2.0.0rc2
2019-04-18 09:04:43 +02:00
"sha256:3773f4c235918987d51daf1db66d51c99fac654c81d6f2f709a046ab446d5e5d",
"sha256:b7802283b70ca24d7119b32915efa7c409982f59913c1a6c0640aacf118b95f5"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
"index": "pypi",
Use falcon 2.0.0rc2
2019-04-18 09:04:43 +02:00
"version": "==4.4.1"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
},
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
"six": {
"hashes": [
Pipfile.lock: update dependencies Updated with `pipenv update`.
2019-01-15 09:22:46 +01:00
"sha256:3350809f0555b11f552448330d0b52d5f24c91a322ea4a15ef22629740f3761c",
"sha256:d16a0141ec1a18405cd4ce8b4613101da75da0e9a7aec5bdd4fa804d0e0eba73"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Pipfile.lock: update dependencies Updated with `pipenv update`.
2019-01-15 09:22:46 +01:00
"version": "==1.12.0"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"traitlets": {
"hashes": [
"sha256:9c4bd2d267b7153df9152698efb1050a5d84982d3384a37b2c1f7723ba3e7835",
"sha256:c6cb5e6f57c5a9bdaa40fa71ce7b4af30298fbab9ece9815b5d995ab6217c7d9"
],
"version": "==4.3.2"
},
"wcwidth": {
"hashes": [
"sha256:3df37372226d6e63e1b1e1eda15c594bca98a22d33a23832a90998faa96bc65e",
"sha256:f4ebe71925af7b40a864553f761ed559b43544f8f71746c2d756c7fe788ade7c"
],
"version": "==0.1.7"
Regenerate pipenv Uses 'kazoo-2.5.0' branch name for installing SolrClient instead of the commit hash and adds flake8 as a dev package. This means that I can track dependencies for production and development and still end up with a requirements.txt for produciton.
2018-11-04 14:55:28 +01:00
}
}
Add Pipfile for pipenv Eventually I'd like to be able to use pipenv instead of plain pip. For now I'll just keep using pipenv and generating requirements.txt like this: $ pipenv run pip freeze > requirements.txt Then I can kinda have the best of both worlds, where I use pipenv on my local machine and pip with requirements.txt on the server.
2018-11-04 14:35:47 +01:00
}
Copy Permalink