sage -unzip

[6bdad4c1-1e26-4f2f-a442-a01a2292c181]

As discussed on sage-devel [1], we lack a way to unzip files.

This very short python script does the job.

Nathann

[1] https://groups.google.com/d/topic/sage-devel/1uoTUsQ29Sw/discussion

Component: distribution

Author: Nathann Cohen

Branch/Commit: 727ac93

Reviewer: Volker Braun

Issue created by migration from https://trac.sagemath.org/ticket/19484

[6bdad4c1-1e26-4f2f-a442-a01a2292c181]

Branch: public/19484

[7ed8c4ca-6d56-4ae9-953a-41e42b4ed313]

Commit: 465d83c

[7ed8c4ca-6d56-4ae9-953a-41e42b4ed313]

Branch pushed to git repo; I updated commit sha1. New commits:

465d83c

trac #19484 - sage -unzip

[mkoeppe]

comment:3

See also #18781.

[dimpase]

comment:4

Replying to @mkoeppe:

See also #18781.

Right, this was the ticket I meant when I posted in sage-devel on this.

[vbraun]

comment:5

Can we at least put sage-unzip into build/bin/ and not expose it via a sage -unzip command line argument? It has no mathematical purpose, its just an internal tool for building Sage packages.

[vbraun]

comment:6

And I agree that there are lots of stupid command line options like sage --twisted. I don't think that means that we should add more out-of-scope commandline options.

[6bdad4c1-1e26-4f2f-a442-a01a2292c181]

comment:7

I thought that it would make more sense in the general bin folder. This is where one would find 'unzip' if we had chosen to package it.

As Dima raised, one can already find many non-mathematical 'utilities' in the general bin/ folder. Some examples: g++,cython,cythonize,python,scons,git, ...

[6bdad4c1-1e26-4f2f-a442-a01a2292c181]

comment:8

And I agree that there are lots of stupid command line options like sage --twisted. I don't think that means that we should add more out-of-scope commandline options.

Oh. Well I have no strong objection to the removal of sage -unzip. I just thought that all sage-something had to be exposed as "sage -something". How would you want it to appear?

Nathann

[vbraun]

comment:9

There is no reason to expose everything as commandline option. There is no sage --fix-pkg-checksums (i hope). The script using sage-unzip can just call it directly.

[6bdad4c1-1e26-4f2f-a442-a01a2292c181]

comment:10

There is no reason to expose everything as commandline option. There is no sage --fix-pkg-checksums (i hope).

Err... That's #18947.

The script using sage-unzip can just call it directly.

Okayokay. So I'll remove that line, I do not mind much.

Nathann

[7ed8c4ca-6d56-4ae9-953a-41e42b4ed313]

Branch pushed to git repo; I updated commit sha1. New commits:

35f2e34

trac #19484: No sage -unzip

[7ed8c4ca-6d56-4ae9-953a-41e42b4ed313]

Changed commit from 465d83c to 35f2e34

[7ed8c4ca-6d56-4ae9-953a-41e42b4ed313]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

727ac93

trac #19484: sage-unzip

[7ed8c4ca-6d56-4ae9-953a-41e42b4ed313]

Changed commit from 35f2e34 to 727ac93

[vbraun]

Reviewer: Volker Braun

[6bdad4c1-1e26-4f2f-a442-a01a2292c181]

comment:14

Cooool! Thanks,

Nathann

[vbraun]

Changed branch from public/19484 to 727ac93