能否通过pip、setuptools、setup.py及PyPI安装图标与启动器？

Absolutely! You can definitely package and install .desktop launchers and SVG icons alongside your Python package using setup.py (or the modern pyproject.toml with setuptools) — and distribute it via PyPI without any issues. Let me walk you through how to do this properly:

Project Structure #

First, organize your project to keep resources separate from your code:

your_python_app/
├── your_python_app/
│   ├── __init__.py
│   └── core.py  # Your main script
├── resources/
│   ├── my-awesome-app.desktop
│   └── my-awesome-app.svg
└── setup.py  # Or pyproject.toml for modern setups

Configuring with setup.py #

Use the data_files parameter in setup.py to specify exactly where your desktop file and icon should be installed. This parameter takes a list of tuples, where each tuple is (target_directory, [source_files]).

Here’s a full example:

from setuptools import setup
from setuptools.command.install import install
import os
import subprocess

# Optional: Add post-install commands to update system caches
class PostInstall(install):
    def run(self):
        install.run(self)
        # Update desktop database
        desktop_dir = os.path.join(self.install_data, "share", "applications")
        try:
            subprocess.run(["update-desktop-database", desktop_dir], check=True)
        except Exception as e:
            print(f"⚠️  Warning: Could not update desktop database: {str(e)}")
        
        # Update icon cache (for GTK-based desktops)
        icon_dir = os.path.join(self.install_data, "share", "icons", "hicolor")
        try:
            subprocess.run(["gtk-update-icon-cache", icon_dir], check=True)
        except Exception as e:
            print(f"⚠️  Warning: Could not update icon cache: {str(e)}")

setup(
    name="my-awesome-app",
    version="1.0.0",
    packages=["your_python_app"],
    # Map resources to system-standard paths
    data_files=[
        # Install .desktop file to the applications directory
        ("share/applications", ["resources/my-awesome-app.desktop"]),
        # Install SVG icon to the scalable apps folder (follows Freedesktop specs)
        ("share/icons/hicolor/scalable/apps", ["resources/my-awesome-app.svg"])
    ],
    # Make your script executable via a terminal command
    entry_points={
        "console_scripts": [
            "my-awesome-app=your_python_app.core:main"
        ]
    },
    # Attach the post-install hook
    cmdclass={"install": PostInstall}
)

The .desktop File #

Your .desktop file needs to reference the executable command from your entry_points and the icon name (without the .svg extension). Here’s a valid example:

[Desktop Entry]
Type=Application
Name=My Awesome App
Comment=A Python app that does cool things
Exec=my-awesome-app  # Matches the console script name from setup.py
Icon=my-awesome-app  # Matches the SVG filename (no extension needed)
Terminal=false  # Set to true if your app needs a terminal
Categories=Utility;Development;  # Helps desktop environments categorize your app

Modern Approach with pyproject.toml #

If you prefer using the newer pyproject.toml standard (recommended for modern Python packages), you can configure everything there instead of setup.py:

[build-system]
requires = ["setuptools>=61.0"]
build-backend = "setuptools.build_meta"

[project]
name = "my-awesome-app"
version = "1.0.0"
packages = ["your_python_app"]
entry-points = {
    "console_scripts": ["my-awesome-app=your_python_app.core:main"]
}

[tool.setuptools.data-files]
"share/applications" = ["resources/my-awesome-app.desktop"]
"share/icons/hicolor/scalable/apps" = ["resources/my-awesome-app.svg"]

For post-install steps in pyproject.toml, you’d still need a small setup.py or use a custom build hook, but the core resource configuration is cleaner here.

Distributing via PyPI #

Once your package is configured correctly, you can upload it to PyPI just like any other Python package. When users install it with:

pip install my-awesome-app

• If installed system-wide (with sudo), the .desktop and icon will go to /usr/share/applications and /usr/share/icons/...
• If installed user-specifically (without sudo), they’ll go to ~/.local/share/applications and ~/.local/share/icons/... — which works perfectly for per-user setups.

Key Notes #

• Permissions: System-wide installs require sudo because /usr/share/ is a protected directory. User-specific installs are safer and don’t need elevated privileges.
• Icon Cache: The post-install steps to update caches ensure your icon shows up immediately in the desktop environment. Without them, users might need to log out and back in.
• Freedesktop Compliance: Installing to share/applications and share/icons/hicolor follows the Freedesktop.org specifications, so your app will work across most Linux desktops (GNOME, KDE, Xfce, etc.).

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