Skip to content
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

Using pipx to handle error: externally-managed-environment #10

Closed

Conversation

rafaeldelucena
Copy link

From the failed run

@rafaeldelucena
Copy link
Author

@ubruhin I got this error with the CI for the PR parkouss#82

@ubruhin
Copy link
Member

ubruhin commented Aug 7, 2024

Thanks, I didn't notice it since there was no CI run for a long time.
I don't know why it still fails with pipx, but I've now tried the way I go normally and this works fine: #11

@ubruhin
Copy link
Member

ubruhin commented Aug 7, 2024

@rafaeldelucena Btw, something we should change in near future is to get rid of nosetest. It is not maintained anymore and doesn't run with recent Python versions, thus only one CI job is still executing the tests. My suggestion would be to remove the testing adapter completely from Funq, making it just a Python library so it can be used with any testing framework (for LibrePCB, we use it already with pytest). And of course the tests in this repo need to be converted to pytest or so. But unfortunately at the moment I don't have much time for that :-/

@rafaeldelucena
Copy link
Author

@rafaeldelucena Btw, something we should change in near future is to get rid of nosetest. It is not maintained anymore and doesn't run with recent Python versions, thus only one CI job is still executing the tests. My suggestion would be to remove the testing adapter completely from Funq, making it just a Python library so it can be used with any testing framework (for LibrePCB, we use it already with pytest). And of course the tests in this repo need to be converted to pytest or so. But unfortunately at the moment I don't have much time for that :-/

I'm 100% on dropping nosetest in the flavor of pytest, I have a WIP branch with that somewhere, but didn't advance because we had no more CI running the tests, there are many good things to come, just need to run the tests again

@rafaeldelucena
Copy link
Author

@ubruhin I'm closing this in favor of your fix in #11

@rafaeldelucena
Copy link
Author

Not required anymore since #11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants