19 Commits

Author	SHA1	Message	Date
Alan Orth	494548c691	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-15 00:38:45 +02:00
Alan Orth	b8f379e7fa	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-29 00:30:06 +03:00
Alan Orth	1806d50a51	Pipfile: Use falcon 2.0.0 ... See: https://github.com/falconry/falcon/releases/tag/2.0.0	2019-05-03 16:31:06 +03:00
Alan Orth	a459e66fd9	Use falcon 2.0.0rc2	2019-04-18 10:04:43 +03:00
Alan Orth	9dcda114c6	Bump Falcon version to 2.0.0b1 ... See: https://github.com/falconry/falcon/releases/tag/2.0.0b1	2019-04-18 09:57:18 +03:00
Alan Orth	622e9a86f1	CHANGELOG.md: Add notes about Python updates	2019-04-15 10:30:29 +03:00
Alan Orth	a640f734c8	Pipfile.lock: run pipenv update	2019-03-17 22:46:39 +02:00
Alan Orth	be94c94433	Pipfile.lock: Run pipenv update	2019-02-07 17:29:47 +02:00
Alan Orth	c95a98dd2d	Pipfile.lock: update dependencies ... Updated with `pipenv update`.	2019-01-15 10:22:46 +02:00
Alan Orth	3f70f94a10	Pipfile.lock: Run pipenv update	2018-11-26 11:53:37 +02:00
Alan Orth	378f56ddc2	Pipfile.lock: Run pipenv update	2018-11-19 23:34:34 +02:00
Alan Orth	a835b0fdc5	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 09:07:32 +02:00
Alan Orth	9c46cfc7e2	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 08:54:54 +02:00
Alan Orth	dcfef06a65	Pipfile.lock: Run pipenv update	2018-11-12 08:20:47 +02:00
Alan Orth	5c8756bede	Add pytest to pipenv development packages	2018-11-11 16:24:54 +02:00
Alan Orth	60ad474b88	Add ipython to pipenv dev packages ... This is very useful for debugging Python code interactively.	2018-11-07 17:07:14 +02:00
Alan Orth	085e525b2f	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 15:55:28 +02:00
Alan Orth	be18779ff9	Add flake8 to pipenv	2018-11-04 15:38:51 +02:00
Alan Orth	60cfd8f23b	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 15:35:47 +02:00