Skip to content

pushing v5.1.0 to pip #204

Open
Open

Description

@ccossou

Hi,

Sorry to intrude with a naïve question. When installing configobj, the latest version is 5.0.6. This version doesn't support validate and I can't install validate either in python 3.7 making the combo configobj==5.0.6+validate incompatible with python 3.7

Is it possible to push 5.1.0 of configobj to pip? This version would basically solve this issue. I wonder if this version is still in beta or not.

Activity

  1. WhyNotHugo commented on Dec 29, 2020

    @WhyNotHugo

    Sorry to nag here about this, but some distros are begging to package a patched 5.0.6, and this is creating breakage in downstream apps.

    The latest stable release is simply too old.

    Would you mind pushing a 5.1.0 based on the current master? Or at least maybe a 5.1.0b1?

  2. huebuild commented on Feb 12, 2021

    @huebuild

    👍

  3. anthraxx commented on May 13, 2021

    @anthraxx
  4. mafrosis commented on Jul 21, 2021

    @mafrosis

    @jhermann I believe you have the relevant permissions to push to pypi?

  5. robdennis commented on Jan 8, 2023

    @robdennis
    Member

    I think this is basically the same sentiment as #213 which now holds the most recent discussion where I lay out that I'm going to put at one last maintenance release (5.1.0) before making it explicit that the project needs a full-time maintainer to take it to the next phase

  6. robdennis commented on Jan 8, 2023

    @robdennis
    Member

    in reading this a bit more, I think the more fundamental point is that there are people who depended on validate as a separate artifact and I need to understand that a bit more

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions