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

use of pbr breaks with zappa #402

Closed
jwkvam opened this issue Apr 7, 2017 · 1 comment
Closed

use of pbr breaks with zappa #402

jwkvam opened this issue Apr 7, 2017 · 1 comment

Comments

@jwkvam
Copy link

jwkvam commented Apr 7, 2017

I'm using Zappa to run some code on AWS Lambda. When I use Zappa's slim_handler to zip up my python code and packages I run into problems with mock. For the time being I've hardcoded the version info to workaround this issue and remove the dependency on pbr. My original bug is here, Miserlou/Zappa#779.

I don't really know where the issue is, but I was hoping you guys might have some insight, thanks!

File "/tmp/pip-build-c1VilV/mock/mock/__init__.py", line 2, in <module>
  File "/tmp/pip-build-c1VilV/mock/mock/mock.py", line 71, in <module>
  File "/tmp/pip-build-c1VilV/pbr/pbr/version.py", line 460, in semantic_version
  File "/tmp/pip-build-c1VilV/pbr/pbr/version.py", line 447, in _get_version_from_pkg_resources
  File "/tmp/pip-build-c1VilV/pbr/pbr/packaging.py", line 750, in get_version
Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name mock was given, but was not able to be found.
@rbtcollins
Copy link
Member

You're missing the dist-info metadata for the installed packages. See #385

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

2 participants