New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Refs #29392 -- Added command line short option -s
for specifying setting.
#10029
[WIP] Refs #29392 -- Added command line short option -s
for specifying setting.
#10029
Conversation
Haha, so this is embarrassing. I wanted to check if and why Sorry for wasting your time @carltongibson -_- |
I honestly didn't know that |
Also I didn't mean to close the PR -- if you still have strong feelings for it please reopen. I find `--s` weird and am happy with not adding `-s` given the backwards issues we'd introduce
…On June 6, 2018 4:07:54 PM GMT+02:00, Carlton Gibson ***@***.***> wrote:
@carltongibson requested your review on: django/django#10029 [WIP] Refs
#29392 -- Added command line short option `-s` for specifying setting..
--
You are receiving this because your review was requested.
Reply to this email directly or view it on GitHub:
#10029 (comment)
|
Hey @apollo13. Thanks for the follow up. No issues on the confusion. I prefer to double check. Personally I’m not fussed by the |
FWIW, I ran into the "some prefix of 'settings' works" behavior the other day. I wouldn't mind having a |
@MarkusH I cheked in 1.11 -- |
Yes. The only option is to add it. I can see the appeal of that. I think we could make the case for the breaking change (and for 2.1 would be a good time given #9933), but I'd want someone to champion that (as I haven't got time/bandwidth/energy for the flack/discussion). I republished my branch in case someone wants to drive this forward: I'm happy to finish the PR, but I don't want to do the politics 😃. |
I feel a bit silly, but for such a small change, I'm finding myself quite strongly opposed to it. The utility of the settings short option seems marginal at best, and I don't think the breaking change is worth the tradeoff.
|
I think that's probably the swinger. No doubt loads of people would be affected. |
PR #9933 (for ticket #29392) removed the ability to use abbreviations of the shared options in commands. The key one there is
--settings
.Why? Because you couldn't define a command with e.g. a
--set
option, as this was getting swallowed as--settings
by the first pre-run parser. (This even though it's unambiguous to the final command parser.)Someone at DjangoCon (who will remain anonymous 🙂) said this was a usability back-step: in the shell they were used to doing something like
--s
and having it work.The example provided in the bug report struck me (and still does) as compelling. I think it was the right fix (correctness trumping convenience) but I'm opening this to discuss.
This PR adds a short option
-s
to--settings
. The hope is, that's the best of both worlds.BC Issues:
makemessages
already uses-s
. It does this for--symlinks
. I'd argue moving it to--settings
is a win (--settings
is always in use,--symlinks
how often?) (Discuss)-s
. Again, I'd probably be happy to steal that. (Discuss.)Other options:
Todo to merge:
django-admin.txt
with changes to--settings
in general andmakemessages
in particular.Is this worth A) a new ticket, B) a post to Django Developers?