Skip to content

Conversation

@shubhbapna
Copy link
Contributor

part of #368

I will update the fields in settings in a separate PR

@shubhbapna shubhbapna force-pushed the decouple-download-source branch from e381f74 to 4e6406f Compare September 3, 2024 23:07
Copy link
Member

@dhellmann dhellmann left a comment

Choose a reason for hiding this comment

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

A couple of nits for things to consider as follow-ups, but this looks good. Nice work with such a complicated refactor!

evaluated, version of the package being downloaded and the URL
from which the source can be downloaded as returned by `resolve_source`.

The return value should be a `pathlib.Path` file path to the downloaded source.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we should also pass the path to the directory where we expect the file to be written? The plugin can get it from the context, but it's one less thing a plugin author has to know. Something to think about for a follow-up.

`sources.resolve_dist()`, which will call `get_resolver_provider()`,
and then the return value of the resolution will be passed back to
`download_source()` as a tuple of URL and version. The provider can
The expectation is that it acts an engine for any sort of package resolution
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
The expectation is that it acts an engine for any sort of package resolution
The expectation is that it acts as an engine for any sort of package resolution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants