A console/terminal demo of the four ways Python brings code in from elsewhere: a standard-library module, a local module in the same folder, an alias, and a module inside a package folder. Runs on Windows 11 and Ubuntu Linux 24.04, uses the standard library only — no third-party packages, no GPU, fully offline.

 

[Folder Structure]

  • CLAUDE.md / AGENT.md: program specification (identical content).
  • CHANGELOG.md: change log.
  • copyright.txt: copyright notice.
  • src/: the demo, the local module and package, the launcher scripts, and this document.
  • venv/: Python virtual environment, created by step 1.

[Prerequisites]

  • Operating system: Windows 11 or Ubuntu Linux 24.04.
  • Python 3 and pip.
  • No third-party packages — the example uses the standard library only.
  • No internet connection and no GPU required.

[Instructions]

Step 1: Create the virtual environment

Create the virtual environment. Because the example uses only the standard library, this step installs no extra packages.

 

Windows 11:

src\01_venv_create.bat

Ubuntu Linux 24.04:

bash src/01_venv_create.sh

Step 2: Activate the virtual environment

Activate the environment in the current shell. On Linux you must source the script so the activation stays in effect after it finishes.

 

Windows 11:

src\02_venv_activate.bat

Ubuntu Linux 24.04:

source src/02_venv_activate.sh

Step 3: Run the import demo

Run the demo. It imports a standard-library module, a local module that sits next to the script, the same module under a shorter alias, and finally a module inside a package folder, printing what each one provides so you can see where every name comes from.

 

Windows 11:

src\03_import.bat

Ubuntu Linux 24.04:

bash src/03_import.sh

Step 4: Remove the virtual environment

When you are finished, delete the venv/ folder to free up disk space. Re-run step 1 whenever you need the environment again.

 

Windows 11:

src\99_venv_clear.bat

Ubuntu Linux 24.04:

bash src/99_venv_clear.sh

[Usage Notes]

  • import module loads the whole module; you then reach its contents through module.name.
  • from module import name brings a single name straight into your own namespace.
  • import module as alias gives the module a shorter name — handy for long package paths.
  • A folder becomes a package once Python can import modules from it, and you address them as package.module.
  • Python searches for modules along sys.path: the script's own folder comes first, then the standard library and the installed packages — so a local file named the same as a standard module will shadow it.

This SDK is built in AppForAI - AI Dev Tools.

 

Purchase license separately:  USD 600, permanent authorization, single APP authorization, single machine authorization, one-year activation, one-year download, one-year update, one-year email technical support.