Closed
Bug 1057295
Opened 10 years ago
Closed 9 years ago
(repo reorg) Identify all pip-installable dependencies of kuma and add them to pip requirements file
Categories
(developer.mozilla.org Graveyard :: Code Cleanup, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jbennett, Unassigned)
References
Details
(Whiteboard: [dev-papercut])
As a second step on bug 1057293, we should identify every Python module that can be pip-installed, and instead of bundling it in vendor add a line for it (pinning to appropriate version as necessary) to our pip requirements file.
Updated•10 years ago
|
Severity: normal → minor
Whiteboard: [dev-papercut]
Updated•10 years ago
|
Component: General → Code Cleanup
Comment 1•10 years ago
|
||
Ubernostrum, would you be willing to mentor a contributor through this? (second verse, same as the first...)
Flags: needinfo?(jbennett)
Reporter | ||
Comment 2•10 years ago
|
||
This one... could be a bug for a contributor to tackle with assistance. If someone really wants to jump on it, let me know and I'll see what I can do to help. Otherwise I'll likely just do it myself once the larger/scarier bits of reorg are done. The main reason I can think of for why this might *not* be a good community/contributor bug, btw, is that I'm not sure yet whether it would require changes to our deployment process. That will require some investigation up-front.
Flags: needinfo?(jbennett)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•