-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Move to PEP-451 style loader #386
base: master
Are you sure you want to change the base?
Conversation
I didn’t add a changelog note yet because that would conflict with #384. |
return None | ||
|
||
|
||
def wrap_loader(loader, class_name): |
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.
A bonus of using this wrapping approach is that it should still work when the settings file is a frozen module, or otherwise provided by some special kind of module. I don’t believe that was supported before, because the old ConfigurationImporter
forced using the plain ConfigurationLoader
, which had no special logic for loading things.
sys.meta_path.insert(0, importer) | ||
installed = True | ||
|
||
|
||
class ConfigurationImporter: | ||
class ConfigurationFinder(PathFinder): |
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.
Also changing this class into a PEP-451 compliant finder, and renaming it as such.
Tests are passing but codecov is failing, as noted on #384. |
@washeck @pauloxnet Is this application still being maintained? Do you need more hands to manage the PR reviews etc? |
The project is maintained but I'm not using it on a daily basis anymore. |
@pauloxnet - ok. Please add me to the project. Also, who is responsible for making releases as it is of no use if PR's are merged but we cannot get new releases done. |
I'm one of the 3 "leads" of the project and I triggered the last release which is aligned with the latest commit. So no risk of PR merged and not released. I suggest to you to open your PR or (better) review opened PRs you are more interested in, to help it to be ready to be merged (e.g. this PR has some failing checks). More info about about the project (and how to join it) here: https://jazzband.co/projects/django-configurations |
I opened an issue about Codecov failings #390 (help needed) |
Please rebase now that tests are passing again. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #386 +/- ##
==========================================
- Coverage 90.39% 90.37% -0.02%
==========================================
Files 25 25
Lines 1197 1195 -2
Branches 102 102
==========================================
- Hits 1082 1080 -2
Misses 88 88
Partials 27 27 ☔ View full report in Codecov by Sentry. |
@cclauss I tied to solve the conflict, but I can't do anything else here. If Adam can't push this forward, you are free to open another PR base on this and solve all the conflict and test issue. |
Just whitespace issues.
|
Can you add code suggestions so I can try to accept those? |
Co-authored-by: Christian Clauss <[email protected]>
@adamchainz - can you add unit tests to achieve required code coverage? |
Fixes #385.