RE:natcap#1431

…atcap#1431

natcap#1431

RE:natcap#1431

…#1431

…esn't like all the nested curly braces. RE:natcap#1431

…cap#1431

RE:natcap#1431

This comes at a near-doubling of required stack memory (and some heap
memory), but it should be OK for most users.  RE:natcap#1431

…cython core. RE:natcap#1431

RE:natcap#1431

…dels-have-int32-limitations

…431-sdr-and-probably-other-routed-models-have-int32-limitations

Conflicts:
	HISTORY.rst

…nt32-limitations' of github.com:phargogh/invest into bugfix/1431-sdr-and-probably-other-routed-models-have-int32-limitations

RE:natcap#1431

This way pip will perform scm-based package installation like normal
with whatever extra dependencies it needs.

RE:natcap#1431

RE:natcap#1431

…dels-have-int32-limitations

RE:natcap#1431

…431-sdr-and-probably-other-routed-models-have-int32-limitations

Conflicts:
	HISTORY.rst

…nt32-limitations' of github.com:phargogh/invest into bugfix/1431-sdr-and-probably-other-routed-models-have-int32-limitations

… version incompatibility that I encountered in github actions. RE:natcap#1431

When running on github actions, I found an error noting that `Hook
already exists: pre-push` (see below), which to me makes me think that
LFS already exists and has been configured.  And I confirm that on GHA,
git-lfs is installed to version 3.4.0

```
git -C data/invest-test-data lfs install
Hook already exists: pre-push

	#!/bin/sh
	command -v git-lfs >/dev/null 2>&1 || { echo >&2 "\nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory (set by 'core.hookspath'; usually '.git/hooks').\n"; exit 2; }
	git lfs pre-push "$@"

To resolve this, either:
  1: run `git lfs update --manual` for instructions on how to merge hooks.
  2: run `git lfs update --force` to overwrite your hook.
```

RE:natcap#1431

…ust in case. RE:natcap#1431

A compiler will be needed to build from source.

RE:natcap#1431