Skip to content

Protobuf 2.6.0 pip dependency conflict #36

Closed

Description

@psypuff

Since google-apputils was added as a dependency on 2.6.0 we have dependency conflict on python-dateutil, apparently google-apputils needs 'python-dateutil>=1.4,<2' but the latest public version is 2.2 which is needed and installed by other packages.

Current workaround is to downgrade python-dateutil to 1.5 but it'll probably break something sooner or later, any chance to loose a bit the requirements?

Thanks

Activity

  1. dhermes commented on Oct 3, 2014

    @dhermes

    FYI this is causing problems for gcloud-python, see
    googleapis/google-cloud-python#215

  2. dhermes commented on Oct 3, 2014

    @dhermes

    @craigcitro FYI I saw you were a maintainer of google-apputils.

    Do you know the reason for strange the dateutil requirement in setup.py:

    REQUIRE = [
        "python-dateutil>=1.4,<2",
        "python-gflags>=1.4",
        "pytz>=2010",
        ]

    It is causing some "upstream" problems in this library.

  3. craigcitro commented on Oct 3, 2014

    @craigcitro
    Contributor

    yes -- this is an unfortunate issue around being able to test with our internal versions of python-dateutil. there's a thread going, but no conclusion yet.

    does anyone happen to know how big the API difference is between version 1.4 and 2+ of python-dateutil?

  4. dhermes commented on Oct 3, 2014

    @dhermes

    Code docs list contact info for Gustavo Niemeyer.

    @niemeyer would you be able to weigh in on the API difference between dateutil 1.4 and 2+?

    UPDATE: I confirmed that Gustavo has handed off maintenance.

    Code is hosted on LaunchPad.

    Other member and PyPI owner is Tomi Pievilaeinen who has contact info on ActiveState.

  5. craigcitro commented on Oct 3, 2014

    @craigcitro
    Contributor

    OK, looking at our code using dateutil, i think we can just drop it.

    let me at least ping the other thread, see if anyone has time to look at this.

  6. dhermes commented on Oct 3, 2014

    @dhermes

    Will it build? If it BUILDs, everyone is happy 👍

  7. craigcitro commented on Oct 4, 2014

    @craigcitro
    Contributor

    i think i'll be able to get a fix out soon, stay tuned.

  8. dhermes commented on Oct 4, 2014

    @dhermes

    w00t. Thanks for pushing through this.

  9. psypuff commented on Oct 5, 2014

    @psypuff
    Author

    Yay, thanks! 👍

  10. georgevreilly commented on Oct 10, 2014

    @georgevreilly

    I had to downgrade my Brew installation of protoc to 2.5 because of this implicit dependency on an ancient version of python-dateutil. We're also using Boto, which requires a modern version of dateutil.

    Since the only reason that google-apputils is being used is to get basetest, which is used only in test code, can the requirement be extracted from setup.py and put into test-requirements.txt?

  11. craigcitro commented on Oct 15, 2014

    @craigcitro
    Contributor

    ... and we're fixed! i just pushed a new version of google-apputils, we should be up and running.

  12. dhermes commented on Oct 15, 2014

    @dhermes

    w00t! I assume you're referring to: https://pypi.python.org/pypi/google-apputils/0.4.1

    How does the Ubuntu / debian source process work?

  13. craigcitro commented on Oct 15, 2014

    @craigcitro
    Contributor

    yep, just pushed the new release, and now this package can install with no trouble.

    i have no idea who/what controls the deb creation.

  14. xfxyjwf commented on Oct 15, 2014

    @xfxyjwf
    Contributor

    Thanks very much, Craig!

  15. edmonds commented on Oct 16, 2014

    @edmonds
    Contributor

    @craigcitro The Debian packaging for google-apputils-python is here: http://anonscm.debian.org/cgit/cloud/google-apputils-python.git. I've just updated it for 0.4.1 and uploaded it to the Debian archive.

  16. craigcitro commented on Oct 17, 2014

    @craigcitro
    Contributor

    wooooo thanks @edmonds !

  17. psypuff commented on Oct 20, 2014

    @psypuff
    Author

    Thanks Craig! 😄

  18. added a commit that references this issue on Jan 19, 2019
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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions