Opened 8 years ago
Closed 7 years ago
#53596 closed update (fixed)
py-mock @1.0.1_0: update to 2.0.0
Reported by: | JDLH (Jim DeLaHunt) | Owned by: | petrrr |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | py-mock |
Description
Port py-mock is at @1.0.1_0. Current version is 2.0.0 per https://pypi.python.org/pypi/mock/ 1.0.1 dates back to July 2015, and 2.0.0 became current in April 2016, per https://github.com/testing-cabal/mock/releases.
However, this module is distributed with the Python standard library as unittest.mock
starting with Python 3.3, per https://docs.python.org/dev/library/unittest.mock.html . So, I suppose the purpose of py-mock is to provide back-ports to Python3 before 3.3 and to Python 2.7.
I am not able to come up with an updated Portfile on my own right now.
Change History (6)
comment:1 Changed 8 years ago by mf2k (Frank Schima)
Cc: | patrik.hartlen@… removed |
---|---|
Owner: | set to patrik.hartlen@… |
Status: | new → assigned |
Summary: | py-mock @1.0.1_0: upgrade to 2.0.0 → py-mock @1.0.1_0: update to 2.0.0 |
comment:2 Changed 7 years ago by petrrr
Cc: | petrrr added |
---|
comment:3 Changed 7 years ago by petrrr
comment:4 Changed 7 years ago by petrrr
Owner: | changed from patrik.hartlen@… to petrrr |
---|
Okay, looks like the maintainer is not active any more.
comment:5 Changed 7 years ago by petrrr
Cc: | petrrr removed |
---|
comment:6 Changed 7 years ago by kurthindenburg (Kurt Hindenburg)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Ping?
Some ports still require this mock as a dependency also on python > 3.3. In order to use
unittest.mock
, one would need to change some imports which has not always been implemented.