Python:如何将类的功能分成多个文件? [英] Python: How can I separate functions of class into multiple files?
问题描述
我知道这个问题已经问过几次了,但是我不太明白以前的答案,并且/或者我认为解决方案不能完全代表我的目标。我对Python还是很陌生,所以我很难解决这个问题。
I know this has been asked a couple of times, but I couldn't quite understand the previous answers and/or I don't think the solution quite represents what I'm shooting for. I'm still pretty new to Python, so I'm having a tough time figuring this out.
我有一个主类,其中包含许多不同的函数。变得越来越难以管理。我希望能够将这些功能分离到一个单独的文件中,但是我发现很难找到一个好方法。
I have a main class that has a TON of different functions in it. It's getting hard to manage. I'd like to be able to separate those functions into a separate file, but I'm finding it hard to come up with a good way to do so.
这里到目前为止,我所做的是:
Here's what I've done so far:
main.py
import separate
class MainClass(object):
self.global_var_1 = ...
self.global_var_2 = ...
def func_1(self, x, y):
...
def func_2(self, z):
...
# tons of similar functions, and then the ones I moved out:
def long_func_1(self, a, b):
return separate.long_func_1(self, a, b)
separate.py
def long_func_1(obj, a, b):
if obj.global_var_1:
...
obj.func_2(z)
...
return ...
# Lots of other similar functions that use info from MainClass
之所以这样做,是因为如果这样做:
I do this because if I do:
obj_1 = MainClass()
我希望能够做到:
obj_1.long_func_1(a,b)
而不是:
separate.long_func_1(obj_1,a,b)
我知道这有点像nit-picky,但我希望几乎所有代码都以 obj_1开头。
,所以不会造成混乱。
I know this seems kind of nit-picky, but I want just about all of the code to start with obj_1.
so there isn't confusion.
我现在在做什么更好的解决方案?我当前设置的唯一问题是:
Is there a better solution that what I'm currently doing? The only issues that I have with my current setup are:
- 我必须更改函数的两个实例的参数
- 似乎不必要地重复
推荐答案
我实际上对此感到惊讶不是重复的。我看到了一些类似的问题,我认为没有一个简明的答案,所以这就是我的做法:
I'm actually surprised this isn't a duplicate. I saw some similar questions and I think there is nowhere a concise answer, so here is how I do it:
- Class(或一组)实际上是一个完整的模块。您不必这样做,但是如果您要在多个文件上拆分一个类,我认为这是最干净的(观点)。
- 定义在<$中c $ c> __ init __。py ,通过有意义的分组将方法分割为文件。
- 方法文件只是具有功能的常规python文件,除了您之外不能忘记自我作为第一个论点。您可以在此处使用辅助方法,都可以使用
self
而不能。 - 方法直接导入到类定义中。
- Class (or group of) is actually a full module. You don't have to do it this way, but if you're splitting a class on multiple files I think this is 'cleanest' (opinion).
- The definition is in
__init__.py
, methods are split into files by a meaningful grouping. - A method file is just a regular python file with functions, except you can't forget 'self' as a first argument. You can have auxiliary methods here, both taking
self
and not. - Methods are imported directly into the class definition.
假设我的类是适合的gui (这实际上是我第一次这样做)。因此,我的文件层次结构可能类似于
Suppose my class is some fitting gui (this is actually what I did this for first time). So my file hierarchy may look something like
mymodule/
__init__.py
_plotstuff.py
_fitstuff.py
_datastuff.py
因此绘图内容将具有适合的绘图方法东西包含拟合方法,而数据东西包含用于加载和处理数据的方法-您明白了。按照惯例,我用 _
标记文件,以表示这些文件并不是要直接导入模块之外的任何位置。因此,例如 _plotsuff.py
可能看起来像:
So plot stuff will have plotting methods, fit stuff contains fitting methods, and data stuff contains methods for loading and handling of data - you get the point. By convention I mark the files with a _
to indicate these really aren't meant to be imported directly anywhere outside the module. So _plotsuff.py
for example may look like:
def plot(self,x,y):
#body
def clear(self):
#body
等。现在重要的是 __ init __。py
:
class Fitter(object):
def __init__(self,whatever):
self.field1 = 0
self.field2 = whatever
#Imported methods
from ._plotstuff import plot, clear
from ._fitstuff import fit
from ._datastuff import load
from ._static_example import something
#Some more small functions
def printHi(self):
print("Hello world")
#static methods need to be set
somthing = staticmethod(something)
汤姆·索耶(Tom Sawyer)提到PEP-8建议将所有进口商品放在顶部,因此您不妨将它们放在 __ init __
,但我更喜欢这种方式。我不得不说,我的Flake8检查器没有抱怨,因此很可能是PEP-8兼容。
Tom Sawyer mentions PEP-8 recommends putting all imports at the top, so you may wish to put them before __init__
, but I prefer it this way. I have to say, my Flake8 checker does not complain, so likely this is PEP-8 compliant.
请注意 from ... import。 ..
对于隐藏一些您不想通过类对象访问的方法中的帮助器功能特别有用。我通常还将类的自定义异常放在不同的文件中,但直接将它们导入,以便可以将它们作为 Fitter.myexception
访问。
Note the from ... import ...
is particularly useful to hide some 'helper' functions to your methods you don't want accessible through objects of the class. I usually also place the custom exceptions for the class in the different files, but import them directly so they can be accessed as Fitter.myexception
.
如果此模块在您的路径中,则可以使用以下命令访问您的班级
If this module is in your path then you can access your class with
from mymodule import Fitter
f = Fitter()
f.load('somefile') #Imported method
f.plot() #Imported method
不完全直观,但也不难。针对您的特定问题的简短版本是您已关闭-只需将导入移至类中,并使用
Not completely intuitive, but not to difficult either. The short version for your specific problem was your were close - just move the import into the class, and use
from separate import long_func_1
别忘了你的自己
!
这篇关于Python:如何将类的功能分成多个文件?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!