PyProd 0.1.0__tar.gz → 0.2.0.post1__tar.gz

pyprod-0.2.0.post1/.github/workflows/publish.yml

@@ -0,0 +1,40 @@
+name: Publish
+on:
+  workflow_dispatch:
+  workflow_call:
+  push:
+    tags:
+      - "[0-9]+.[0-9]+.[0-9]+"
+      - "[0-9]+.[0-9]+.[0-9]+.post[0-9]+"
+
+concurrency:
+  group: pyprod-deploy
+  cancel-in-progress: true
+
+jobs:
+  publish:
+    name: Upload release to PyPI
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/pyprod
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - run: uv build
+
+      - name: Store the distribution packages
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+#        with:
+#          repository-url: https://test.pypi.org/legacy/

pyprod-0.2.0.post1/.github/workflows/test.yml

@@ -0,0 +1,38 @@
+name: Test
+
+on:
+  workflow_call:
+  workflow_dispatch:
+  push:
+    branches: ["main"]
+  pull_request:
+    branches: ["main"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+          - "3.10"
+          - "3.11"
+          - "3.12"
+          - "3.13"
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Install uv and set the python version
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install the project
+        run: uv sync --all-extras --dev
+
+      - name: Run tests
+        run: uv run pytest tests

{pyprod-0.1.0 → pyprod-0.2.0.post1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PyProd
-Version: 0.1.0
+Version: 0.2.0.post1
 Summary: PyProd: More Makeable than Make
 Project-URL: Homepage, https://github.com/atsuoishimoto/pyprod
 Project-URL: Documentation, https://pyprod.readthedocs.io/en/latest/
@@ -17,12 +17,11 @@ Description-Content-Type: text/x-rst
 PyProd - More Makeable than Make
 =================================
 
-PyProd is a Python script that can be used as an alternative to Makefile. By leveraging Python's versatility, it enables you to define build rules and dependencies programmatically, allowing for dynamic configurations, integration with existing Python libraries, and custom build logic not easily achievable with traditional Makefiles. For detailed documentation, please refer to the `official documentation <https://example.com/pyprod-docs>`_.
+PyProd is a Python script that can be used as an alternative to Makefile. By leveraging Python's versatility, it enables you to define build rules and dependencies programmatically, allowing for dynamic configurations, integration with existing Python libraries, and custom build logic not easily achievable with traditional Makefiles. For detailed documentation, please refer to the `official documentation <https://pyprod.readthedocs.io/en/latest/>`_.
 
 
 Features
 --------
-
 - Define build rules in Python: Use Python functions to create clear and concise build logic.
 - Specify dependencies for each rule: Automatically track and resolve dependencies between files, such as source files and headers.
 - Easily extendable with custom Python functions: Integrate custom logic for specialized tasks, like code linting or deployment.
@@ -30,7 +29,6 @@ Features
 
 Installation
 --------------
-
 To install PyProd, simply use pip:
 
 .. code-block:: sh
@@ -39,9 +37,7 @@ To install PyProd, simply use pip:
 
 Usage
 -----
-
-In PyProd, a traditional Makefile for C can be expressed as a Python script like this:
-
+With PyProd, a traditional Makefile for C can be expressed as a Python script like this:
 
 .. code-block:: python
 
@@ -63,6 +59,7 @@ In PyProd, a traditional Makefile for C can be expressed as a Python script like
 
     all = "hello.exe"
 
+
 To run the build script, simply execute:
 
 .. code-block:: sh
@@ -72,5 +69,4 @@ To run the build script, simply execute:
 
 License
 -------
-
 PyProd is licensed under the MIT License. See the `LICENSE <LICENSE>`_ file for more details.

{pyprod-0.1.0 → pyprod-0.2.0.post1}/README.rst

@@ -1,12 +1,11 @@
 PyProd - More Makeable than Make
 =================================
 
-PyProd is a Python script that can be used as an alternative to Makefile. By leveraging Python's versatility, it enables you to define build rules and dependencies programmatically, allowing for dynamic configurations, integration with existing Python libraries, and custom build logic not easily achievable with traditional Makefiles. For detailed documentation, please refer to the `official documentation <https://example.com/pyprod-docs>`_.
+PyProd is a Python script that can be used as an alternative to Makefile. By leveraging Python's versatility, it enables you to define build rules and dependencies programmatically, allowing for dynamic configurations, integration with existing Python libraries, and custom build logic not easily achievable with traditional Makefiles. For detailed documentation, please refer to the `official documentation <https://pyprod.readthedocs.io/en/latest/>`_.
 
 
 Features
 --------
-
 - Define build rules in Python: Use Python functions to create clear and concise build logic.
 - Specify dependencies for each rule: Automatically track and resolve dependencies between files, such as source files and headers.
 - Easily extendable with custom Python functions: Integrate custom logic for specialized tasks, like code linting or deployment.
@@ -14,7 +13,6 @@ Features
 
 Installation
 --------------
-
 To install PyProd, simply use pip:
 
 .. code-block:: sh
@@ -23,9 +21,7 @@ To install PyProd, simply use pip:
 
 Usage
 -----
-
-In PyProd, a traditional Makefile for C can be expressed as a Python script like this:
-
+With PyProd, a traditional Makefile for C can be expressed as a Python script like this:
 
 .. code-block:: python
 
@@ -47,6 +43,7 @@ In PyProd, a traditional Makefile for C can be expressed as a Python script like
 
     all = "hello.exe"
 
+
 To run the build script, simply execute:
 
 .. code-block:: sh
@@ -56,5 +53,4 @@ To run the build script, simply execute:
 
 License
 -------
-
 PyProd is licensed under the MIT License. See the `LICENSE <LICENSE>`_ file for more details.

{pyprod-0.1.0 → pyprod-0.2.0.post1}/docs/conf.py

@@ -26,10 +26,10 @@ html_theme = "sphinx_rtd_theme"
 html_static_path = ["_static"]
 
 html_logo = "pyprod2.png"
-html_favicon = 'pyprod2.png'
+html_favicon = "pyprod2.png"
 html_context = {
-  'display_github': True,
-  'github_user': 'atsuoishimoto',
-  'github_repo': 'pyprod',
-  'github_version': 'main/docs/',
-}
+    "display_github": True,
+    "github_user": "atsuoishimoto",
+    "github_repo": "pyprod",
+    "github_version": "main/docs/",
+}

{pyprod-0.1.0 → pyprod-0.2.0.post1}/docs/prodfile.rst

@@ -15,17 +15,17 @@ A rule is defined using the ``@rule`` decorator, which takes the target file as
    Defines rule to build target files.
 
    :param target: The target file or files to be generated by the rule. Wildcards can be used in filenames, and exactly one % must be included in the filename.
-   :type target: str|Path|list[str|Path]
+   :type target: str | Path|list[str | Path]
 
    :param pattern: Specify the pattern used to extract the stem of the target filename.
 
-   :type pattern: str|Path|None
+   :type pattern: str | Path | None
 
    :param depends: Specify the dependencies of the target file. The target file will be rebuilt if any of the dependencies are newer than the target file.
-   :type depends: str|Path|list[str|Path]
+   :type depends: str | Path | list[str | Path]
 
    :param uses: Specify the dependencies of the target file. Unlike the ``depends`` parameter, the target file will not be rebuilt if any of the dependencies are newer than the target file.
-   :type uses: str|Path|list[str|Path]
+   :type uses: str | Path | list[str | Path]
 
 Build function
 ~~~~~~~~~~~~~~~~~~~
@@ -88,20 +88,19 @@ The rule decorator can also be used as a standalone function without being tied
 Checker definition
 ^^^^^^^^^^^^^^^^^^
 
-A checker is defined using the ``@check`` decorator, which takes the target file as an argument. The checker tests if the target is exists or not.
+PyProd provides default checkers for common file types for files and directories. For non-file targets requiring specialized checks, you can define a custom checker to determine whether a build is needed.
+A checker is defined using the ``@check`` decorator, which takes the target file as an argument.
 
 .. py:function:: @check(target)
 
    Defines a checker to get last modified time of the target.
 
    :param target: The target file to be checked. Wildcards can be used.
-   :type target: str|Path
+   :type target: str | Path
 
    :return: Last modified time of the file if the target exists. Returns false or raise FileNotFoundError if the target does not exist.
    :rtype: false|float|datetime.datetime
 
-PyProd provides default checkers for common file types for files and directories. 
-PyProd includes default checkers for common file types, applicable to both files and directories. For non-file targets requiring specialized checks, you can define a custom checker to determine whether a build is needed.
 
 For example, a checker to retrieve the last modified timestamp of a file on Amazon S3 can be defined as follows:
 
@@ -160,22 +159,22 @@ Example:
 
 .. py:function:: run(*args, echo=True, shell=None, stdout=None,cwd=None, text=True,    check=True)
 
-   Execute a command. This function is a wrapper around `subprocess.run()` and provides additional functionality for the build system.
+   Execute a command. This function is a wrapper around `subprocess.run() <https://docs.python.org/3/library/subprocess.html#subprocess.run>`_ and provides additional functionality for the build system.
 
    :param args: Command and arguments to execute. If first argument is a list, the first element is the command and the rest are arguments. Sequences specified for args are automatically flattened.
-   :type args: str|Path|list[str|Path]
+   :type args: str | Path| list[str | Path]
 
-   :echo: Print the command before executing it (default ``True``).
+   :param echo: Print the command before executing it (default ``True``).
    :type echo: bool
 
-   :shell: Run the command in a shell. If None, the shell is used unless `arg` is sequence (default ``None``).
+   :param shell: Run the command in a shell. If None, the shell is used unless `arg` is sequence (default ``None``).
    :type shell: bool|None
 
-   :stdout: Capture the output of the command (default ``False``).
+   :param stdout: Capture the output of the command (default ``False``).
    :type shell: bool
 
-   :cwd: Change the current working directory before executing the command.
-   :type shell: str|Path|None
+   :param cwd: Change the current working directory before executing the command.
+   :type shell: str | Path | None
 
    :param text: Use text mode for stdout and stderr (default ``True``).
    :type shell: bool
@@ -204,13 +203,13 @@ Example:
    :ref:`run <run>`.
 
    :param args: Command and arguments to execute. If first argument is a list, the first element is the command and the rest are arguments. Sequences specified for args are automatically flattened.
-   :type args: str|Path|list[str|Path]
+   :type args: str | Path | list[str | Path]
 
    :echo: Print the command before executing it (default ``True``).
    :type echo: bool
 
    :cwd: Change the current working directory before executing the command.
-   :type shell: str|Path|None
+   :type shell: str | Path | None
 
    :param check: Raise an exception if the command returns a non-zero exit code (default ``True``).
    :type shell: bool
@@ -235,10 +234,10 @@ Example:
    Glob the given relative pattern in the directory represented by this path. This function is a wrapper around `pathlib.Path.glob() <https://docs.python.org/3/library/pathlib.html#pathlib.Path.glob>`_. Unlike ``pathlib.Path.glob()``, this function ignores files and directlies that start with a dot. Also, this function returns a list of Path objects.
 
    :param path: The file pattern to match.
-   :type path: str|Path
+   :type path: str | Path
 
    :param dir: The directory to search in (default ``.``).
-   :type dir: str|Path
+   :type dir: str | Path
 
    :return: A list of Path object.
    :rtype: list[Path]

{pyprod-0.1.0 → pyprod-0.2.0.post1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "PyProd"
-version = "0.1.0"
+version = "0.2.0.post1"
 description = "PyProd: More Makeable than Make"
 readme = "README.rst"
 requires-python = ">=3.10"

pyprod-0.1.0/sample/build-c/Prodfile.py → pyprod-0.2.0.post1/sample/build-c/PRODFILE.py

@@ -12,13 +12,12 @@ OBJS = "hello.o main.o".split()
 def link(target, *src):
     run(CC, "-o", target, src)
 
+
 @rule("%.o", depends=("%.c", DEPS))
 def compile(target, src, *deps):
     run(CC, "-c -o", target, src, CFLAGS)
 
 
-
-
 def clean():
     run("rm", "-rf", OBJS, APP)
 

{pyprod-0.1.0/sample/build-c → pyprod-0.2.0.post1/sample/generate-doc}/.gitignore

@@ -1,2 +1,2 @@
 objs/*
-app.txt
+DOC.txt

{pyprod-0.1.0 → pyprod-0.2.0.post1}/src/pyprod/prod.py

@@ -3,6 +3,7 @@ import concurrent.futures
 import datetime
 import importlib
 import importlib.machinery
+import importlib.util
 import logging
 import os
 import re

pyprod-0.1.0/.github/workflows/test.yml

@@ -1,22 +0,0 @@
-name: Python application
-
-on:
-  push:
-    branches: ["main"]
-  pull_request:
-    branches: ["main"]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v5
-
-      - name: Run tests
-        run: |
-          uv run pytest tests

pyprod-0.1.0/.vscode/settings.json

@@ -1,5 +0,0 @@
-{
-  "[yaml]": {
-    "editor.tabSize": 2
-  }
-}

pyprod-0.1.0/.xxx/.Prodfile.py.pyprod/.gitignore

@@ -1,2 +0,0 @@
-# Created by venv; see https://docs.python.org/3/library/venv.html
-*

pyprod-0.1.0/.xxx/.Prodfile.py.pyprod/bin/Activate.ps1

@@ -1,248 +0,0 @@
-<#
-.Synopsis
-Activate a Python virtual environment for the current PowerShell session.
-
-.Description
-Pushes the python executable for a virtual environment to the front of the
-$Env:PATH environment variable and sets the prompt to signify that you are
-in a Python virtual environment. Makes use of the command line switches as
-well as the `pyvenv.cfg` file values present in the virtual environment.
-
-.Parameter VenvDir
-Path to the directory that contains the virtual environment to activate. The
-default value for this is the parent of the directory that the Activate.ps1
-script is located within.
-
-.Parameter Prompt
-The prompt prefix to display when this virtual environment is activated. By
-default, this prompt is the name of the virtual environment folder (VenvDir)
-surrounded by parentheses and followed by a single space (ie. '(.venv) ').
-
-.Example
-Activate.ps1
-Activates the Python virtual environment that contains the Activate.ps1 script.
-
-.Example
-Activate.ps1 -Verbose
-Activates the Python virtual environment that contains the Activate.ps1 script,
-and shows extra information about the activation as it executes.
-
-.Example
-Activate.ps1 -VenvDir C:\Users\MyUser\Common\.venv
-Activates the Python virtual environment located in the specified location.
-
-.Example
-Activate.ps1 -Prompt "MyPython"
-Activates the Python virtual environment that contains the Activate.ps1 script,
-and prefixes the current prompt with the specified string (surrounded in
-parentheses) while the virtual environment is active.
-
-.Notes
-On Windows, it may be required to enable this Activate.ps1 script by setting the
-execution policy for the user. You can do this by issuing the following PowerShell
-command:
-
-PS C:\> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
-
-For more information on Execution Policies: 
-https://go.microsoft.com/fwlink/?LinkID=135170
-
-#>
-Param(
-    [Parameter(Mandatory = $false)]
-    [String]
-    $VenvDir,
-    [Parameter(Mandatory = $false)]
-    [String]
-    $Prompt
-)
-
-<# Function declarations --------------------------------------------------- #>
-
-<#
-.Synopsis
-Remove all shell session elements added by the Activate script, including the
-addition of the virtual environment's Python executable from the beginning of
-the PATH variable.
-
-.Parameter NonDestructive
-If present, do not remove this function from the global namespace for the
-session.
-
-#>
-function global:deactivate ([switch]$NonDestructive) {
-    # Revert to original values
-
-    # The prior prompt:
-    if (Test-Path -Path Function:_OLD_VIRTUAL_PROMPT) {
-        Copy-Item -Path Function:_OLD_VIRTUAL_PROMPT -Destination Function:prompt
-        Remove-Item -Path Function:_OLD_VIRTUAL_PROMPT
-    }
-
-    # The prior PYTHONHOME:
-    if (Test-Path -Path Env:_OLD_VIRTUAL_PYTHONHOME) {
-        Copy-Item -Path Env:_OLD_VIRTUAL_PYTHONHOME -Destination Env:PYTHONHOME
-        Remove-Item -Path Env:_OLD_VIRTUAL_PYTHONHOME
-    }
-
-    # The prior PATH:
-    if (Test-Path -Path Env:_OLD_VIRTUAL_PATH) {
-        Copy-Item -Path Env:_OLD_VIRTUAL_PATH -Destination Env:PATH
-        Remove-Item -Path Env:_OLD_VIRTUAL_PATH
-    }
-
-    # Just remove the VIRTUAL_ENV altogether:
-    if (Test-Path -Path Env:VIRTUAL_ENV) {
-        Remove-Item -Path env:VIRTUAL_ENV
-    }
-
-    # Just remove VIRTUAL_ENV_PROMPT altogether.
-    if (Test-Path -Path Env:VIRTUAL_ENV_PROMPT) {
-        Remove-Item -Path env:VIRTUAL_ENV_PROMPT
-    }
-
-    # Just remove the _PYTHON_VENV_PROMPT_PREFIX altogether:
-    if (Get-Variable -Name "_PYTHON_VENV_PROMPT_PREFIX" -ErrorAction SilentlyContinue) {
-        Remove-Variable -Name _PYTHON_VENV_PROMPT_PREFIX -Scope Global -Force
-    }
-
-    # Leave deactivate function in the global namespace if requested:
-    if (-not $NonDestructive) {
-        Remove-Item -Path function:deactivate
-    }
-}
-
-<#
-.Description
-Get-PyVenvConfig parses the values from the pyvenv.cfg file located in the
-given folder, and returns them in a map.
-
-For each line in the pyvenv.cfg file, if that line can be parsed into exactly
-two strings separated by `=` (with any amount of whitespace surrounding the =)
-then it is considered a `key = value` line. The left hand string is the key,
-the right hand is the value.
-
-If the value starts with a `'` or a `"` then the first and last character is
-stripped from the value before being captured.
-
-.Parameter ConfigDir
-Path to the directory that contains the `pyvenv.cfg` file.
-#>
-function Get-PyVenvConfig(
-    [String]
-    $ConfigDir
-) {
-    Write-Verbose "Given ConfigDir=$ConfigDir, obtain values in pyvenv.cfg"
-
-    # Ensure the file exists, and issue a warning if it doesn't (but still allow the function to continue).
-    $pyvenvConfigPath = Join-Path -Resolve -Path $ConfigDir -ChildPath 'pyvenv.cfg' -ErrorAction Continue
-
-    # An empty map will be returned if no config file is found.
-    $pyvenvConfig = @{ }
-
-    if ($pyvenvConfigPath) {
-
-        Write-Verbose "File exists, parse `key = value` lines"
-        $pyvenvConfigContent = Get-Content -Path $pyvenvConfigPath
-
-        $pyvenvConfigContent | ForEach-Object {
-            $keyval = $PSItem -split "\s*=\s*", 2
-            if ($keyval[0] -and $keyval[1]) {
-                $val = $keyval[1]
-
-                # Remove extraneous quotations around a string value.
-                if ("'""".Contains($val.Substring(0, 1))) {
-                    $val = $val.Substring(1, $val.Length - 2)
-                }
-
-                $pyvenvConfig[$keyval[0]] = $val
-                Write-Verbose "Adding Key: '$($keyval[0])'='$val'"
-            }
-        }
-    }
-    return $pyvenvConfig
-}
-
-
-<# Begin Activate script --------------------------------------------------- #>
-
-# Determine the containing directory of this script
-$VenvExecPath = Split-Path -Parent $MyInvocation.MyCommand.Definition
-$VenvExecDir = Get-Item -Path $VenvExecPath
-
-Write-Verbose "Activation script is located in path: '$VenvExecPath'"
-Write-Verbose "VenvExecDir Fullname: '$($VenvExecDir.FullName)"
-Write-Verbose "VenvExecDir Name: '$($VenvExecDir.Name)"
-
-# Set values required in priority: CmdLine, ConfigFile, Default
-# First, get the location of the virtual environment, it might not be
-# VenvExecDir if specified on the command line.
-if ($VenvDir) {
-    Write-Verbose "VenvDir given as parameter, using '$VenvDir' to determine values"
-}
-else {
-    Write-Verbose "VenvDir not given as a parameter, using parent directory name as VenvDir."
-    $VenvDir = $VenvExecDir.Parent.FullName.TrimEnd("\\/")
-    Write-Verbose "VenvDir=$VenvDir"
-}
-
-# Next, read the `pyvenv.cfg` file to determine any required value such
-# as `prompt`.
-$pyvenvCfg = Get-PyVenvConfig -ConfigDir $VenvDir
-
-# Next, set the prompt from the command line, or the config file, or
-# just use the name of the virtual environment folder.
-if ($Prompt) {
-    Write-Verbose "Prompt specified as argument, using '$Prompt'"
-}
-else {
-    Write-Verbose "Prompt not specified as argument to script, checking pyvenv.cfg value"
-    if ($pyvenvCfg -and $pyvenvCfg['prompt']) {
-        Write-Verbose "  Setting based on value in pyvenv.cfg='$($pyvenvCfg['prompt'])'"
-        $Prompt = $pyvenvCfg['prompt'];
-    }
-    else {
-        Write-Verbose "  Setting prompt based on parent's directory's name. (Is the directory name passed to venv module when creating the virtual environment)"
-        Write-Verbose "  Got leaf-name of $VenvDir='$(Split-Path -Path $venvDir -Leaf)'"
-        $Prompt = Split-Path -Path $venvDir -Leaf
-    }
-}
-
-Write-Verbose "Prompt = '$Prompt'"
-Write-Verbose "VenvDir='$VenvDir'"
-
-# Deactivate any currently active virtual environment, but leave the
-# deactivate function in place.
-deactivate -nondestructive
-
-# Now set the environment variable VIRTUAL_ENV, used by many tools to determine
-# that there is an activated venv.
-$env:VIRTUAL_ENV = $VenvDir
-
-$env:VIRTUAL_ENV_PROMPT = $Prompt
-
-if (-not $Env:VIRTUAL_ENV_DISABLE_PROMPT) {
-
-    Write-Verbose "Setting prompt to '$Prompt'"
-
-    # Set the prompt to include the env name
-    # Make sure _OLD_VIRTUAL_PROMPT is global
-    function global:_OLD_VIRTUAL_PROMPT { "" }
-    Copy-Item -Path function:prompt -Destination function:_OLD_VIRTUAL_PROMPT
-    New-Variable -Name _PYTHON_VENV_PROMPT_PREFIX -Description "Python virtual environment prompt prefix" -Scope Global -Option ReadOnly -Visibility Public -Value $Prompt
-
-    function global:prompt {
-        Write-Host -NoNewline -ForegroundColor Green "($_PYTHON_VENV_PROMPT_PREFIX) "
-        _OLD_VIRTUAL_PROMPT
-    }
-}
-
-# Clear PYTHONHOME
-if (Test-Path -Path Env:PYTHONHOME) {
-    Copy-Item -Path Env:PYTHONHOME -Destination Env:_OLD_VIRTUAL_PYTHONHOME
-    Remove-Item -Path Env:PYTHONHOME
-}
-
-# Add the venv to the PATH
-Copy-Item -Path Env:PATH -Destination Env:_OLD_VIRTUAL_PATH
-$Env:PATH = "$VenvExecDir$([System.IO.Path]::PathSeparator)$Env:PATH"