You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Disclaimer: I know we're neither Google, Numpy nor anything similar, but I like to think about the optimal structure and things anyway. So it's mostly for fun ;) )
I was thinking about the naming and structure of repositories, also looking at dependencies etc. I tend to have rather multiple, small repositories and a nice name. What came to my mind is:
name: Phynix Output -> pkg-name: phyout -> import as yo
(remark on the "import as": yes, it's unconventional. But its a "Phynix" (the "y") and the o for output. Additionally, p is more common as a prefix then y. Yes, I' don't find it very nice somehow, but somehow I also like it. Your thoughts?)
name: Phynix Data -> pkg-name: phydata -> import as yd
name: Phynix Minimizer -> pkg-name: phymin -> import as ym
etcetc.
(Disclaimer: I know we're neither Google, Numpy nor anything similar, but I like to think about the optimal structure and things anyway. So it's mostly for fun ;) )
I was thinking about the naming and structure of repositories, also looking at dependencies etc. I tend to have rather multiple, small repositories and a nice name. What came to my mind is:
name: Phynix Output -> pkg-name: phyout -> import as yo
(remark on the "import as": yes, it's unconventional. But its a "Phynix" (the "y") and the o for output. Additionally, p is more common as a prefix then y. Yes, I' don't find it very nice somehow, but somehow I also like it. Your thoughts?)
name: Phynix Data -> pkg-name: phydata -> import as yd
name: Phynix Minimizer -> pkg-name: phymin -> import as ym
etcetc.
What do you think, @SebastianJL ?
The text was updated successfully, but these errors were encountered: