aliyun / aliyun/aliyun-openapi-python-sdk

aliyun-sdk-core doesn't work with crpythongraphy

Open
#470 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
578
PR merge metrics
No merged PRs in 30d

Description

  • Python Version:
    python 3.6
  • aliyunsdkcore Version:
    2.13.36
  • API:
    Initialization of Function Compute

Yesterday a new 37.0.0 version of cryptography has been released. aliyun-python-sdk-core doesn't have an upper bound for this version in the setup.py so it started picking cryptography 37.0.0 on pip install aliyun-python-sdk-core. When a package with aliyun-python-sdk-core and cryptography 37.0.0 is deployed to Function Compute with Python 3.6, the FC fails with the error below on invoke:

[ERROR] {'errorMessage': "Module initialization error: 'module 'lib' has no attribute 'X509_V_FLAG_CB_ISSUER_CHECK''", 'errorType': 'UserCodeError', 'stackTrace': ["AttributeError: module 'lib' has no attribute 'X509_V_FLAG_CB_ISSUER_CHECK'"]}

I believe that aliyun-python-sdk-core should require cryptography <=37.0.0,

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting aliyun-python-sdk-core/setup3.py at the dependency declaration linked in the issue. Confirm the Python 3.6 and Function Compute failure context, then update the cryptography requirement as requested; done when installation no longer selects an incompatible release.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.