Skip to content

Problem with new version of pip #13

Closed

Description

@marlontrapp

We started to have problems using the plugin with 'dockerizedPip: True' since yesterday (19/03/2018).

After some search we've found the cause of this error:

if (ret.error || ret.stderr.length != 0) {

This check is causing problem when a new version of pip is released and the docker image is not updated with that version. Because pip prints the warning message of new version available in the stderr.
Is there a reason to check for the size of stderr? The 'ret.error' isn't enough?

Activity

  1. added a commit that references this issue on Mar 20, 2018
  2. lucasventurasc commented on Mar 20, 2018

    @lucasventurasc
    Contributor

    I opened a pull request to fix the problem which happens when new pip versions are distributed.

  3. added a commit that references this issue on Mar 22, 2018
  4. Apathyman commented on Mar 22, 2018

    @Apathyman
    Contributor

    lucas' solution works for us, we're using a local fork until this can be fixed. I recommend using his branch until chchou approves the pull request.

  5. added a commit that references this issue on Mar 30, 2018
  6. added a commit that references this issue on Mar 30, 2018
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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions