You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do think we need some CI for windows to claim compatibility. It may be easy, but I have no experience with windows -- same for every other bioinformatician in the lab
I have a document on my laptop with bunch of problems, i forgot to paste It here. There's more than dependencies.
But anyhow:
PyBigWig
pysam (required for bamread)
We did some tests on windows through github actions
(see actions -> filter by branch:expand_os). It's more fails than I had hoped.
Summary:
cannot install 1. pyBigWig, 2. bamread due to pysam.
get_sequence fetches some sequence but not as expected (tutorial test fail). pyfaidx bug on windows? or just negative strand? must investigate
various exceptions on opening files while accessing example_data, e.g. PermissionError when loading example_data.chipseq, example_data.ensembl_gtf, example_data.rfam_hits (easy fix? AI points to python "open" working differently on windows)
some \r in docstring output
Currently leaving expand_os branch as: testing only for windows, and only unit tests (others are commented in pyproject.toml). If pyranges code gets patched and these tests pass, we'd still need to move on to other tests too. And we would need to devise a way to split tests that require add-on dependencies (like pyBigWig) from others, so we could only test the minimal core for windows.
Activity
marco-mariotti commentedon Jan 12, 2026
I do think we need some CI for windows to claim compatibility. It may be easy, but I have no experience with windows -- same for every other bioinformatician in the lab
endrebak commentedon Jan 12, 2026
I'll have a look sometime. It might be as simple as adding a Windows entry in the OS list.
marco-mariotti commentedon Jan 14, 2026
@nadezhdamakarova1 in my lab uses windows alongside linux. She will test installation and tutorial, before considering automatizing to CI
[-]Add Windows-compatible as selling point in README.md[/-][+]Add Windows-compatibility tests[/+]marco-mariotti commentedon Jan 30, 2026
Changing name of issue to reflect that the main thing here is to ensure windows compatibility.
I opened branch expand_os to add non Linux OS to CI workflow. Mac works. Windows has some problems with dependencies. Following this through
endrebak commentedon Jan 31, 2026
Which packages :)
marco-mariotti commentedon Jan 31, 2026
I have a document on my laptop with bunch of problems, i forgot to paste It here. There's more than dependencies.
But anyhow:
PyBigWig
pysam (required for bamread)
Are not available.
And pyfaidx may have some bugs
endrebak commentedon Jan 31, 2026
So, this means that main pyranges works on Windows and some of the libraries we use for special functionality does not.
So pyranges without [all] should work then.
marco-mariotti commentedon Jan 31, 2026
We did some tests on windows through github actions
(see actions -> filter by branch:expand_os). It's more fails than I had hoped.
Summary:
cannot install 1. pyBigWig, 2. bamread due to pysam.
get_sequence fetches some sequence but not as expected (tutorial test fail). pyfaidx bug on windows? or just negative strand? must investigate
various exceptions on opening files while accessing example_data, e.g. PermissionError when loading example_data.chipseq, example_data.ensembl_gtf, example_data.rfam_hits (easy fix? AI points to python "open" working differently on windows)
some \r in docstring output
Currently leaving expand_os branch as: testing only for windows, and only unit tests (others are commented in pyproject.toml). If pyranges code gets patched and these tests pass, we'd still need to move on to other tests too. And we would need to devise a way to split tests that require add-on dependencies (like pyBigWig) from others, so we could only test the minimal core for windows.