-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
add support for {pdm}
placeholder in scripts
#2408
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2408 +/- ##
==========================================
+ Coverage 84.51% 84.53% +0.02%
==========================================
Files 102 103 +1
Lines 10109 10129 +20
Branches 2224 2226 +2
==========================================
+ Hits 8544 8563 +19
- Misses 1087 1088 +1
Partials 478 478
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Hmm, will have to look at Windows failures tomorrow. I'm going to guess related to path normalization in some way... |
* add support for `{pdm}` placeholder in scripts * check should_interpolate * fix docs * add news item * Fix feedback and Windows
* add support for `{pdm}` placeholder in scripts * check should_interpolate * fix docs * add news item * Fix feedback and Windows
* add support for `{pdm}` placeholder in scripts * check should_interpolate * fix docs * add news item * Fix feedback and Windows
Pull Request Checklist
news/
describing what is new.Describe what you have changed in this PR.
As discussed on Discord, this adds support for using a
{pdm}
placeholder in scripts to refer to the current interpreter. I'm not sure if this should affect calls in any way, but I don't think so since they'd (presumably) use the same python interpreter/venv.