-
Notifications
You must be signed in to change notification settings - Fork 840
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
pika.compat should be a module, not package #978
Conversation
Fixes the issue raised here: #945 (comment)
Codecov Report
@@ Coverage Diff @@
## master #978 +/- ##
======================================
Coverage 82.5% 82.5%
======================================
Files 19 19
Lines 3779 3779
Branches 567 567
======================================
Hits 3118 3118
Misses 508 508
Partials 153 153
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. But I didn't quite understand why the package compat didn't work in #945. Would you mind elaborating?
@vitaly-krugl because |
So, one option was to list |
Yes, sure, like this: setuptools.setup(
…
packages=['pika', 'pika.adapters', 'pika.compat'],
…
) or even better (autodiscovery): from setuptools import find_packages
setuptools.setup(
…
packages=find_packages(exclude=['*.tests', '*.tests.*', 'tests.*', 'tests']),
…
) |
@vitaly-krugl apologies that I missed your question and thank you @anton-ryzhov for answering it. |
Thanks @anton-ryzhov! @lukebakken - I like the |
I doubt Pika will add packages in the future. The issue around |
pika.compat should be a module, not package (cherry picked from commit 973ebc3)
Fixes the issue raised here:
#945 (comment)