setup.py still at version 0.1.1? #8

Closed
opened 2018-01-05 05:33:34 +00:00 by import_bot · 1 comment
Collaborator

Ran this morning to try and fetch 0.1.3. Ended up with 0.1.1 still.

$ pip3 install --upgrade hg+https://torsion.org/hg/atticmatic
Collecting hg+https://torsion.org/hg/atticmatic
Cloning hg https://torsion.org/hg/atticmatic to /tmp/pip-2rm1xl7f-build
Installing collected packages: atticmatic
Found existing installation: atticmatic 0.1.1
Uninstalling atticmatic-0.1.1:
Successfully uninstalled atticmatic-0.1.1
Running setup.py install for atticmatic
Successfully installed atticmatic-0.1.1


Imported from Taiga issue 7 (done). Created on 2015-07-30T09:24:14+0000 by Thomas Harold.

Ran this morning to try and fetch 0.1.3. Ended up with 0.1.1 still. $ pip3 install --upgrade hg+https://torsion.org/hg/atticmatic Collecting hg+https://torsion.org/hg/atticmatic Cloning hg https://torsion.org/hg/atticmatic to /tmp/pip-2rm1xl7f-build Installing collected packages: atticmatic Found existing installation: atticmatic 0.1.1 Uninstalling atticmatic-0.1.1: Successfully uninstalled atticmatic-0.1.1 Running setup.py install for atticmatic Successfully installed atticmatic-0.1.1 --- Imported from Taiga issue 7 (done). Created on 2015-07-30T09:24:14+0000 by Thomas Harold.
import_bot added the
bug
label 2018-01-05 05:33:34 +00:00
Author
Collaborator

Fixed, and added a test so this doesn't happen again. The problem was just that the setup.py was out of date.


Comment on 2015-07-30T15:14:32+0000 by Dan Helfman.

Fixed, and added a test so this doesn't happen again. The problem was just that the setup.py was out of date. --- Comment on 2015-07-30T15:14:32+0000 by Dan Helfman.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#8
No description provided.