Python 3 version fork and some questions

[BEEugene]

Hi, again!
First, I've forked the package and made python 3 support.
I am not an experienced user of python and Github, should I do some commits or leave the fork to leave by itself?

The second problem is that with the following project structure:

-project:
--fold0
---subfolder
----more subfolders
---subfold2
--fold1
--fold2

the public-release export only modules from fold0, others are not exported.
For example, I've
import fold0.subfolder... module which is imported in subfold2.
The public-release exports this successfully and rewrites as
from helpers import ...
but the other imports from fold1 and fold1 stays the same as
from fold1... import ...
Is this a regular thing? (or maybe I broke smth:))

[BEEugene]

Found an answer to the second problem.
I didn't have the init.py file in fold1, so the script didn't saw them.
For the fold2 I've changed a pipeline in a "project" scope.

[petered]

Nice, apologies for the 4-year-late reply. Should I merge your fork? Is it good?

[BEEugene]

Ok. Well, not sure about that, didn't use it for long time, but it definitely worked somehow and helped me, thank you.