AWS lambda packaging

[SimonWoolf]

Customer states that when they try to run a python program packaged for aws lambda that uses ably, they get a "cannot import name '_AES'" error, though it works fine when run locally. They're not using crypto features, and are using the default package (from pip install ably), which doesn't include crypto. Customer states they are using python 3.6, but declines to provide any more details or steps to reproduce their issue.

[mattheworiordan]

@jdavid would be good to address this too if you can?

[jdavid]

Actually the version that makes crypto optional (commit 2f7e0d3) has not been released yet. A new release should fix it; but maybe merge #98 first?

[mattheworiordan]

@jdavid I wanted to, but you've not responded to my question re: failures

[jdavid]

I have answered in #88 where a similar question/comment has been posted. The failures don't seem related to crypto. Hopefully the errors will be fixed this afternoon.

[mattheworiordan]

Ok, thanks @jdavid. Shout if you need me to merge #98 now or not.

[jdavid]

PR #98 can be merged already.

[mattheworiordan]

Is this now resolved @jdavid?

[jdavid]

Yes. Should the customer validate?

[jdavid]

I think we can close this, should be good with the 1.0.1 release