Error using NoDB on python3 about nodb HOT 14 OPEN

Perhaps we should just drop support for python2 as it only has a couple of months left?

from nodb.

I want to talk to @Miserlou before we publish to PyPI, but for now, can you:

pip install git+https://github.com/Miserlou/NoDB.git@4616921

from nodb.

which version are you using?

from nodb.

Hitting the same issue with python 3.6.3

using the same sample code as above and from the readme.

from nodb.

Which version of NoDB? All the has_keys were removed from the code base and other changes to make it python3 compatible in v0.4. v0.3.3 would still have them and it is not python3 compatible.

from nodb.

from nodb.

I also did a pip install nodb and it installed nodb 0.3.2.

Do you have plans to push the newer version to pypi?

from nodb.

Is there any progress with this issue? Thanks

from nodb.

I don't have access to push this to PyPI, but for now, you can:

pip install git+https://github.com/Miserlou/NoDB.git@4616921

You can also add this to your requirements file:

git+https://github.com/Miserlou/NoDB.git@4616921

from nodb.

I'm also seeing this, thanks @FlipperPA for the workaround.

from nodb.

However, there's a problem with @FlipperPA 's workaround. I'm trying to deploy a Falcon app to Elastic Beanstalk with Python 3.6. However, futures being installed which breaks the deploy. Therefore it seems impossible to use nodb in this context at the moment.

from nodb.

I have the same problem as @antgel

Using commit ID 4616921, it installs futures>=3.0.5 which is only for Python2.

For me on AWS Lambda this doesn't work:

Syntax error in module 'main': invalid syntax (_base.py, line 381)

Issue is here: agronholm/pythonfutures#41
Some info here: https://pypi.org/project/futures/

Python 3 users should not attempt to install it, since the package is already included in the standard library

Workaround

Delete <python path>/concurrent and <python path>/futures* from your zip package. It's hacky but I don't know a better way.

from nodb.

i've removed futures from requirements.txt in the latest pull request #26
this should resolve this issue

from nodb.

this will be resolved with #19

from nodb.