You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project README.rst contains a "Status" section which was composed in the repo's very first commit, and has remained unchanged ever since. Which means that both on the landing page of the repo here, and on the package's PyPi listing page, capturer's' "status" is described thusly:
The capturer package was developed as a proof of concept over the course of a
weekend, because I was curious to see if it could be done (reliably). After a
weekend of extensive testing it seems to work fairly well so I'm publishing the
initial release as version 1.0, however I still consider this a proof of
concept because I don't have extensive "production" experience using it yet.
Here's hoping it works as well in practice as it did during my testing :-).
Considering that was 5 years ago, and capturer hit the big three-point-oh with its most recent (9th!) release, that "status" reads a bit like some sort of weird impostor-syndrome performance art piece. 😆
The text was updated successfully, but these errors were encountered:
The project
README.rst
contains a "Status" section which was composed in the repo's very first commit, and has remained unchanged ever since. Which means that both on the landing page of the repo here, and on the package's PyPi listing page, capturer's' "status" is described thusly:Considering that was 5 years ago, and
capturer
hit the big three-point-oh with its most recent (9th!) release, that "status" reads a bit like some sort of weird impostor-syndrome performance art piece. 😆The text was updated successfully, but these errors were encountered: