The Wombelix Post - Python

Release: MoinMoin Wiki Container, powered by PyPy2

2021-10-09T00:00:00+02:00

Today I published the first version of moinmoin-pypy2-container, a ready to use image to run MoinMoin Wiki, based on openSUSE Leap.

It contains some enhancements regarding the intial wiki setup to make it easier to get started and already ships with a pre-configured nginx.

Latest stable release of MoinMoin was 8th November 2020 and requires Python 2, development of the successor moin2 is ongoing but wasn't released yet.

moin2 supports Python 3, but there is still a lot to do and the Project could use some help, what about a good first issue?

It might be that User still want to keep using the latest stable release and wait with the migration for a while.

Besides minor enhancements, the main goal of moinmoin-pypy2-container is to provide a easy to use alternative to keep using MoinMoin.

The official Python 2 Runtime is End-of-Life. But PyPy will support Python 2 "forever" and still provide updates in future.

Please check the README in the below linked Source code Repository for further details about the features and usage.

The repository is available on Codeberg (Primary), Gitlab (Mirror), Github (Mirror).

Pre-build Container Images can be downloaded from quay.io.

Installing static site generator Pelican inclusive Plugins with pipx

2021-09-25T00:00:00+02:00

Quick one, after re-installing my Notebook, I had to configure lot of things again and I wasn't happy with my earlier Python venv setup.

I was taking a deeper look into pipx and I think that's way easier to use. It just take care about a venv per package that I'm going to install, I don't have to take care about anything on my own.

I tried it and after learning about the inject feature, mentioned by cs01 in a GitHub Issue (Archive: [1], [2]) it was no problem to install Pelican including some Plugins via pipx:

pipx install pelican
pipx inject pelican pelican-pdf
pipx inject pelican markdown
pipx inject pelican pelican-read-more

pipx behave different than pip if package already exists

2021-09-23T00:00:00+02:00

I decided to put as much as possible of my local config into an Ansible Playbook. Makes it easier to track what I install and change, also to setup from scratch should it necessary.

In the past I mainly used pip in combination with venv to install Python stuff. Changing for most of it to pipx seems logical, it will take care about the necessary venvs on it's own.

Just had to learn that the return code of pip is 0 but from pipx it's 1 in case a package already exists.

Why does it matter? Not the most elegant solution but I decided to just use command to trigger pip / pipx from my Playbook:

- name: Python Package Installation (pip)
  command: "python3 -m pip install --user {{ item }}"
  changed_when: false
  loop:
    - pipx
    - nox

- name: Python Package Installation (pipx)
  command: "pipx install {{ item }}"
  changed_when: false
  loop:
    - poetry
    - duplicity
    - pre-commit

No problem with pip, but pipx failed after the first run.

There was an older GitHub Issue, based on the comments, pipx was supposed to behave smilar as pip and also use return code 0 since v0.13 already. After some research I found the Pull Request that reverted the earlier change during some re-factoring.

Thanks to the great improvements in that PR, it was just a very small change necessary to restore the functionality introduced in Commit 11b853e:

diff --git a/docs/changelog.md b/docs/changelog.md
index 0a95ce15..67d14929 100644
--- a/docs/changelog.md
+++ b/docs/changelog.md
@@ -1,6 +1,7 @@
 dev

 - Fixed `pipx list` output phrasing to convey that python version displayed is the one with which package was installed.
+- Fixed `pipx install` to provide return code 0 if venv already exists, similar to pip’s behavior. (#736)

 0.16.4

diff --git a/src/pipx/constants.py b/src/pipx/constants.py
index 4fe2d58b..11fc013f 100644
--- a/src/pipx/constants.py
+++ b/src/pipx/constants.py
@@ -21,7 +21,7 @@
 # pipx shell exit codes
 EXIT_CODE_OK = ExitCode(0)
 EXIT_CODE_INJECT_ERROR = ExitCode(1)
-EXIT_CODE_INSTALL_VENV_EXISTS = ExitCode(1)
+EXIT_CODE_INSTALL_VENV_EXISTS = ExitCode(0)
 EXIT_CODE_LIST_PROBLEM = ExitCode(1)
 EXIT_CODE_UNINSTALL_VENV_NONEXISTENT = ExitCode(1)
 EXIT_CODE_UNINSTALL_ERROR = ExitCode(1)
diff --git a/tests/test_install.py b/tests/test_install.py
index 941f4c01..0eb2d9cc 100644
--- a/tests/test_install.py
+++ b/tests/test_install.py
@@ -109,7 +109,7 @@ def test_install_no_packages_found(pipx_temp_env, capsys):

 def test_install_same_package_twice_no_force(pipx_temp_env, capsys):
     assert not run_pipx_cli(["install", "pycowsay"])
-    assert run_pipx_cli(["install", "pycowsay"])
+    assert not run_pipx_cli(["install", "pycowsay"])
     captured = capsys.readouterr()
     assert (
         "'pycowsay' already seems to be installed. Not modifying existing installation"

Related Pull Request: https://github.com/pypa/pipx/pull/736

Merged into pipx/main on 25th September 2021

That's a good example why I love and prefer Open Source, I could fix the Problem on my own and share the improvement with the community, within a few days it was already merged and will be part of the next Release.

Pelican Plugin: read-more

2021-04-05T00:00:00+02:00

The read-more Pelican Plugin was the second one I helped to migrate to the new Structure / GitHub Organization.

After a specified length, it adds a "read more" link the the Posts Overview, you can see it on this Blog in action for example.

The Configuration is very easy, the Plugin supports a few Parameter for your pelican.conf File.

It can by installed by running python -m pip install pelican-read-more, the Source is available on https://github.com/pelican-plugins/read-more

Proudly present: My first accepted Pull Request for Pelican

2021-03-03T00:00:00+01:00

As already mentioned in my Post Migration from Wordpress to Pelican the fact that Pelican is written in Python and provide a Plugin system was important for me. So I can adjust the Code and also give something back to the Pelican Community

The Project is moving away from their monolithic Plugin Repository to a separate Organization Namespace were every Plugin has it's own Repository and get published to PyPI.

Due to the fact that i wanted to use the PDF Generator but it wasn't yet migrated, i decided to contribute (Archive: [1], [2]) and assist with updating and migrating this Plugin.

Today I proudly present: My first accepted Pull Request for Pelican (PDF Plugin) (Archive: [1], [2])

There is still room for improvement and i'm working on further fixes and features, but it's a starting Point.

You find at the bottom of every Article and Page a PDF Download Link, the linked PDF file was generated by the mentioned Plugin.