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

feat: built-in cache support #22

Merged
merged 2 commits into from
Oct 21, 2022
Merged

feat: built-in cache support #22

merged 2 commits into from
Oct 21, 2022

Conversation

frostming
Copy link
Contributor

No description provided.

@frostming frostming linked an issue Oct 21, 2022 that may be closed by this pull request
@frostming frostming merged commit 5f29900 into main Oct 21, 2022
@frostming frostming deleted the feat/builtin-cache branch October 21, 2022 04:07
@gazpachoking
Copy link

😯😄 Awesome!

@pawamoy
Copy link
Contributor

pawamoy commented Oct 26, 2022

For projects which do not track pdm.lock (libraries), should I pass pyproject.toml instead?

@gazpachoking
Copy link

For projects which do not track pdm.lock (libraries), should I pass pyproject.toml instead?

If you want it to always be testing against the latest allowable version of your deps, I'd turn caching off all together.

@frostming
Copy link
Contributor Author

For projects which do not track pdm.lock (libraries), should I pass pyproject.toml instead?

Yes, you can override it via cache-dependency-path option

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.

Built in cache support
3 participants