Opened 3 years ago

Last modified 11 months ago

#20343 new enhancement

Write a setup.py for chutney

Reported by: dawuud Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: install
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I want to use the chutney API for various projects. It would make it much easier to use if it had a proper setup.py

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by teor

Keywords: install added
Type: defectenhancement

Do we need chutney to be versioned to have a setup.py? (#20344)

comment:2 Changed 2 years ago by teor

Owner: teor deleted
Status: newassigned

Disowning tickets I don't intend to work on in the next 6 months.

comment:3 Changed 2 years ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

comment:4 Changed 11 months ago by exarkun

Do we need chutney to be versioned to have a setup.py? (#20344)

Versioning is great but I don't think it is a requirement for this ticket. Versioning would probably be a requirement for issuing a _release_ and having a setup.py would also be helpful in producing a release. But setup.py will also let folks install this via a git URL or a hand-build source archive.

comment:5 Changed 11 months ago by exarkun

Practically speaking, it looks like it would be a good idea to re-arrange the repository structure a good deal before writing a setup.py. distutils/setuptools could probably be bent to deal with the current structure but it will be a lot easier if chutney changes to look more like a typical Python project.

Are folks okay with that? I don't know why it is arranged as it currently is. I would assume just non-familiarity with Python conventions on the part of the author (and/or non-existence of those conventions at whatever time Chutney was written).

Note: See TracTickets for help on using tickets.