support python3.14

[percy507]

Hello, I encountered an installation issue when trying to use binance-sdk-derivatives-trading-usds-futures with Python 3.14.

Currently, the package specifies:
python_requires = ">=3.9, <3.14"

My project uses Python 3.14 for the following reasons:

• While Python 3.14 introduces some breaking changes (e.g., in asyncio and urllib), they do not appear to affect this SDK's core functionality based on my review (no removed APIs that the package depends on).
• Python 3.14 brings meaningful improvements in performance (e.g., faster I/O and asyncio) and memory management (e.g., incremental garbage collection).
• My project relies on the uuid7 feature (introduced in Python 3.13 and stable in 3.14), which provides optimal time-ordered UUIDs not natively available in earlier versions.

Given this, I would like to request that the SDK relax its python_requires constraint to support Python 3.14.

If there are currently no known compatibility issues, perhaps updating the range to: >=3.9, <3.15
or simply:
>=3.9
would be sufficient.

Thank you very much!

[percy507]

Another problem,
In my test project, I switch to python3.13, when installing the package, I got the following error:

(test-python-py3.13) ➜  test-python poetry add binance-sdk-derivatives-trading-usds-futures              
Using version ^4.0.0 for binance-sdk-derivatives-trading-usds-futures

Updating dependencies
Resolving dependencies... (0.0s)

Because no versions of binance-sdk-derivatives-trading-usds-futures match >4.0.0,<5.0.0
 and binance-sdk-derivatives-trading-usds-futures (4.0.0) depends on ruff (>=0.12.0,<0.13.0), binance-sdk-derivatives-trading-usds-futures (>=4.0.0,<5.0.0) requires ruff (>=0.12.0,<0.13.0).
So, because test-python depends on both binance-sdk-derivatives-trading-usds-futures (^4.0.0) and ruff (^0.14.1), version solving failed.

I noticed that the SDK includes this in its main dependencies: ruff = "^0.12.0"

This is causing installation issues because ruff is a dev tool (linter) and shouldn’t be part of the runtime dependencies.

If a project already uses a newer ruff version (like 0.14.x), dependency resolution fails and the SDK cannot be installed.

It would be better to move ruff to dev-dependencies or remove it from the install dependencies entirely.

After checking the pyproject.toml, I also noticed a few additional potential issues:

• Other dev tools listed as runtime dependencies
  • black = "^25.1.0" and pytest are in [tool.poetry.dependencies].
  • These are also dev tools and should not be required at runtime.
• Duplicate or conflicting dev dependencies
  • pytest appears both in main dependencies and in the dev group with different versions.
  • Suggest keeping all dev/test dependencies in one place to avoid conflicts.

Making these adjustments would make the SDK easier to install and integrate without forcing users to downgrade dev tools or change Python versions.

Thanks for your work on this project!

ps: These problems seem to also exist in other packages, eg: binance-sdk-spot.