-
Notifications
You must be signed in to change notification settings - Fork 202
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
enable --module-extensions
by default (+ resolve template values used in extension version)
#4501
Conversation
I'm very confused, out of the type of tests i expected to see failing, the one that actually broke is test_exts_list, the one the test is supposed to already be using this feature to see the list of extensions?? And It fails because it is missing homepage field.
I can only assume this test was never actually running properly then? Confusing. |
9b45800
to
cb6eb4b
Compare
oh, it's just the test that is super misleading, issue has nothing to do with homepage. It was just due to the partial template resolving code that get_description attempts for some reason. I think it started from needlessly using template to put in the |
Old method needlessly involved template resolutions, duplicating the template resolving code, but only partially and would break if anything but the 4 most common templates were used.
cb6eb4b
to
3170d9f
Compare
I'm struggling with the test suite, because of the already existing bug that breaks --module-extensions=True.
|
The bug here also is present in the generated |
Concrete example of the bug in module for
because exts_list = [
...
('%(namelower)s', version, {
'checksums': ['2586e5ff4150f122716fc40f5530e92871befc051848fbe82600969c535b762d'],
}),
] |
--module-extensions
true by default (+ resolve template values used in extension version)
--module-extensions
true by default (+ resolve template values used in extension version)--module-extensions
by default (+ resolve template values used in extension version)
1247d0f
to
60f5eb2
Compare
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
…on name/version are resolved as expected
60f5eb2
to
ac9ddea
Compare
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
fixes #4396