spinframework / spinframework/spin-python-sdk
Add Spin-version-specific worlds to `src/spin_sdk/wit/spin.wit`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48
- Forks
- 15
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 1
Description
Currently, there's no obvious way to use the latest SDK to target older (e.g. pre-3.4) versions of Spin; the only option is to use an earlier SDK version. One easy way to address that would be to add version-specific worlds to spin.wit, e.g. one for Spin 3.2.x, one for Spin 3.3.x, etc. This will allow the user to specify which Spin version they wish to target using the --world option to componentize-py in the build directive of their spin.toml file. The default would remain the latest version of Spin supported by the SDK.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/spin_sdk/wit/spin.wit and inspect the existing worlds and version-related definitions. Check how the --world option to componentize-py is specified in the build directive of spin.toml. Done means version-specific worlds cover the supported older Spin versions while the latest supported version remains the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100