Testing the email setup for the Alpine 3.19 migration for our Sourcehut
install.

Peter

Hi Oliver,

On 02/01, Olivier C wrote:
>Vanitydoc (https://code.pfad.fr/vanitydoc/) has a couple of differences with GoHome:
>- it generates static HTML (and gemtext) files
>- it generates the documentation (as well as a link to the forge)

I do like that concept. Pretty neat. I also thought about auto linking
to godocs.io or even the official Go docs server automatically. Your
method is a cool idea though.

Thanks for sharing. Maybe if I ever get the urge I'll add the same
functionality.

Thanks Aiden! Good catch. Applied.

On 01/15, Aiden Fox Ivey wrote:
>Patch should be fairly self explanatory.
>
>Signed-off-by: Aiden Fox Ivey <aiden@fox-ivey.com>

Hi Hugo,

Just pushed version 1.9.2 to pypi. I think we'll push a new version once
5.0 is officially released but for now this should work.

Thanks,

Peter

On 11/16, Hugo Rodger-Brown wrote:
>Hi Peter - is there a planned release for the Django 5.0 upgrade?
>
>Hugo
>

Thank you! This has been applied & pushed. Will work on a release
shortly as I'm waiting for another patch to be resubmitted.

Peter

>Hi Peter, thanks for your response. Does this one work? (I took out the
>comments too since they're not really necessary.)

Hi Matt. I can manually apply this but you won't get credit in the
commit because it's not a valid hg patch (missing commit info, etc.). If
you don't care about that then I'll make the small change and commit it.
If you'd prefer your commit, please submit a new patch via `hg email`.

Thanks,

Peter

>Just read https://petersanchez.com/why-i-use-linux-workstation/ and was
>inspired to say hi. Your set-up and experience is eerily similar mine,
>except my sojurn into the BSDs was with OpenBSD. Am now mostly
>Artix/Arch-based but now doubt I will switch again in the future.

Hi Mathew. Thanks for the note! Glad you enjoyed the post. One day I'll
get around to finishing and posting one of the 30+ (seriously) drafts I
have started. 

>(Originally found you from the source hut mailing lists).

Ahh, fellow Sourcehut user. We're definitely birds of a feather my
friend :)

Matt, thanks for the second patch. Unfortunately it doesn't apply. It
looks like you may be trying to submit it directly from a parent repo
which you've included the impersonate code into. The error is:

`unable to find 'vendor/django-impersonate-1.9.1/impersonate/views.py' for patching`

There is no `vendor` directory in the repo. If you can clone the main
repo, make your changes, and resubmit the patch it should apply cleanly.

Thanks,

Peter

>Doing so prevents this code from getting flagged in our toolchain, and
>it seems to be best practice, so I'd suggest integrating this into the
>main repo.

Matt, thanks for the patch! The issue here is that the `usedforsecurty`
keyword variable was added in Python 3.9 and current supported versions
of Django are 3.2, 4.1 and 4.2.

Unfortunately 3.2 supports Python 3.6 still (though support for 3.2 goes
away in April next year) and 4.2 has support for 3.8 and is supported
until April 2026.

So I think the patch needs a Python version check and if it's 3.9+, add
the flag.

Thank you Sarah. This has been applied. For reference, there was another
patch for this same issue here:

https://lists.code.netlandish.com/~petersanchez/public-inbox/patches/71

I think it has some issues so I asked for a revision. Maybe Tom can
piggy back off your work to update his patch for some of the other
housekeeping he did. Or if you've got the inkling, feel free to send
another patch. It's much appreciated!