Skip to content

Conversation

tim-schilling
Copy link
Member

Occassionally we will get a stacktrace that's an importlib instance string
representation. While we may be able to put the python path or something else
it's likely easier (and more logical) to simply pass that onto the user.

I was unable to reproduce the issue in our tests, so I've mocked the case
in test_importlib_path_issue_1612.

Fixes #1612

Occassionally we will get a stacktrace that's an importlib instance string
representation. While we may be able to put the python path or something else
it's likely easier (and more logical) to simply pass that onto the user.

I was unable to reproduce the issue in our tests, so I've mocked the case
in test_importlib_path_issue_1612.

Fixes #1612
Copy link
Member

@matthiask matthiask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest adding a comment to this particular location in the code, not just the test. LGTM but tests are failing.

Co-authored-by: Matthias Kestenholz <[email protected]>
@tim-schilling
Copy link
Member Author

tim-schilling commented May 2, 2022

tests are failing.

I didn't have time to investigate that part yet. It's likely failing on main as well since the other recent PR has the same failure exception.

@matthiask
Copy link
Member

You're right. Let's merge this.

@matthiask matthiask merged commit c39b84b into django-commons:main May 2, 2022
@tim-schilling tim-schilling deleted the issue-1612 branch May 2, 2022 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ValueError: not enough values to unpack (expected 2, got 1)
2 participants