I've been using this term with a loose understanding as heard in the phrases "uses base python", "built on base python" that basically suggests a python project that only depends externally on Python Standard Library modules alone.
I've recently been exposed to the lingo of
system python, and seeing comments like
# SYSTEM IMPORTS heading off a series of base python imports in some of the code I've been following.
From what I've gathered system python is really just a python installation that comes with a system, as in the canonical
/usr/bin/python executable. It can be expanded to include third party packages like any python installation, so it seams these comments are suggesting default system python installation modules, which to me is really getting at Base Python because I could have a default installation of Anaconda, Jython, IronPython, etc and they'd all share the same base installation setup of the standard library. To me it is the connection to the standard library that what really counts, not where the installation is to be found.
Is it imprecise to refer to standard library modules as system imports? Seems to conflate the two. I was surprised too that there's so much colloquial use of "base python" online in SO Q/A but there's not much of a formal definition online. What I find instead online is hits for base classes and integer base representation, so given that...
- What is Base Python?
- What is System Python?
- What's the difference?