Bug 247686 - [NEW PORT] devel/py-class-registry: Factory+Registry pattern for Python classes
Summary: [NEW PORT] devel/py-class-registry: Factory+Registry pattern for Python classes
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: feature, needs-qa
Depends on:
Blocks: 247687
  Show dependency treegraph
 
Reported: 2020-07-01 07:49 UTC by waitman
Modified: 2021-11-23 08:15 UTC (History)
6 users (show)

See Also:
koobs: maintainer-feedback? (waitman)


Attachments
devel/py-class-registry 2.1.2 (2.76 KB, patch)
2020-07-01 07:49 UTC, waitman
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description waitman 2020-07-01 07:49:53 UTC
Created attachment 216103 [details]
devel/py-class-registry 2.1.2

needed for devel/py-b2 2.0.0
Comment 1 Li-Wen Hsu freebsd_committer freebsd_triage 2020-07-02 07:48:01 UTC
Please list yourself in the MAINTAINER filed. Thanks!
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2020-07-03 03:32:08 UTC
Update COMMENT to match setup.py:description (modulo portlint compliance):

"Factory+Registry pattern for Python classes"
Comment 3 Henry 2020-07-18 18:49:50 UTC
This should probably be called py-class-registry2 as there are 2.x [1] and a 3.x [3] branches from the same project [3] but it's incompatible with at least B2 [4], which is the initial use case.

Also note the 3.x branch dropped 2.7 support.

[1] https://pypi.org/project/class-registry/
[2] https://pypi.org/project/phx-class-registry/
[3] https://github.com/todofixthis/class-registry/tags
[4] https://github.com/Backblaze/B2_Command_Line_Tool/blob/49a29b6d786e68db58ff8303c718fdab9d43eaaa/requirements.txt#L4
Comment 4 Bartek Rutkowski freebsd_committer freebsd_triage 2021-11-23 08:15:15 UTC
Would you want to be a maintainer of this port? I'm happy to commit it to get the b2 port over the line, but you need to take on maintainership of this submission or find a maintainer for it.