-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Sort requirements.txt
files when generating Python code
#16115
Conversation
Changelog[uncommitted] (2024-05-03)Bug Fixes
|
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.
This probably needs the tests to be run with PULUMI_ACCEPT=true
to regenerate the testdata. The rest of the code changes look good to me.
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.
Agree with Thomas, change looks good but testdata needs re-generating.
PULUMI_ACCEPT=1 go test ./...
in pkg/codegen/python and sdk/python/cmd/pulumi-language-python should do it
Also a small update to the PR description to add that it fixes the bug Thomas raised about the tests being flaky. |
2c1bc2c
to
286d76d
Compare
286d76d
to
92fbbb7
Compare
To be merged after #16119 merges. Tentative changelog: - [backend] Fix concurrent reads from and writes to display resource timer maps [#16101](#16101) - [engine] Better handle property dependencies and deleted-with relationships when pruning URNs, verifying snapshot integrity and computing dependency graphs. [#16088](#16088) - [programgen/python] Sort generated requirements.txt files when generating Python programs [#16115](#16115)
A couple of our tests now generate multi-line
requirements.txt
whose order is dependent on that in which we enumerate packages when testing. This PR changes this so that we always sort them, meaning we can consistently check against snapshotted results (as opposed to having flaky tests that only pass when the generated order matches the one we happened to snapshot last).Fixes #16113