Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

buildozer help fail #285

Closed
pat1 opened this issue Feb 8, 2016 · 3 comments
Closed

buildozer help fail #285

pat1 opened this issue Feb 8, 2016 · 3 comments

Comments

@pat1
Copy link
Contributor

pat1 commented Feb 8, 2016

with git 0.32dev

buildozer help
# Check configuration tokens
Usage:
    buildozer [--profile <name>] [--verbose] [target] <command>...
    buildozer --version

Available targets:
  android            Android target, based on python-for-android project
Traceback (most recent call last):
  File "/usr/bin/buildozer", line 9, in <module>
    load_entry_point('buildozer==0.32dev', 'console_scripts', 'buildozer')()
  File "/usr/lib/python2.7/site-packages/buildozer/scripts/client.py", line 13, in main
    Buildozer().run_command(sys.argv[1:])
  File "/usr/lib/python2.7/site-packages/buildozer/__init__.py", line 976, in run_command
    getattr(self, cmd)(*args)
  File "/usr/lib/python2.7/site-packages/buildozer/__init__.py", line 1037, in cmd_help
    self.usage()
  File "/usr/lib/python2.7/site-packages/buildozer/__init__.py", line 892, in usage
    doc = m.__doc__.strip().splitlines()[0].strip()
AttributeError: 'NoneType' object has no attribute 'strip'
@kmonson
Copy link

kmonson commented Feb 9, 2016

I can confirm this.

@mikeyjkmo
Copy link

I'm also seeing this problem. I've just installed the latest dev version with
pip install https://github.com/kivy/buildozer/archive/master.zip

@kived
Copy link
Contributor

kived commented Feb 26, 2016

The android_new module doesn't have a docstring. Everything else should work with buildozer, other than this usage message.

Docstrings should only be used for documenting code, not for usage messages and such. They are also stripped out of optimized builds, which is a good reason not to rely on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants