alanorth/dspace-statistics-api
1
0
Fork 0
mirror of https://github.com/ilri/dspace-statistics-api.git synced 2024-06-09 13:25:09 +02:00
Code Releases Activity
3197b79578
dspace-statistics-api/Pipfile.lock

312 lines
14 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": {
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256": "97e81a39aace7e0a0436f569e583c9c430aaccd6fc3a5e0169c78c9fa57e5e5e"
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.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"python_version": "3.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
},
"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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:e4f3620cfea4f83eedc95b24abd9cd56f3c4b146dd0177e83a21b4eb49e21e50",
"sha256:fd7c7c74727ddcf00e9acd26bba8da604ffec95bf1c2144e67aff7a8b50e6cef"
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==2019.9.11"
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
},
"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": [
Pipfile.lock: run pipenv update Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"sha256:1904bb2b8a43658807108d59c3f3d56c2b6121a701161de0ddf9ad140073c626",
"sha256:cd4a810dd51bf497552cf3f863b575dabd73d6ad6a91075b65936b151cbf4f9c"
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.lock: run pipenv update Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"version": "==20.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
},
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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:040234f8a4a8dfd692662a8308d78f63f31a97e1c42d2480e5e6810c48966a29",
"sha256:086f7e89ec85a6704db51f68f0dcae432eff9300809723a6e8782c41c2f48e03",
"sha256:18ca813fdb17bc1db73fe61b196b05dd1ca2165b884dd5ec5568877cabf9b039",
"sha256:19dc39616850342a2a6db70559af55b22955f86667b5f652f40c0e99253d9881",
"sha256:2166e770cb98f02ed5ee2b0b569d40db26788e0bf2ec3ae1a0d864ea6f1d8309",
"sha256:3a2522b1d9178575acee4adf8fd9f979f9c0449b00b4164bb63c3475ea6528ed",
"sha256:3aa773580f85a28ffdf6f862e59cb5a3cc7ef6885121f2de3fca8d6ada4dbf3b",
"sha256:3b5deaa3ee7180585a296af33e14c9b18c218d148e735c7accf78130765a47e3",
"sha256:407af6d7e46593415f216c7f56ba087a9a42bd6dc2ecb86028760aa45b802bd7",
"sha256:4c3c09fb674401f630626310bcaf6cd6285daf0d5e4c26d6e55ca26a2734e39b",
"sha256:4c6717962247445b4f9e21c962ea61d2e884fc17df5ddf5e35863b016f8a1f03",
"sha256:50446fae5681fc99f87e505d4e77c9407e683ab60c555ec302f9ac9bffa61103",
"sha256:5057669b6a66aa9ca118a2a860159f0ee3acf837eda937bdd2a64f3431361a2d",
"sha256:5dd90c5438b4f935c9d01fcbad3620253da89d19c1f5fca9158646407ed7df35",
"sha256:659c815b5b8e2a55193ede2795c1e2349b8011497310bb936da7d4745652823b",
"sha256:69b13fdf12878b10dc6003acc8d0abf3ad93e79813fd5f3812497c1c9fb9be49",
"sha256:7a1cb80e35e1ccea3e11a48afe65d38744a0e0bde88795cc56a4d05b6e4f9d70",
"sha256:7e6e3c52e6732c219c07bd97fff6c088f8df4dae3b79752ee3a817e6f32e177e",
"sha256:7f42a8490c4fe854325504ce7a6e4796b207960dabb2cbafe3c3959cb00d1d7e",
"sha256:84156313f258eafff716b2961644a4483a9be44a5d43551d554844d15d4d224e",
"sha256:8578d6b8192e4c805e85f187bc530d0f52ba86c39172e61cd51f68fddd648103",
"sha256:890167d5091279a27e2505ff0e1fb273f8c48c41d35c5b92adbf4af80e6b2ed6",
"sha256:98e10634792ac0e9e7a92a76b4991b44c2325d3e7798270a808407355e7bb0a1",
"sha256:9aadff9032e967865f9778485571e93908d27dab21d0fdfdec0ca779bb6f8ad9",
"sha256:9f24f383a298a0c0f9b3113b982e21751a8ecde6615494a3f1470eb4a9d70e9e",
"sha256:a73021b44813b5c84eda4a3af5826dd72356a900bac9bd9dd1f0f81ee1c22c2f",
"sha256:afd96845e12638d2c44d213d4810a08f4dc4a563f9a98204b7428e567014b1cd",
"sha256:b73ddf033d8cd4cc9dfed6324b1ad2a89ba52c410ef6877998422fcb9c23e3a8",
"sha256:b8f490f5fad1767a1331df1259763b3bad7d7af12a75b950c2843ba319b2415f",
"sha256:dbc5cd56fff1a6152ca59445178652756f4e509f672e49ccdf3d79c1043113a4",
"sha256:eac8a3499754790187bb00574ab980df13e754777d346f85e0ff6df929bcd964",
"sha256:eaed1c65f461a959284649e37b5051224f4db6ebdc84e40b5e65f2986f101a08"
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",
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==2.8.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
},
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
"requests": {
"hashes": [
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"sha256:11e007a8a2aa0323f5a921e9e6a2d7e4e67d9877e85773fba9ba6419025cbeb4",
"sha256:9cf5292fcd0f598c671cfc1e0d7d1a7f13bb8085e9a590f48c010551dc6c4b31"
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
],
"index": "pypi",
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"version": "==2.22.0"
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
},
"urllib3": {
"hashes": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:a8a318824cc77d1fd4b2bec2ded92646630d7fe8619497b142c84a9e6f5a7293",
"sha256:f3c5fd51747d450d4dcf6f923c81f78f811aab8205fda64b0aba34a4e48b0745"
CHANGELOG.md: Add notes about Python updates
2019-04-15 09:30:29 +02:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==1.25.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
}
},
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
"attrs": {
"hashes": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:08a96c641c3a74e44eb59afb61a24f2cb9f4d7188748e76ba4bb5edfa3cb7d1c",
"sha256:f7b7ce16570fe9965acd6d30101a28f62fb4a7f9e926b3bbc9b61f8b04247e72"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==19.3.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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:54c38050039232e1db4ad7375cfce6748d7b41c29e95a081c8a6d2c30364a2ce",
"sha256:5d19b92a3c8f7f101c8dd86afd86b0f061a8ce4540ab8cd401fa2542756bce6d"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==4.4.1"
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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:45681a117ecc81e870cbf1262835ae4af5e7a8b08e40b944a8a6e6b895914cfb",
"sha256:49356e766643ad15072a789a20915d3c91dc89fd313ccd71802303fd67e4deca"
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",
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==3.7.9"
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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:dfd303b270b7b5232b3d08bd30ec6fd685d8a58cabd54055e3d69d8f029f7280",
"sha256:ed7ebe1cba899c1c3ccad6f7f1c2d2369464cc77dba8eebc65e2043e19cda995"
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",
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==7.9.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 This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"sha256:786b6c3d80e2f06fd77162a07fed81b8baa22dde5d62896a790a331d6ac21a27",
"sha256:ba859c74fa3c966a22f2aeebe1b74ee27e2a462f56d3f5f7ca4a59af61bfe42e"
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 This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"version": "==0.15.1"
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": [
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"sha256:409cd48d4db7052af495b09dec721011634af3753ae1ef92d2b32f73a745f832",
"sha256:92b8c4b06dac4f0611c0729b2f2ede52b2e1bac1ab48f089c7ddc12e26bb60c4"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"version": "==7.2.0"
},
"packaging": {
"hashes": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:28b924174df7a2fa32c1953825ff29c61e2f5e082343165438812f00d3a7fc47",
"sha256:d9551545c6d761f3def1677baf08ab2a3ca17c56879e70fecba2fc4dde4ed108"
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==19.2"
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": [
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"sha256:63854233e1fadb5da97f2744b6b24346d2750b85965e7e399bec1620232797dc",
"sha256:666b0ee4a7a1220f65d367617f2cd3ffddff3e205f3f16a0284df30e774c2a9c"
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 This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
"version": "==0.5.1"
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 Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"sha256:15b2acde666561e1298d71b523007ed7364de07029219b604cf808bfa1c765b0",
"sha256:966c145cd83c96502c3c3868f50408687b38434af77734af1e9ca461a4081d2d"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
Pipfile.lock: run pipenv update Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"version": "==0.13.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
"prompt-toolkit": {
"hashes": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:46642344ce457641f28fc9d1c9ca939b63dadf8df128b86f1b9860e59c73a5e4",
"sha256:e7f8af9e3d70f514373bf41aa51bc33af12a6db3f71461ea47fea985defb2c31",
"sha256:f15af68f66e664eaa559d4ac8a928111eebd5feda0c11738b5998045224829db"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==2.0.10"
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: run pipenv update Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"sha256:83ec6c6133ca6b529b7ff5aa826328fd14b5bb02a58c37f4f06384e96a0f94ab",
"sha256:b7949de3d396836085fea596998b135a22610bbcc4f2abfe9e448e44cbc58388"
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 Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"version": "==2.5.1"
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
},
"pyparsing": {
"hashes": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:20f995ecd72f2a1f4bf6b072b63b22e2eb457836601e76d6e5dfcd75436acc1f",
"sha256:4ca62001be367f01bd3e92ecbb79070272a9d4964dce6a48a82ff0b8bc7e683a"
Pipfile.lock: Run pipenv update This brings in, among others, psycogpg 2.8.3, requests 2.22.0, and pytest 5.1.1.
2019-08-28 23:30:06 +02:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==2.4.5"
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": [
Pipfile.lock: run pipenv update Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"sha256:63344a2e3bce2e4d522fd62b4fdebb647c019f1f9e4ca075debbd13219db4418",
"sha256:f67403f33b2b1d25a6756184077394167fe5e2f9d8bdaab30707d19ccec35427"
Add pytest to pipenv development packages
2018-11-11 10:52:58 +01:00
],
"index": "pypi",
Pipfile.lock: run pipenv update Brings gunicorn 20.0.4, pytest 5.3.1, and others. I hadn't noticed that gunicorn was bumped from 19.x.x to 20.x.x last week. See: https://docs.gunicorn.org/en/stable/news.html#id6
2019-11-27 10:06:13 +01:00
"version": "==5.3.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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:1f1b7d42e254082a9db6279deae68afb421ceba6158efa6131de7b3003ee93fd",
"sha256:30f610279e8b2578cab6db20741130331735c781b56053c59c4076da27f06b66"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==1.13.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": [
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"sha256:70b4c6a1d9019d7b4f6846832288f86998aa3b9207c6821f3578a6a6a467fe44",
"sha256:d023ee369ddd2763310e4c3eae1ff649689440d4ae59d7485eb4cfbbe3e359f7"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
],
Use Python 3.8.0 for pipenv Python 3.8.0 was released several months ago and has made it into Arch Linux's core repositories so it's time to start moving.
2019-11-14 23:38:45 +01:00
"version": "==4.3.3"
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively.
2018-11-07 16:07:14 +01:00
},
"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