Skip to content
This repository has been archived by the owner on Dec 31, 2023. It is now read-only.

ModuleNotFoundError: No module named pkg_resources #322

Closed
tnguyen14 opened this issue May 9, 2022 · 2 comments
Closed

ModuleNotFoundError: No module named pkg_resources #322

tnguyen14 opened this issue May 9, 2022 · 2 comments
Assignees
Labels
api: monitoring Issues related to the googleapis/python-monitoring API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@tnguyen14
Copy link

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Please run down the following list and make sure you've tried the usual "quick fixes":

If you are still having issues, please be sure to include as much information as possible:

Environment details

  • OS type and version: linux
  • Python version: 3.8.13
  • pip version: pip --version
  • google-cloud-monitoring version: 2.9.1

Steps to reproduce

Code example

Stack trace

Python 3.8.13 (default, Mar 18 2022, 13:52:37)
[GCC 9.3.1 20200408 (Red Hat 9.3.1-2)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from google.cloud import monitoring_v3
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/.../dependencies/site-packages/google/cloud/monitoring_v3/__init__.py", line 17, in <module>
    from .services.alert_policy_service import AlertPolicyServiceClient
  File "/.../dependencies/site-packages/google/cloud/monitoring_v3/services/alert_policy_service/__init__.py", line 16, in <module>
    from .client import AlertPolicyServiceClient
  File "/.../dependencies/site-packages/google/cloud/monitoring_v3/services/alert_policy_service/client.py", line 20, in <module>
    import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

This library depends on setuptools, which was included in google-api-core up to 2.4.0, but was removed in 2.5.0 googleapis/python-api-core#339

@product-auto-label product-auto-label bot added the api: monitoring Issues related to the googleapis/python-monitoring API. label May 9, 2022
@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels May 10, 2022
@parthea parthea added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed 🚨 This issue needs some love. triage me I really want to be triaged. labels May 17, 2022
@parthea parthea self-assigned this May 17, 2022
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label May 17, 2022
@parthea
Copy link
Contributor

parthea commented May 17, 2022

Hi @tnguyen14 ,

Thanks for reporting this issue and proposing a fix! I'm going to check if we can remove the dependency on setuptools.

I've also opened an issue for a long term fix: googleapis/gapic-generator-python#1316

@parthea parthea added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. labels Jun 27, 2022
@parthea
Copy link
Contributor

parthea commented Dec 15, 2022

Closed via eaaca48

@parthea parthea closed this as completed Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api: monitoring Issues related to the googleapis/python-monitoring API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants