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.

Sign up for GitHub

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

Jump to bottom

Conflicts with py-test-utils-0.1.0: installs files into the same place: problematic file: /usr/local/lib/python3.9/site-packages/test_utils/__init__.py #169

Open
yurivict opened this issue Jan 25, 2024 · 1 comment
Open

Conflicts with py-test-utils-0.1.0: installs files into the same place: problematic file: /usr/local/lib/python3.9/site-packages/test_utils/__init__.py #169

yurivict opened this issue Jan 25, 2024 · 1 comment
Assignees
@parthea
Labels
next major: breaking change this is a change that we should wait to bundle into the next major version 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

@yurivict
Copy link

Could you please use a namespace not intersecting with other existing Python packages:

===>   Registering installation for py39-google-cloud-testutils-1.4.0 as automatic
Installing py39-google-cloud-testutils-1.4.0...
pkg-static: py39-google-cloud-testutils-1.4.0 conflicts with py39-test-utils-0.1.0 (installs files into the same place).  Problematic file: /usr/local/lib/python3.9/site-packages/test_utils/__init__.py
@parthea parthea self-assigned this Jan 25, 2024
@parthea parthea added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. next major: breaking change this is a change that we should wait to bundle into the next major version labels Jan 25, 2024
@parthea
Copy link
Contributor

parthea commented Jan 25, 2024

@yurivict , Thanks for reporting this issue! I'm not able to provide an ETA on a fix as this will be a breaking change for the library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@parthea parthea

Labels
next major: breaking change this is a change that we should wait to bundle into the next major version 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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yurivict @parthea