#221 fedpkg without arguments: AttributeError: 'Namespace' object has no attribute 'command' (PY3)
Closed: Fixed 5 years ago Opened 5 years ago by churchyard.

When I run fedpkg on Python 3 without arguments, I get:

$ fedpkg
Traceback (most recent call last):
  File ".../fedpkg/fedpkg/__main__.py", line 84, in main
    sys.exit(client.args.command())
AttributeError: 'Namespace' object has no attribute 'command'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File ".../fedpkg/.tox/py36/bin/fedpkg", line 11, in <module>
    load_entry_point('fedpkg', 'console_scripts', 'fedpkg')()
  File ".../RedHat/fedpkg/fedpkg/__main__.py", line 89, in main
    (client.args.command.__name__, e))
AttributeError: 'Namespace' object has no attribute 'command'

While on Python 2:

$ fedpkg
usage: fedpkg [-h] [--config CONFIG] [--release RELEASE | --dist DIST]
              [--module-name MODULE_NAME] [--user USER] [--password PASSWORD]
              [--runas RUNAS] [--path PATH] [--verbose] [--debug] [-q]
              [--user-config USER_CONFIG]
              {help,build,chain-build,clean,clog,clone,co,copr-build,commit,ci,compile,container-build,container-build-setup,diff,gimmespec,gitbuildhash,giturl,import,install,lint,local,mockbuild,mock-config,module-build,module-build-cancel,module-build-info,module-build-local,module-build-watch,module-overview,new,new-sources,patch,prep,pull,push,scratch-build,sources,srpm,switch-branch,tag,unused-patches,upload,verify-files,verrel,retire,update,request-repo,request-tests-repo,request-branch}
              ...
fedpkg: error: too few arguments

Not sure if rpkg or fedpkg bug. This was a change in Argparser. I remember being hit by this before: https://bugs.launchpad.net/cloud-init/+bug/1424277


Metadata Update from @cqi:
- Issue assigned to cqi

5 years ago

Metadata Update from @cqi:
- Assignee reset
- Issue set to the milestone: 1.34
- Issue tagged with: bug, py3

5 years ago

Metadata Update from @cqi:
- Issue assigned to cqi

5 years ago

Commit 4ee7051 fixes this issue

Login to comment on this ticket.

Metadata