Static versioning in pyproject.toml is conflicting with version.py versioning

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system, ci-cd

Research direction

Start by comparing the static version in pyproject.toml with the dynamic version.py setup and reviewing the scikit-build compatibility concerns described in the issue. Investigate whether the current build configuration or hatchling can provide consistent versioning, then verify that forced version updates are checked in CI; done means the two versioning approaches no longer conflict and CI enforces the intended check.

Written by the indexing model from the issue text.

Description

invalid

version.py and the dynamic version in pyproject.toml were intended to work in tandem, with further checks on forced version updates with every PR. It's hardcoded in pyproject.toml and is not checked in CI.

That was a HACK due to the issues of scikit-build. Thus, to resolve the issue, it is recommended to verify the compatibility of scikit-build and pyproject.toml, or consider using the hatchling library as an alternative for wheel building.

Dominant language
Python
Stars
2
Forks
5
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arrayfire/arrayfire-py

All issues in arrayfire/arrayfire-py

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.