dspace-statistics-api/Pipfile

[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
gunicorn = "*"
falcon = "*"
"psycopg2-binary" = "*"
requests = "*"

[dev-packages]
ipython = "*"
"flake8" = "*"
pytest = "*"

[requires]
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			`[[source]]`
			`url = "https://pypi.org/simple"`
			`verify_ssl = true`
			`name = "pypi"`

			`[packages]`
Re-create pipenv environment from scratch When I originally created the pipenv environment I used the standard pip requirements.txt that I already had, which captured all the mod- ules and their exact versions at the time. This makes it hard to se- parate the project's actual dependencies from the dependencies' dep- endencies, complicating the Pipfile and making it hard to update mo- dule versions later. I've re-created the environment with the following commands: $ pipenv install gunicorn falcon psycopg2-binary git+https://github.com/alanorth/SolrClient.git@kazoo-2.5.0#egg=SolrClient $ pipenv install --dev ipython flake8 pytest 2018-11-14 08:07:32 +01:00			`gunicorn = "*"`
			`falcon = "*"`
			`"psycopg2-binary" = "*"`
Refactor to use vanilla requests library The SolrClient library is unmaintained, which is starting to cause problems due to the moving Python ecosystem. Switching to requests does not change my code in any meaningful way and makes maintenance easier. 2019-04-15 09:19:50 +02:00			`requests = "*"`
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
			`[dev-packages]`
Add ipython to pipenv dev packages This is very useful for debugging Python code interactively. 2018-11-07 16:07:14 +01:00			`ipython = "*"`
Re-create pipenv environment from scratch When I originally created the pipenv environment I used the standard pip requirements.txt that I already had, which captured all the mod- ules and their exact versions at the time. This makes it hard to se- parate the project's actual dependencies from the dependencies' dep- endencies, complicating the Pipfile and making it hard to update mo- dule versions later. I've re-created the environment with the following commands: $ pipenv install gunicorn falcon psycopg2-binary git+https://github.com/alanorth/SolrClient.git@kazoo-2.5.0#egg=SolrClient $ pipenv install --dev ipython flake8 pytest 2018-11-14 08:07:32 +01:00			`"flake8" = "*"`
Add pytest to pipenv development packages 2018-11-11 10:52:58 +01:00			`pytest = "*"`
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
			`[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"`