unpythonic 0.15.5__tar.gz → 1.0.0__tar.gz

{unpythonic-0.15.5 → unpythonic-1.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: unpythonic
-Version: 0.15.5
+Version: 1.0.0
 Summary: Supercharge your Python with parts of Lisp and Haskell.
 Keywords: functional-programming,language-extension,syntactic-macros,tail-call-optimization,tco,continuations,currying,lazy-evaluation,dynamic-variable,macros,lisp,scheme,racket,haskell
 Author-Email: Juha Jeronen <juha.m.jeronen@gmail.com>
@@ -35,6 +35,8 @@ In the spirit of [toolz](https://github.com/pytoolz/toolz), we provide missing f
 ![version on PyPI](https://img.shields.io/pypi/v/unpythonic) ![PyPI package format](https://img.shields.io/pypi/format/unpythonic) ![dependency status](https://img.shields.io/librariesio/github/Technologicat/unpythonic)  
 ![license: BSD](https://img.shields.io/pypi/l/unpythonic) ![open issues](https://img.shields.io/github/issues/Technologicat/unpythonic) [![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen)](http://makeapullrequest.com/)
 
+We use [semantic versioning](https://semver.org/).
+
 *Some hypertext features of this README, such as local links to detailed documentation, and expandable example highlights, are not supported when viewed on PyPI; [view on GitHub](https://github.com/Technologicat/unpythonic) to have those work properly.*
 
 
@@ -857,6 +859,60 @@ If `--no-compile` is NOT used, the precompiled bytecode cache may cause errors s
 
 This is a common issue when using macro expanders in Python.
 
+### Development mode (for developing `unpythonic` itself)
+
+Starting with v0.15.5, `unpythonic` uses [PDM](https://pdm-project.org/en/latest/) to manage its dependencies. This allows easy installation of a development copy into an isolated venv (virtual environment), allowing you to break things without breaking anything else on your system (including apps and libraries that use an installed copy of `unpythonic`).
+
+#### Install PDM in your Python environment
+
+To develop `unpythonic`, if your Python environment does not have PDM, you will need to install it first:
+
+```bash
+python -m pip install pdm
+```
+
+Don't worry; it won't break `pip`, `poetry`, or other similar tools.
+
+We will also need a Python for PDM venvs. This Python is independent of the Python that PDM itself runs on. It is the version of Python you would like to use for developing `unpythonic`.
+
+For example, we can make Python 3.10 available with the command:
+
+```bash
+pdm python install 3.10
+```
+
+Specifying just a version number defaults to CPython (the usual Python implementation). If you want PyPy instead, you can use e.g. `pypy@3.10`.
+
+#### Install the isolated venv
+
+Now, we will auto-create the development venv, and install `unpythonic`'s dependencies into it. In a terminal that sees your Python environment, navigate to the `unpythonic` folder, and issue the command:
+
+```bash
+pdm install
+```
+
+This creates the development venv into the `.venv` hidden subfolder of the `unpythonic` folder.
+
+If you are a seasoned pythonista, note that there is no `requirements.txt`; the dependency list lives in `pyproject.toml`.
+
+#### Upgrade dependencies (later)
+
+To upgrade dependencies to latest available versions compatible with the specifications in `pyproject.toml`:
+
+```bash
+pdm update
+```
+
+#### Develop
+
+To activate the development venv, in a terminal that sees your Python environment, navigate to the `unpythonic` folder, and issue the command:
+
+```bash
+$(pdm venv activate)
+```
+
+Note the Bash exec syntax `$(...)`; the command `pdm venv activate` just prints the actual internal activation command.
+
 ### Uninstall
 
 ```bash

{unpythonic-0.15.5 → unpythonic-1.0.0}/README.md

@@ -6,6 +6,8 @@ In the spirit of [toolz](https://github.com/pytoolz/toolz), we provide missing f
 ![version on PyPI](https://img.shields.io/pypi/v/unpythonic) ![PyPI package format](https://img.shields.io/pypi/format/unpythonic) ![dependency status](https://img.shields.io/librariesio/github/Technologicat/unpythonic)  
 ![license: BSD](https://img.shields.io/pypi/l/unpythonic) ![open issues](https://img.shields.io/github/issues/Technologicat/unpythonic) [![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen)](http://makeapullrequest.com/)
 
+We use [semantic versioning](https://semver.org/).
+
 *Some hypertext features of this README, such as local links to detailed documentation, and expandable example highlights, are not supported when viewed on PyPI; [view on GitHub](https://github.com/Technologicat/unpythonic) to have those work properly.*
 
 
@@ -828,6 +830,60 @@ If `--no-compile` is NOT used, the precompiled bytecode cache may cause errors s
 
 This is a common issue when using macro expanders in Python.
 
+### Development mode (for developing `unpythonic` itself)
+
+Starting with v0.15.5, `unpythonic` uses [PDM](https://pdm-project.org/en/latest/) to manage its dependencies. This allows easy installation of a development copy into an isolated venv (virtual environment), allowing you to break things without breaking anything else on your system (including apps and libraries that use an installed copy of `unpythonic`).
+
+#### Install PDM in your Python environment
+
+To develop `unpythonic`, if your Python environment does not have PDM, you will need to install it first:
+
+```bash
+python -m pip install pdm
+```
+
+Don't worry; it won't break `pip`, `poetry`, or other similar tools.
+
+We will also need a Python for PDM venvs. This Python is independent of the Python that PDM itself runs on. It is the version of Python you would like to use for developing `unpythonic`.
+
+For example, we can make Python 3.10 available with the command:
+
+```bash
+pdm python install 3.10
+```
+
+Specifying just a version number defaults to CPython (the usual Python implementation). If you want PyPy instead, you can use e.g. `pypy@3.10`.
+
+#### Install the isolated venv
+
+Now, we will auto-create the development venv, and install `unpythonic`'s dependencies into it. In a terminal that sees your Python environment, navigate to the `unpythonic` folder, and issue the command:
+
+```bash
+pdm install
+```
+
+This creates the development venv into the `.venv` hidden subfolder of the `unpythonic` folder.
+
+If you are a seasoned pythonista, note that there is no `requirements.txt`; the dependency list lives in `pyproject.toml`.
+
+#### Upgrade dependencies (later)
+
+To upgrade dependencies to latest available versions compatible with the specifications in `pyproject.toml`:
+
+```bash
+pdm update
+```
+
+#### Develop
+
+To activate the development venv, in a terminal that sees your Python environment, navigate to the `unpythonic` folder, and issue the command:
+
+```bash
+$(pdm venv activate)
+```
+
+Note the Bash exec syntax `$(...)`; the command `pdm venv activate` just prints the actual internal activation command.
+
 ### Uninstall
 
 ```bash

{unpythonic-0.15.5 → unpythonic-1.0.0}/pyproject.toml

@@ -45,7 +45,7 @@ classifiers = [
     "Topic :: Software Development :: Libraries",
     "Topic :: Software Development :: Libraries :: Python Modules",
 ]
-version = "0.15.5"
+version = "1.0.0"
 
 [project.license]
 text = "BSD"

{unpythonic-0.15.5 → unpythonic-1.0.0}/unpythonic/__init__.py

@@ -7,7 +7,7 @@ If you have ``mcpyrate`` installed, see also ``unpythonic.syntax``
 for a trip down the rabbit hole.
 """
 
-__version__ = '0.15.5'
+__version__ = '1.0.0'
 
 from .amb import *  # noqa: F401, F403
 from .arity import *  # noqa: F401, F403