Stepwise migrations, command line tool, status.

[cam-stitt]

Fixes #11, #12, #13.

[stas]

Nose is not part of the setup.py, why not just use setuptools with test command?

https://pythonhosted.org/setuptools/setuptools.html#test-build-package-and-run-a-unittest-suite

[Dr-Horv]

Ah nice with stepwise and status, thanks! 😄

[stas]

Instead of providing an optparse instance which is hard to use during tests you could provide a dictionary. (Ex.: args.__dict__).

Worth mentioning that args is not a very good name, for example pdb.set_trace() will shadow it.

[stas]

@cam-stitt I took the liberty to write some feedback, I hope you look at it in the most constructive way. I'm motivated to see this package improving since we are using it, the new version has some nice improvements but it is absolutely backwards incompatible.

My experience of using arnold is more as a library rather as a tool. The fact that we could pragmatically integrate with our codebase was a huge win. To give you an idea of how we were using it:

import os
from arnold import main
from our_package import Model, migrations

main(
    direction='up',
    database=Model._meta.database,
    directory=os.path.dirname(migrations.__file__),
    migration_module='our_package.migrations'
)

The feedback I left is related mostly to some design aspects that are no longer helping a developer use arnold the same way it worked before. Please let me know if I can help with anything else.

Thanks in advance for all the work on arnold.

[cam-stitt]

I appreciate the feedback. It's the only way the project can get better. I was well aware of the backward incompatibility of the update, and probably should have spent more time trying to make it work. The good news is that the update does still have a configuration file that you can setup. Maybe I need to look at how I can have the folder/migrations all setup within the config.