| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2022-08-22 | Add missing makedepends | Claudia Pellegrino | |
| 2022-08-22 | Replace `flit` invocation with `build` | Claudia Pellegrino | |
| The `flit` command performs some up-front validation before it actually builds the package. This is intended for upstream project maintainers so they have a chance to learn about issues before they proceed to cut a release. Once a package is released, people who consume the package (which includes package repository maintainers) are assumed to be mainly interested in getting the already-released package to build. Therefore, they may simply want to run the build backend without caring about up-front validation. That’s what the `build` command does: invoke the suitable build backend, which in the case of `flit`, doesn’t run the validation steps. See discussion in [1]. [1]: https://github.com/pypa/flit/issues/580 CC: Thomas Kluyver <thomas@kluyver.me.uk> CC: William Woodruff <william@yossarian.net> | |||
| 2022-08-22 | Keep .pyc files | Claudia Pellegrino | |
| According to the wiki, the preferred way to package a Python artifact is to build a wheel. [1] This basically produces a tree of .py files with a bit of metadata, ready to use. Intermingled with those .py files, it also produces a __pycache__ directory containing .pyc files. The documentation says that those contain Python bytecode, which in turn is tightly coupled to the specific VM that was used to produce them [2]. In other words, Python bytecode is architecture-independent, but effectively tied to a specific version of the Python runtime, for example 3.10. [3] Keep the .pyc files because: 1. According to The Arch Way, things should be simple. The simplest thing to do is to not care about .pyc files, and just leave them in, just like upstream does. 2. Installing a wheel to a `pkgdir` already ties the package to a specific Python version anyway, for example due to the fact that the `site-packages` hierarchy is version-specific. So the .pyc files are safe to use, regardless of architecture. 3. For most AUR users, the target architecture is identical to the build architecture. [1]: https://wiki.archlinux.org/title/Python_package_guidelines#Standards_based_(PEP_517) [2]: https://docs.python.org/3/glossary.html#term-bytecode [3]: https://stackoverflow.com/q/7807541 | |||
| 2022-08-19 | Bump dependencies; use flit, installer; add LICENSE | Claudia Pellegrino | |
| 2022-08-19 | Update .gitignore | Claudia Pellegrino | |
| 2021-12-07 | Bump python-pip-api dependency | Claudia Pellegrino | |
| 2021-11-23 | Update dependencies | Claudia Pellegrino | |
| 2021-11-09 | Initial commit | Claudia Pellegrino | |