Skip to content

Document that python setup.py develop add the symlink to easy-install.pth #7422

Closed

Description

@NelleV

Else, it's really hard to "uninstall" matplotlib.

Activity

  1. anntzer commented on Nov 8, 2016

    @anntzer
    Contributor

    It looks like pip install -e . / pip uninstall matplotlib handles this fine. I'd suggest switching the docs to recommending using those (specifically pip install --upgrade --no-deps -e ., which is the more practical set of flags I think).

  2. tacaswell commented on Nov 8, 2016

    @tacaswell
    Member

    Both methods are currently in the docs as of #7229

  3. anntzer commented on Nov 8, 2016

    @anntzer
    Contributor

    I'd rather move the pip-based method first (and explicitly recommend it), given, again, that it does not suffer from the issue @NelleV mentions. (But it is only better if you remember to include the --upgrade (and possibly --no-deps) flags.)

  4. efiring commented on Nov 8, 2016

    @efiring
    Member

    I think --upgrade is dangerous; at least in some versions of pip, it upgrades all dependencies without the courtesy of even listing them and then asking if that is what you really want to do. Does --no-deps reliably take care of that, or is it only available in newer versions of pip? After being bitten by the unwanted upgrades, I switched to always uninstalling first, so --upgrade is not needed.
    Apart from that, I agree, the pip methods should be emphasized because they handle uninstalling.

  5. QuLogic commented on Nov 8, 2016

    @QuLogic
    Member

    In a conda env, I've never had to use --upgrade; not too sure why that is though.

  6. anntzer commented on Nov 8, 2016

    @anntzer
    Contributor

    I never had this issue while using --no-deps. I have no idea about whether this was broken on previous versions but we can always first suggest pip install --upgrade pip and then we only have to care about the latest pip, which I'm certain implements this correctly :-)

  7. petehuang commented on Jan 6, 2017

    @petehuang
    Contributor

    So the latest on this is that we feel positive about two changes in https://github.com/matplotlib/matplotlib/blob/master/doc/devel/contributing.rst:

    1. Add language around pip install --upgrade pip to ensure that all pip commands on the page run well
    2. Move a variant of the pip install method first (before python setup.py develop). Remaining question is which exact variant we want? Thoughts?
  8. NelleV commented on Jan 6, 2017

    @NelleV
    MemberAuthor

    fyi, I am against moving the pip command before the python setup.py install.
    It is not a standard way of installing python packages. I would suggest waiting until that is the case (as IMO it is very unlikely that it will ever become the standard way to install python packages).

  9. efiring commented on Jan 6, 2017

    @efiring
    Member

    @NelleV, in https://docs.python.org/3/installing/, it says,

    pip is the preferred installer program. Starting with Python 3.4, it is included by default with the Python binary installers.

    You would maintain that although it is officially "preferred" it is not "standard", and is unlikely to become so?

  10. tacaswell commented on Jan 7, 2017

    @tacaswell
    Member

    Also see https://pip.pypa.io/en/stable/reference/pip_install/#usage .
    This is also how IPython recommends installation http://ipython.readthedocs.io/en/stable/install/install.html?highlight=setup.py#installation-from-source

    I have been test-driving always using pip for installing things from source for the last few months and am pretty happy. It is less to type and reliably uninstalls (both develop and normal installs).

    Going down this path also offers a sliver of hope that the setptools/distutils Gordian knot will ever be untangled (by localizing it all in pip first).

    I am comfortable with mpl being on the leading edge of this shift.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions