Bug 1794263 - Multiple imports from the same library in the .py files in geo-rep
Summary: Multiple imports from the same library in the .py files in geo-rep
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kshithij Iyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-23 06:20 UTC by Kshithij Iyer
Modified: 2020-03-17 03:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-17 03:18:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 24063 0 None Open [geo-rep] Merging multiple import into single import 2020-01-23 06:25:21 UTC

Description Kshithij Iyer 2020-01-23 06:20:29 UTC
Description of problem:
Geo-replication has a large number of repeated imports as shown below:
```
from syncdutils import set_term_handler, finalize, lf
from syncdutils import log_raise_exception, FreeObject, escape
```

There imports can be clubbed together as shown below:
``
from syncdutils import (set_term_handler, finalize, lf,
                        log_raise_exception, FreeObject, escape)
``` 

Version-Release number of selected component (if applicable):
Whatever is the current master version.

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2020-01-23 06:25:23 UTC
REVIEW: https://review.gluster.org/24063 ([geo-rep] Merging multiple import into single import) posted (#1) for review on master by Kshithij Iyer

Comment 2 Worker Ant 2020-03-17 03:18:31 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/1105, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.