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

Drop 3.6 support #33

Closed
jordaneremieff opened this issue Feb 3, 2019 · 4 comments
Closed

Drop 3.6 support #33

jordaneremieff opened this issue Feb 3, 2019 · 4 comments
Labels
improvement Improve an existing feature

Comments

@jordaneremieff
Copy link
Collaborator

I don't think this project should need to support 3.6 since AWS Lambda supports 3.7. I would have started from this perspective, but initially I included the Azure Functions adapter which only supported 3.6.

@jordaneremieff jordaneremieff added the improvement Improve an existing feature label Feb 3, 2019
@jordaneremieff
Copy link
Collaborator Author

3.6 dropped with 0.6.7

@chgangaraju
Copy link

It would be really helpful if it has 3.6 support unless it's really difficult to maintain. It matters when we are working on different projects and need to use a different python version for one project because of a specific library.

@jordaneremieff
Copy link
Collaborator Author

jordaneremieff commented May 22, 2019

@chgangaraju I don't think it should be too difficult to maintain and may be open to supporting 3.6 again, what are some example cases where this support would be useful?

@jordaneremieff
Copy link
Collaborator Author

I am going to close this again for now, but willing to reconsider if there are examples to support 3.6 again - it is not apparent to me where this would be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improve an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants