Add Makefile for env, dev, and django example

[dotysan]

• migrate setup.py develop to pip install
• also ignore other env and working files

[subzero10]

Hey @dotysan, thanks for submitting this PR!

There's already an issue #127 to use a dependency manager, what is your opinion on using Make + pip vs the other options listed in the issue?

[dotysan]

Well...a small/simple Makefile with venv is just my personal crutch. It's mostly out of habit. And just because I can easily read/edit/execute it.

I really don't have much experience with Pipenv, Poetry, PDM.

I did, however, bootstrap a pip module with Flit last month and it worked swimmingly! I also enjoyed tinkering with Hatch, but in the end Flit met my simple needs.

In a different branch, I'm in the process of moving tests to tox and requirements out of setup.py into pip --require files for both dev and test. Maybe after that, this will all be moot...

[subzero10]

Well...a small/simple Makefile with venv is just my personal crutch. It's mostly out of habit. And just because I can easily . > read/edit/execute it.

I really don't have much experience with Pipenv, Poetry, PDM.

I see your point, though it means the Makefile needs to be maintained as the package evolves. I would like to explore at least one of these dependency management tools first.

I did, however, bootstrap a pip module with Flit last month and it worked swimmingly! I also enjoyed tinkering with Hatch, but in the end Flit met my simple needs.

I didn't know about Flit, we use Twine to deploy this package :).

In a different branch, I'm in the process of moving tests to tox and requirements out of setup.py into pip --require files for both dev and test. Maybe after that, this will all be moot...

I guess we should wait for that branch then, right?

[dotysan]

I've moved all the heavy lifting into tox here. #153

And I still use the lightweight Makefile for only constructing my local dev/venv, dependencies, and repetitive tasks.