Bug 257333 - [NEW PORT] devel/py-async-exit-stack: AsyncExitStack backport for Python 3.5+
Summary: [NEW PORT] devel/py-async-exit-stack: AsyncExitStack backport for Python 3.5+
Status: Closed Overcome By Events
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
Depends on:
Blocks: 257334
  Show dependency treegraph
 
Reported: 2021-07-22 13:39 UTC by Goran Mekić
Modified: 2022-01-03 08:33 UTC (History)
3 users (show)

See Also:


Attachments
asyncexit.diff (1.82 KB, patch)
2021-07-22 13:39 UTC, Goran Mekić
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Goran Mekić 2021-07-22 13:39:04 UTC
Created attachment 226610 [details]
asyncexit.diff

QA:

  * portlint: OK (looks fine.)
  * testport: OK (poudriere: 13.0, amd64 tested)
  * maketest: OK (23 passed)
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2021-07-28 02:20:49 UTC
Python doesn't need to block / be assignee on new ports
Comment 2 Goran Mekić 2021-10-27 12:14:16 UTC
Any chance we can merge this?
Comment 3 Hiroki Tagato freebsd_committer freebsd_triage 2022-01-03 04:27:05 UTC
(In reply to Goran Mekić from comment #2)

Now the ports tree has python 3.7 or later.

The following URL says this software is for python 3.5 and 3.6.
https://pypi.org/project/async-exit-stack/

So I guess the port is no longer useful in our ports tree.

Could we just close this?