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

Use tblib to pickle errors in run_in_pyodide #2619

Merged
merged 10 commits into from
May 27, 2022

Conversation

hoodmane
Copy link
Member

No description provided.

Copy link
Member

@ryanking13 ryanking13 left a comment

Choose a reason for hiding this comment

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

Thanks, @hoodmane. It is not directly related to this PR, but I recently found that it is a little non-intuitive that one should build pytest to run a test that uses run_in_pyodide (which is because pytest_assert_rewrites is true in default).

For example,

$ PYODIDE_PACKAGES="some_pkg" make
$ pytest packages/some_pkg

will complain about pytest not being installed, so one has to do

$ PYODIDE_PACKAGES="some_pkg,core" make
# or
$ PYODIDE_PACKAGES="some_pkg,pytest" make

to run a test.

This PR also adds a dependency to run a test, so we probably should update some documentation, or find a better way to deal with inner(?) test dependencies.

requirements.txt Show resolved Hide resolved
@hoodmane
Copy link
Member Author

I should fix it so that if pytest isn't installed it just falls back to not using it. Same is possible for tblib. They just generate better tracebacks when a test fails, so on failure we can append "for a better traceback, build pytest and tblib".

@hoodmane hoodmane merged commit d818f41 into pyodide:main May 27, 2022
@hoodmane hoodmane deleted the run_in_pyodide-tblib branch March 1, 2023 17:27
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.

2 participants