Add `rattail_shopfoo` project generator

also *remove* the `db/alembic/env.py` script from rattail-adjacent
generator. it didn't seem necessary..now we'll see if it ever is

Massive overhaul of "generate project" feature

previous incarnation was woefully lacking. new feature is much more
extensible. still need to remove old POS integration specifics in
some places.

and a couple of unrelated things that snuck in..

- deprecate `rattail.util.OrderedDict`
- deprecate `rattail.util.import_module_path()`
- deprecate `rattail.util.import_reload()`

Add `rattail telemetry` command

for submitting basic server info to support host

Officially require SQLAlchemy 1.4.x

drop support for 1.3.x, not yet ready to support 1.5.x

Bump version cap for SQLAlchemy to 1.4.x

hopefully can jump ahead further soon, but let's make sure all dust
has settled on this jump first

had to adjust some relationships to avoid FK "overlap" - cf. also
https://docs.sqlalchemy.org/en/14/errors.html#error-qzyx

Remove some cruft from new project template

more to go, esp. for install command, but not today..

Add `rattail make-project` command, for simpler quickstart

also adds a basic DB handler, etc.

Add initial logic for `rattail cleanup` command

will add a cleaner for beaker sessions shortly; more will come later
i'm sure

Remove the 'backup' extra from `setup.py`

no reason for rattail proper to get involved with those details

Add basic `rattail overnight` command, for running luigi tasks

although at this stage, it isn't very aware of luigi, and just knows
to run the "script" associated with given task defined in config

Add datasync handler class; let it talk to supervisor

seems like we maybe shouldn't assume presence of (or access to)
supervisor, but in practice so far it's a safe bet...

Add support for memcached as beaker config cache backend

technically this is for other backends too, i just tried memcached

Add entry points support for locating email profiles

this simplifies adding support for new email profiles in custom apps,
when they're added to underlying packages

Add basic `rattail postfix-summary` command

hopefully will help track down mail problems when they occur. note
that this may require configuring `sudoers` to work correctly

Add initial support for Beaker caching of config values from DB

refs #8

Add `rattail mysql-chars` command to view/fix charset, collation

at least that's the goal, so far it won't actually try to fix, but can
emit SQL for manual fix

Stop using legacy syntax to define entry points

been meaning to get around to that, but setuptools v60.9.0 seems to
have forced my hand. never did find docs saying that the syntax had
been deprecated, but updating that fixed a problem where apparently
none of the entry points were actually being recorded when the package
was installed, when setuptools 60.9 was present

https://setuptools.pypa.io/en/latest/history.html#v60-9-0

Move tests out of the installed package set

this seems to be better practice. from what i can tell this is a
clean move with no breakage.. and built package files no longer seem
to include test modules

Remove some config for nosetests

buildbot is using only pytest now, but will leave nose in the test
dependencies until other packages are updated, e.g. tailbone

OMG a ridiculous commit to overhaul import handler config etc.

- add `AppHandler.get_designated_import_handlers()` and friends
- exit w/ code 1 when command line makes no sense and must print help
- register all core import/export handlers via setup.py and config
- use "handler key" lookup for all core import/export commands
- stop displaying model list in help for import/export command
- migrate datasync "change" permissions, per tailbone changes
- log warning w/ traceback if loading entry point fails

Add some methods/attrs to import handlers, for exposing in web app

not complete but a good start

Add "generic" vendor catalog parser

we'll see how generic it really is once more people try to use it...

Add initial version of the "mailmon" daemon

and refactor some filemon config etc. to leverage common logic

Freeze version of SQLAlchemy to 1.3.x

we should support 1.4.x ASAP but for now tailbone still requires an older
zope.sqlalchemy which in turn can't handle SA 1.4.x

Let win32 share the 'auth' extra

since it's just passlib now, and that seems to work fine

Add simple `rattail checkdb` command

almost certainly needs improvement, but i need it released for sake of testing
Theo dev bootstrap

Add feature to generate new features...

at least that's the idea. probably requires a web UI to be useful

Tweak borg requirement for 'backup' extra

per latest borg docs. i had encountered an issue with pip 20.3.3 and its "new
resolver" although not real clear how related that was.

Add `rattail version-check` command, for consistency checks

just the very basics for now, not sure what all is needed yet

Add `rattail make-batch` command

so that we can make new batches via filemon, but shell out to avoid versioning

Add `rattail purge-versions` command

for those times when you need to start fresh on that

Add 'backup' requirements extra

mainly just for borg of course

Add basic support for `rattail import-csv` command

not sure how useful this will be yet, but seems promising for sample data anyway

Add support for `rattail export-csv` command

this may need some tweaks yet, but may be complete already?

Omit deprecated kwarg for `session.is_modified()`

when checking for pending changes, to be recorded to stub table. apparently
this could have been done a long time ago but only recently did warnings bring
my attention to it

Add generic `rattail run-n-mail` command

for use when the default system behavior won't let us define mail recipients
for e.g. 'at' job output emails

Add new `backup` command

i.e. `rattail backup`, meant to (hopefully) handle the common use cases...

Add `update-costs` command for making future costs become current

this just assumes any future cost which starts "before now" is game

Add versioning workaround support for batch actions

* commands accept `--versioning`, `--no-versioning` args
* use `finish()` progress method when ending a loop
* add `SocketProgress` (and `FileProgress`)
* commands accept `--progress-socket` arg
* add `do_*()` handler methods, for wrapping main actions
* populate, refresh, execute of batch may be done via command line
* handler declares which action(s) may (not) be done with versioning
* handler declares which version models to catch-up after execute

Add `runsql` command, mostly for dev use

at least for now? kind of in a rush at the moment

Test commit

trying to get buildbot 1.0 to auto-run from commit

Always install bcrypt

what the hell, might as well right?

Add 'bcrypt' as dependency

this seems safe enough...

Remove py-bcrypt as dependency for 'auth' feature

need to add bcrypt instead, but must wait to avoid breaking things

Add basic `ExcelWriter` class, plus xlrd and openpyxl dependencies

maybe not the best idea, but practical for now

Switch to passlib for password hashing and verification

at some point now, can remove the 'salt' column too

Add new `upgrade` command

for creating and/or executing upgrades

Switch license to GPL v3 (no longer Affero)

refs #2

Replace usage of `execfile()`

per py3k effort

Add basic `import-versions` command, for "catching up" versions

so far only Person is supported..

Disable some unused commands

The command logic remains in place, for now...

Remove `tempmon-server` command

This has been moved to the rattail-tempmon project

Remove deprecated commands: adduser, initdb

The make-user command does the same thing now.

Overhaul `rattail make-user` command to support multiple systems

Just 2 for now, rattail and windows. Probably need a way for custom
projects to support more systems as needed..

Add FormEncode as official dependency

That probably could have been done differently..oh well this works for now.

Add new bulk PostgreSQL and Rattail->Rattail importers

Plus tests, sort of..plenty of stubs in here still.

Add new Rattail -> Rattail main importer, with new/final framework

Plus tests, yay. Also includes a couple of other tweaks which came up
in other testing.

Remove alembic import from `db.util` module

Also bump the alembic version requirement, to ensure support for
multiple migration bases.

Make 'tests' a proper subpackage again; add some tests

Trying to make more of an effort here...

Add bulk Rattail importer, plus various tweaks

Tweaks are mostly for the sake of a `host_session`, if one is involved.

Make 'commands' subpackage, add 'rattail-dev' command.

And add subcommand for 'rattail-dev new-batch'. Hopefully this is all a
good idea, pretty rough draft at this point.