-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add enable-all-extensions
option
#5315
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
option = optikcontainer.add_option(*args, **optdict) | ||
try: | ||
option = optikcontainer.add_option(*args, **optdict) | ||
except optparse.OptionConflictError: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Pierre-Sassoulas Are we sure this doesn't create problems?
Without it for some reason we get an error on accept-no-param-docs
being a duplicate error. I couldn't figure out why it did this. This solves the issue and passes the tests, but I wonder if this creates other issues..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, it's strange, the error that is caught itself did not seem out of place for me, but if it's accept-no-param-docs being a duplicate error
then it's an internal pylint error not an optparse error ? We should probably investigate if that's the case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found the issue.
It is the extension check_docs
. Because of it we are double loading docparams
.
It has been deprecated for 5+ years. Perhaps it is time to remove it?
Pull Request Test Coverage Report for Build 1464306898
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I just saw the coverage and realized it's not tested at all. Maybe it's doable in a functional test ?
@@ -489,7 +489,13 @@ def cb_verbose_mode(self, *args, **kwargs): | |||
def cb_enable_all_extensions(self, option_name: str, value: None) -> None: | |||
"""Callback to load and enable all available extensions""" | |||
for filename in os.listdir(os.path.dirname(extensions.__file__)): | |||
if filename.endswith(".py") and not filename.startswith("_"): | |||
# pylint: disable=fixme | |||
# TODO: Remove the check for deprecated check_docs after the extension has been removed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we remove the extension in 2.13
? Or do we consider this 3.0
worthy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's decide later. these todo list issue are very convenient, I'm going to do more of those. #5317 Feel free to edit :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might want to look into Github projects, I find them even more convenient and much harder to lose out of sight as the issues on the front page increase.
doc/whatsnew/<current release.rst>
.Type of Changes
Description
@Pierre-Sassoulas 👀
Might as well put it in
2.12
.Partial of #5306.