Bug 1115864

Summary: Better naming/structuring required for libgfapi-python modules
Product: [Community] GlusterFS Reporter: Humble Chirammal <hchiramm>
Component: libgfapiAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact: Sudhir D <sdharane>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-17 15:57:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Humble Chirammal 2014-07-03 09:23:22 UTC 
Description of problem:

Libgfapi-python module (http://review.gluster.org/#/c/7805/3/test/unit/gluster/test_gfapi.py ) currently import :

from glusterfs import gfapi	
from glusterfs import api
			
This is confusing. It is required to move the api (which are really internal calls and not exposed) to another file. test_api.py for example. This file is for unit testing gfapi.py only.


Version-Release number of selected component (if applicable):

http://review.gluster.org/#/c/7805/
Comment 1 Niels de Vos 2016-06-17 15:57:04 UTC 
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.
Comment 2 Natalie Marie 2024-07-29 15:49:30 UTC Comment hidden (spam)