Opened 6 years ago

Last modified 3 years ago

#21033 closed defect

package type = pip needs documentation — at Version 7

Reported by: Matthias Köppe Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: Vincent Delecroix, Volker Braun, Erik Bray, Jeroen Demeyer, Leif Leonhardy, John Palmieri Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by Matthias Köppe)

There are now several packages where build/pkgs/PACKAGE/type is "pip".

Is there any documentation on this?

Some related tickets:

  • #20218: Use pip to install Python dependencies
  • #19213: For packages listed in build/pkgs/piprules, allow 'sage --optional' to list them

Change History (7)

comment:1 Changed 6 years ago by Jeroen Demeyer

I don't know if everybody agrees to "officially" support the pip type packages. It was mainly meant as stopgap for some disappearing old-style packages.

comment:2 Changed 6 years ago by Jeroen Demeyer

Description: modified (diff)

comment:3 Changed 6 years ago by Jeroen Demeyer

Also, shouldn't the way in which a package is installed (traditional way vs. pip way) be orthogonal to whether a package is considered standard, optional, or experimental?

Certainly not standard since we need to ship the sources of standard packages with Sage. They aren't really optional nor experimental either. I see it as just a shortcut to ./sage --pip install PKG.

comment:4 Changed 6 years ago by Volker Braun

The pip-type package could be enhanced to use a mirrored tarball if there is one, then we could also use it for standard packages. Though really the benefit seems pretty small compared to putting pip install in the spkg-install.

comment:5 in reply to:  1 Changed 6 years ago by Matthias Köppe

Replying to jdemeyer:

I don't know if everybody agrees to "officially" support the pip type packages. It was mainly meant as stopgap for some disappearing old-style packages.

"Official" or not, documentation is better than no documentation, no?

comment:6 in reply to:  2 Changed 6 years ago by Matthias Köppe

Replying to jdemeyer:

Description modified

Let me ask again my question which you removed from the description above:

I tried to add a package of this type for pypolymake (for #20892), but adding the file build/pkgs/pypolymake/type does not seem to enable "sage -i pypolymake". What am I missing?

comment:7 Changed 6 years ago by Matthias Köppe

Description: modified (diff)
Note: See TracTickets for help on using tickets.