-
Notifications
You must be signed in to change notification settings - Fork 5
Error: No such command "init_db". #11
Comments
Issue reported to click issue tracker at pallets/click#1123 Seems they done broke something overnight. On a related note is there anyway to force mschematool to depend on a specific version of click, in this case the working v6.7? |
For others reading we've worked around the issue with pip freeze, order of operations is important here (assuming fresh box with only python/pip installed):
The result is that pip doesn't bother pulling down the latest click package, which would break mschematool. |
See linked issue to click package repo, turns out it's due to the underscore _ in a) command authors (@aartur) are still expected to use underscore(s) in decorated method names They're working out something of a compromise for click v7.1 but v7.0 will forever break mschematool (and other packages that depend on click and use underscores in their method names). So I guess the question is, can you lock mschematool tool to require click < v7.0 or >= v7.1? |
I'm sorry guys, I thought I fixed the delivery of notifications but this was not the case (I think my email gateway's IPs are sometimes blocked by some ISPs). I released 0.9.1 with package version pinned. If someone is willing to take over the maintenance of |
I added a deprecation notice to the README. |
Sometime overnight our CI began failing during database migrations at step
mschematool xyz init_db
:Error: No such command "init_db".
Looking at the log of the last successful run and comparing it to the failing runs:
log from Successful job:
log from Failing job:
The text was updated successfully, but these errors were encountered: