能否让用户无需pip安装模块，改用本地文件夹导入依赖？

Absolutely, you can skip pip installs entirely and import modules directly from local folders—this is a common use case for distributing self-contained scripts or avoiding dependency conflicts. Let’s walk through exactly how to do both of your requested scenarios:

Scenario 1: Import Modules from a Separate Local Folder #

If you have all your required modules stored in an independent folder (say, local_modules), you just need to tell Python where to look for them by adding that folder’s path to sys.path—the list of directories Python checks when importing modules.

Here’s a step-by-step implementation:

1. Organize your files:

   your_project/
   ├── your_script.py
   └── local_modules/
       ├── requests/          # Example module you want to import
       └── another_module/
   

2. Add the local folder path to sys.path in your script:

   import sys
   import os
   
   # Get the absolute path of your script's directory
   script_directory = os.path.dirname(os.path.abspath(__file__))
   # Build the path to your local modules folder
   local_modules_path = os.path.join(script_directory, "local_modules")
   # Insert the path at the start of sys.path (to prioritize local modules over system ones)
   sys.path.insert(0, local_modules_path)
   
   # Now you can import modules like normal!
   import requests
   from another_module import some_function
   

Scenario 2: Self-Contained Script with a Co-Located Module Folder #

For a script that lives alongside a folder containing a module’s full resources, the approach is similar—you just need to ensure Python can find the adjacent module folder.

1. Set up your directory structure:

   my_self_contained_app/
   ├── main.py               # Your main script
   └── my_custom_module/
       ├── __init__.py       # *Optional but recommended* (marks the folder as a Python package)
       ├── core.py           # Module files
       └── resources/
           └── config.json   # Any assets the module uses
   

2. Import the module in your script:
   Since the module folder is in the same directory as your script, Python will automatically check the current directory for modules by default. But to avoid issues with relative paths or different execution contexts, it’s safer to explicitly add the script’s directory to sys.path:

   import sys
   import os
   
   # Ensure the script's directory is in Python's search path
   sys.path.insert(0, os.path.dirname(os.path.abspath(__file__)))
   
   # Import your local module
   import my_custom_module
   from my_custom_module.core import run_app
   
   # Use the module as needed
   run_app()
   

Key Notes for Success #

• Include __init__.py: While Python 3.3+ supports namespace packages without this file, adding an empty __init__.py makes your folder explicitly recognizable as a Python package and avoids unexpected behavior.
• Handle dependencies: If your local module relies on other packages, you’ll need to include those dependencies in your local folder structure too (repeat the same sys.path trick for them).
• Cross-platform compatibility: Always use os.path.join() to build paths instead of hardcoding slashes—this works on Windows, macOS, and Linux.
• Alternative: site.addsitedir(): For more flexibility (like automatically processing .pth files), you can use site.addsitedir() instead of modifying sys.path directly:

  import site
  import os
  
  site.addsitedir(os.path.join(os.path.dirname(os.path.abspath(__file__)), "local_modules"))
  

内容的提问来源于stack exchange，提问作者grumblermannice