Skip to content

Consider switching CI to Github Workflows, include Windows #108

Closed
#140
Closed
Consider switching CI to Github Workflows, include Windows#108
#140
Assignees
bnavigator

Description

@roryyorke
roryyorke
opened on Apr 25, 2020

Nothing for this release, but would it be worth to switch from Travis to Github Workflows and include Windows builds there? Possibly based on #80, although to me that seems a bit outdated by now.

Originally posted by @bnavigator in #101

Activity

  1. bnavigator commented on May 30, 2020

    @bnavigator
    bnavigator
    on May 30, 2020
    Collaborator

    This will also be a good opportunity to adopt NEP 29, which effectively means to drop the support for Python 2 and 3.5 now and 3.6 very soon.

  2. bnavigator
    self-assigned this
    on Dec 21, 2020

  3. bnavigator commented on Dec 30, 2020

    @bnavigator
    bnavigator
    on Dec 30, 2020
    Collaborator

    I have been trying to prepare something in #140, but it is not finished yet.

    Dropping Python 2 will also help to avoid workarounds like in #139.

  4. bnavigator
    linked a pull request that will close this issueGitHub workflow #140on Dec 30, 2020
  5. roryyorke
    closed this as completedin #140on Jan 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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