feat: Fingerprint datapoints python package #353
Conversation
github-actions
bot
added
the
t-tooling
pyproject.toml
Outdated
| build-backend = "hatchling.build" | ||
|
|
||
| [project] | ||
| name = "fingerprint_datapoints" |
fingerprint_datapoints/LICENSE
Outdated
| @@ -0,0 +1,201 @@ | |||
| Apache License | |||
There was a problem hiding this comment.
couldn't we use the license from the root dir?
There was a problem hiding this comment.
Good point. WIll reuse it.
There was a problem hiding this comment.
How frequently do you think we'll release this? Should we automate changelog generation?
There was a problem hiding this comment.
I think it will be on demand, only when there is reason to. But I do not expect periodic releases. So I would suggest adding automation only if my prediction proves wrong :D
| requires = ["hatchling"] | ||
| build-backend = "hatchling.build" |
There was a problem hiding this comment.
What are the benefits of using hatch over uv or poetry?
There was a problem hiding this comment.
I don't know. I picked the same build-backend we use in crawlee. (Maybe there is better option, but I would rather stick with the same tool in our repos. If we decide to change it, lets do it for all repos.)
There was a problem hiding this comment.
What are the benefits of using hatch over uv or poetry?
uv does not have its own backend (see astral-sh/uv#3957), and they recommend using hatchling (it's from PyPA).
There was a problem hiding this comment.
They do, see the same issue 😏 astral-sh/uv#3957 (comment) or Hynek's recent video https://www.youtube.com/watch?v=mFyE9xgeKcA
Co-authored-by: Jan Buchar <[email protected]>
|
Failing CI due to unrelated issues: #355 |
Add simple Python package that contains fingerprint data and helpers to get them and release flow to push it to pypi.