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

Python bindings should handle scientific notation of floats #2105

Closed
thibault-martinez opened this issue Mar 1, 2024 · 3 comments
Closed
Assignees
Labels
b-python Bindings - Python

Comments

@thibault-martinez
Copy link
Member

As present in the MetricsResponse of the API

@thibault-martinez thibault-martinez added the b-python Bindings - Python label Mar 1, 2024
@thibault-martinez thibault-martinez added this to the v2.0.0 (Q1 2024) milestone Mar 1, 2024
@Alex6323
Copy link
Contributor

Alex6323 commented Mar 5, 2024

Can I get more information on this issue? In what sense can Python in particular not handle the scientific notation? Do you have an example or error message?

@Thoralf-M
Copy link
Member

Decoding the metrics from the nodeinfo fails currently

"metrics":{"blocksPerSecond":"1.48E+01","confirmedBlocksPerSecond":"1.51E+01","confirmationRate":"1.0202702702702702E+02"}

but it's changed and moved to another endpoint atm https://github.com/iotaledger/iota.go/pull/703/files then we need to check again if it works fine or needs a custom decoder

@Alex6323 Alex6323 linked a pull request Mar 15, 2024 that will close this issue
@Alex6323 Alex6323 removed a link to a pull request Mar 15, 2024
@thibault-martinez
Copy link
Member Author

Metrics has been moved out of info response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
b-python Bindings - Python
Projects
Status: Done
Development

No branches or pull requests

3 participants