Skip to content

Add test entries for PYODIDE_INTERPRETER and PYODIDE_PACKAGE_INDEX #207

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

Closed
wants to merge 2 commits into from

Conversation

agriyakhetarpal
Copy link
Member

This PR should add a few test entries for #199.

cc: @hoodmane

Comment on lines 50 to 51
"interpreter" = "$(PYODIDE_INTERPRETER)"
"package_index" = "$(PYODIDE_PACKAGE_INDEX)"
Copy link
Member

Choose a reason for hiding this comment

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

I don't think we expect people to overwrite these configs.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, this is with the in-tree case, I'll drop it. What should be the scenario with the out-of-tree case?

Copy link
Member

Choose a reason for hiding this comment

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

I don't think people would want to overwrite these variables in out-of-tree as well. The interpreter is coming from the xbuildenv, and the package_index is created by pyodide venv. I guess these variables are used mostly for getting the path for these values rather than overwriting it?

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.

LGTM

@agriyakhetarpal
Copy link
Member Author

I agree with you here, @ryanking13 and @hoodmane does too – I don't see anyone in the near future trying to override the package index without horribly breaking their ABI compatibility due to a runtime, and we don't have a nice way to deal with this until #88, so I would be fine with closing this. We already have tests that check the existence of the keys and vars, so this might be redundant. Thanks for the review!

@agriyakhetarpal agriyakhetarpal deleted the more-test-config-entries branch May 23, 2025 03:11
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