Closed
Bug 1203121
Opened 9 years ago
Closed 8 years ago
update packages (2015-09-06): gengo
Categories
(Input Graveyard :: Code Quality, defect)
Input Graveyard
Code Quality
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: willkg, Unassigned)
References
Details
(Whiteboard: p=1 s=input.2015q4)
+++ This bug was initially created as a clone of Bug #1202288 +++
This bug covers upgrading the gengo library:
requirements/requirements.txt
--------------------- --------- ---------- --------
gengo ==0.1.19 0.1.26 outdated
This is in vendor/, too. If we can switch it to a vendor/src/, that'd be good.
Note: We have unittests that mock various parts of the library to test it, this can only be effectively tested live in production. Yay!
Reporter | ||
Comment 1•9 years ago
|
||
Fixing blocks and depends.
Reporter | ||
Comment 2•9 years ago
|
||
Grabbing this to do now.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Whiteboard: p=2 s=input.2015q3 → p=1 s=input.2015q3
Reporter | ||
Comment 3•9 years ago
|
||
The state of the repository tags, PyPI and the CHANGELOG make it difficult to understand what changed. 0.1.26 isn't tagged in their repository, but 0.1.27 is. However, 0.1.27 is not available on PyPI.
I wrote up an issue about it in their tracker: https://github.com/gengo/gengo-python/issues/58
Given that I can't figure out what changed, I'm kind of loathe to work on this now. I'll wait to see how that issue plays out plus whether they push 0.1.27 to PyPI before I proceed.
Reporter | ||
Comment 5•9 years ago
|
||
I'm unassigning myself from this. I'm not going to get to it before I transition off.
Assignee: willkg → nobody
Status: ASSIGNED → NEW
Comment 6•8 years ago
|
||
The Input service has been decommissioned (see bug 1315316) and has been replaced by a redirect to an external vendor (SurveyGizmo). I'm bulk WONTFIXing Input bugs that do not appear to be relevant anymore.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•