Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Conflict between delegator and delegator.py
See original GitHub issueif I have both delegator and delegaror.py installed python will pick the first one and I’ll get an error message saying AttributeError: module 'delegator' has no attribute 'run', is there a way to ensure the right module is being used when both of these packages are installed?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Automatic delegation for classes extending python abc ...
The delegator methods are made in a separate function because we need a namespace where name doesn't change after the function's been created....
Read more >a key function of nursing: delegation is not a mysterious art ...
Under-delegating can occur if delegators believe that delegation can be interpreted as a lack of ability on their part to accomplish the jobs...
Read more >Delegation vs Inheritance in Java
Delegation can be viewed as a relationship between objects where one object forwards certain method calls to another object, called its delegate ...
Read more >amitt001/delegator.py: Subprocesses for Humans 2.0.
Delegator.py is a simple library for dealing with subprocesses, inspired by both envoy and pexpect (in fact, it depends on it!). This module...
Read more >What is the difference between proxy class and delegation ...
A proxy has no other functionality than to forward actions. A class that delegates also adds its own functionality. In that, effectively, a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It does not. The problem is two differently-named packages on pypi with the same module-name. Don’t call your module delegator is it already exists on pypi.
Django has set a very bad standard here, naming packages like “django-foo” that you use by “importing foo” instead of “import django_foo”.
Closing due to inactivity 👍