#42907 closed submission (fixed)
py-tox @1.6.1 tox: virtualenv-based automation of test activities
| Reported by: | steenzout (Pedro Salgado) | Owned by: | neverpanic (Clemens Lang) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.1 |
| Keywords: | Cc: | ||
| Port: | py-tox |
Description
Hello,
here goes my port to build tox.
cheers, Pedro Salgado
Attachments (1)
Change History (6)
Changed 11 years ago by steenzout (Pedro Salgado)
| Attachment: | py-tox.tgz added |
|---|
comment:1 Changed 11 years ago by steenzout (Pedro Salgado)
The tox_select port was submitted as well.
please check https://trac.macports.org/ticket/42908.
comment:2 Changed 11 years ago by neverpanic (Clemens Lang)
| Owner: | changed from macports-tickets@… to cal@… |
|---|---|
| Port: | py-tox added |
Committed in r118036 with the following changes:
- Added required maintainer line. Please run
port lint --nitpickbefore submitting Portfiles, in this caseport lint --nitpick -- subport=py27-toxif you're in the directory of the Portfile. I've set the maintainer to nomaintainer for now, let me know if you'd like to maintain this port (and decide whether to list openmaintainer as explained in http://guide.macports.org/#project.update-policies.nonmaintainer). - Added
25and26topython.versionssince you provided select files for them, so I guessed that's what you wanted?
Can tox be built with python 3.x? If so, is there any reason why you didn't enable the 3.x subports?
comment:3 Changed 11 years ago by neverpanic (Clemens Lang)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 Changed 11 years ago by steenzout (Pedro Salgado)
tox can be built on python 3.x but since I don't use it I didn't even think of adding it. let's face it I had already spent 2h reading the docs and checking for patterns / best practices while browsing through other ports to figure out how to to this again :)
I'll updated my Portfile, check the tox repo to see what other Python versions are being maintained, run the lint command and submit an update.
I'd love to maintain the port but the only examples I looked had a <username> from a <username>@macports.org account. I checked the macports membership section but I wasn't sure how many ports I had to contribute :) I'll just try my luck right after I read the whole doc beginning to the end instead of jumping through sections.
thx for your help.
comment:5 Changed 11 years ago by neverpanic (Clemens Lang)
I've added you as maintainer in r118067. You don't have to be a committer to maintain a port; just open tickets, attach patches and set the keywords to "maintainer" and/or "haspatch". If that doesn't help, ping macports-dev after a while.
I know the documentation can sometimes be daunting, and a lot of stuff isn't documented at all. If you have any questions, feel free to drop by in IRC, or send mail to macports-dev.
Portfile + additional files.