Skip to content

Conversation

@sh-rp
Copy link
Collaborator

@sh-rp sh-rp commented Sep 18, 2025

Description

We have tests to test lower bounds of our allowed dependencies. We also want to see if a newer version of any or our dependencies (as allowed in pyproject.toml) breaks anything in dlt.

@netlify
Copy link

netlify bot commented Sep 18, 2025

Deploy Preview for dlt-hub-docs canceled.

Name Link
🔨 Latest commit 8a1bb6d
🔍 Latest deploy log https://app.netlify.com/projects/dlt-hub-docs/deploys/68cbc4aafe0b070007b7a1f9

@sh-rp sh-rp force-pushed the tests/test_newest_package_versions branch from 3163148 to d32b2ee Compare September 18, 2025 07:43
@sh-rp sh-rp force-pushed the tests/test_newest_package_versions branch from 689daa9 to 8a1bb6d Compare September 18, 2025 08:36
assert (
coerce_value("text", "binary", HexBytes(b"binary string")) == "0x62696e61727920737472696e67"
)
assert coerce_value("text", "binary", HexBytes(b"binary string")) in [
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

A newer version of hexbytes returns the hexcode without "0x". We have a couple of options:

  • Keep as is, this means users will see other values in their destination after upgrading this lib
  • Normalize result in normalizer so the result is the same regardless of lib version (kind of a breaking change, either for users on the old version or the new version)
  • Update min version of hexbytes to the version with the new output. Also a kind of breaking change.

Imho this is probably an edge case. I think I would probably keep it as is.

Copy link
Collaborator

Choose a reason for hiding this comment

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

HexBytes was used to make sure that 0x is present... so if that got removed it does not make sense to use it. My take: write our own HexBytes that alwasy prefixes and parses the prefix. it should be pretty simple to do.

for now I'd merge this ticket

@sh-rp sh-rp self-assigned this Sep 18, 2025
@sh-rp sh-rp marked this pull request as ready for review September 18, 2025 09:28
Copy link
Collaborator

@rudolfix rudolfix left a comment

Choose a reason for hiding this comment

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

@sh-rp let's merge it. I always wanted to test of max dependencies too.

re. HexBytes: see my comment I bet @alkaline-0 can port this to dlt and remove the dependency :)

assert (
coerce_value("text", "binary", HexBytes(b"binary string")) == "0x62696e61727920737472696e67"
)
assert coerce_value("text", "binary", HexBytes(b"binary string")) in [
Copy link
Collaborator

Choose a reason for hiding this comment

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

HexBytes was used to make sure that 0x is present... so if that got removed it does not make sense to use it. My take: write our own HexBytes that alwasy prefixes and parses the prefix. it should be pretty simple to do.

for now I'd merge this ticket

@sh-rp sh-rp merged commit 58ae630 into devel Sep 19, 2025
135 of 136 checks passed
@sh-rp sh-rp deleted the tests/test_newest_package_versions branch September 19, 2025 06:53
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.

3 participants