8000 Add Windows-compatibility tests · Issue #120 · pyranges/pyranges1 · GitHub
[go: up one dir, main page]

Skip to content
8000

Add Windows-compatibility tests #120

Open

Description

@endrebak

It should also be added to the paper if we are asked for revisions.

Perhaps we should add a Windows flow to the C/I? That is another issue though

Activity

  1. marco-mariotti commented on Jan 12, 2026

    @marco-mariotti
    Member

    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

  2. endrebak commented on Jan 12, 2026

    @endrebak
    CollaboratorAuthor

    I'll have a look sometime. It might be as simple as adding a Windows entry in the OS list.

  3. marco-mariotti commented on Jan 14, 2026

    @marco-mariotti
    Member

    @nadezhdamakarova1 in my lab uses windows alongside linux. She will test installation and tutorial, before considering automatizing to CI

  4. changed the title [-]Add Windows-compatible as selling point in README.md[/-] [+]Add Windows-compatibility tests[/+] on Jan 30, 2026
  5. marco-mariotti commented on Jan 30, 2026

    @marco-mariotti
    Member

    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

  6. endrebak commented on Jan 31, 2026

    @endrebak
    CollaboratorAuthor

    Which packages :)

  7. marco-mariotti commented on Jan 31, 2026

    @marco-mariotti
    Member

    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

  8. endrebak commented on Jan 31, 2026

    @endrebak
    CollaboratorAuthor

    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.

  9. marco-mariotti commented on Jan 31, 2026

    @marco-mariotti
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    0