You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: