Error with toml package when deploying project

[alfonsomhc]

I get this error when I deploy my project:

Packaging project as gzipped tarball.
  Could not find a version that satisfies the requirement toml==0.9.3 (from versions: 0.6.0, 0.6.5, 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.1, 0.9.2, 0.9.3.1)
No matching distribution found for toml==0.9.3

My understanding is that when zappa gets installed, the requirement is toml==0.9.3, but when it tries to make the package that will be send to Amazon, it does not find toml==0.9.3 (it does find toml==0.9.3.1 though).

Would it be a solution to update the requirements.txt (and require toml==0.9.3.1?

My environment is python 3.6, and the latest zappa available in pip.

By the way I think the deployment should fail in this kind of situation. I guess this is what #1235 is about.

[alfonsomhc]

I tried to install that package version:

$ pip install toml==0.9.3.1
Collecting toml==0.9.3.1
Installing collected packages: toml
  Found existing installation: toml 0.9.3
    Uninstalling toml-0.9.3:
      Successfully uninstalled toml-0.9.3
Successfully installed toml-0.9.3

I checked in pypi (https://pypi.python.org/pypi/toml) and it seems that in fact the two version packages are the same.

Therefore I don't think requirements.txt needs to be udpated. It's probably a bug in the packaging system that doesn't support four levels in the version?

[jwkvam]

I think the same issue is causing recent problems in this issue as well #64.

I believe the issue is that the code in toml version 0.9.3.1 refers to itself as 0.9.3 in it's code.

[mcrowson]

Would this be fixed if Zappa didn't peg requirement versions?

[Miserlou]

This is toml's problem, pinned requirements or not.

[mcrowson]

but it would allow the user to pin the working version of toml and still use the latest/greatest zappa

[tycoles]

Yeah it looks like we either roll back to toml 0.9.2 (which may not be possible) or wait for a new toml release (0.9.4). Zappa version 0.44.3 is the latest version of Zappa with working toml (0.9.2) in it, in case anyone out there is wondering.