Closed Bug 562476 Opened 15 years ago Closed 15 years ago

command line options are not specifiable in the mozmill.cli() function

Categories

(Testing Graveyard :: Mozmill, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: k0scist, Unassigned)

Details

(Whiteboard: [mozmill-2.0][CLI])

mozmill.cli(), the command line entry-point for the `mozmill` script, neither takes nor transmits command line arguments. This relies then on `optparse`'s behavior to parse sys.argv[1:]. This makes it uncallable as a python function. Likewise, the mozmill.CLI class which it front-ends has no such facility. Adding such a facility would make the command line entry point callable from python with mangling sys.argv
Whiteboard: [mozmill-1.4.2?]
Whiteboard: [mozmill-1.4.2?] → [mozmill-1.4.2-]
I'm not really sure if I understand this problem here. Jeff, could a possible fix on bug 564537 help you here?
OS: Linux → All
Whiteboard: [mozmill-1.4.2-] → [mozmill-2.0?][CLI]
this is now fixed on master, closing
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Which changeset made it possible?
Whiteboard: [mozmill-2.0?][CLI] → [mozmill-2.0][CLI]
Not sure, entirely? It landed with pluggable-events + the command line refactor, so whatever changeset made it go from e.g. def cli(): CLI().run() to def cli(args=sys.argv[1:]): CLI(args).run()
It's always helpful to have the changeset listed in the bug for verification purposes. It's kinda hard at a later stage to identify a regression without that information.
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.