conda-forge / conda-forge/xeus-python-feedstock
python-3.14t build
- Dominant language
- Batchfile
- Stars
- 1
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
### Solution to issue cannot be found in the documentation.
- [x] I checked the documentation.
### Issue
Is there a way to trigger this build to satisfy the python 3.14 dependency, or does extra internal work in xeus-python need to be done? I have a software (Harpy) who's bioconda build can't pass and the maintainers are asking me to trigger rebuilds in the dependencies for 3.14 compat rather than setting a `python <3.14` upper limit. If not, I can return to the maintainer explaining their suggested solution is not tractable.
Discussion:
https://github.com/bioconda/bioconda-recipes/pull/65792#discussion_r3421253711
### Installed packages
```shell
- altair >=6.0
- bcftools >=1.23
- click >=8.2
- conda >=24.8
- djinn >=2.3
- htslib >=1.23
- jupyter-book >=2.1.0
- papermill >=2.6
- pandas >=2.3.3
- pillow >=12.2
- polars >=1.39
- pysam >=0.23
- python >=3.11
- rich-click >=1.9.3
- samtools >=1.23
- seqtk
- snakemake-minimal >=9.19.0
- vl-convert-python >=1.9.0
- xeus-python >=0.18.1
```
### Environment info
```shell
conda build
```
Contributor guide
Research direction
Start by reading the linked bioconda discussion and reviewing how this feedstock is handled by `conda build` for Python 3.14 compatibility. Determine whether a rebuild can be triggered or whether xeus-python needs additional internal work; done means documenting the supported path or the reason it is not tractable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100