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

Adjust requirements to use enum-compat in place of enum34 #105

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Adjust requirements to use enum-compat in place of enum34 #105

wants to merge 1 commit into from

Conversation

MightySCollins
Copy link

When using enum34 issues can occur on any python version over 3.4. By using this package it will use the standard package on later versions of python. Using enum34 in later versions of python can cause issues with pip itself and break installs.

@MightySCollins
Copy link
Author

Looks like this was resolved in 25fa4f4. I am just curious if this is a better solution than just using the compact library which is what I have always done?

jiajie-chen-havas added a commit to jiajie-chen-havas/BingAds-Python-SDK that referenced this pull request Nov 16, 2022
BingAds v13.0.14 has a regression in the versioning for `enum34`.
This causes `pip install bingads==13.0.14` to break on Python versions `>=3.4,<3.9`,
as it interferes with the `enum` system library.

Solution is to revert the change to the `enum34` versioning in `setup.py`.

For reference, see:
* BingAds#105
* BingAds@25fa4f4
* https://github.com/BingAds/BingAds-Python-SDK/blame/13ae4fde11df8317083038a998ede49f4f9af1f2/setup.py#L18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant