#42476: py-mock @1.0.1: enable py33 and py34 as well ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-mock | ------------------------------+-------------------------------- Comment (by patrik.hartlen@…): Replying to [comment:1 Peter.Danecek@…]:

Update:

I have now no *immediate* need that this is implemented. I was able resolve the problem with `mock` in python 3.3 in the respective packages I was interested in, so this concrete use case is gone.

Still, I could imagine there are cases where `py33-mock` and `py34-mock` might be helpful to get software working fast. So consider this and close if found appropriate.

I a fine if this ticket is just closed.

I was trying to find how similar modules have been handled on macports, looking at argparse that was introduced in 2.7 and 3.2 that module is not included in the Portfile for the versions 2.7 and 3.2. I will try to find other examples before closing the ticket. -- Ticket URL: <https://trac.macports.org/ticket/42476#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#42476: py-mock @1.0.1: enable py33 and py34 as well ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-mock | ------------------------------+-------------------------------- Comment (by Peter.Danecek@…): Not sure if the example of `argparse` applies here, because of the difference in namespace. The package provides `mock` while Python 3.3+ provides `unitest.mock`. Software needs to account for this difference, so it may compare more to the situation with `simplejson` (package) vs. `json` (Python 2.6+) where `py-simplejson` packages still exist or **maybe** the cited `py-distutils-extra`, which I cannot say much about. But as I mentioned before, this is only an **extra** consideration. For my special purpose it is not relevant anymore and the ticket can just be closed. Not implementing this, might be the extra incentive to changes depending software sooner ;-) -- Ticket URL: <https://trac.macports.org/ticket/42476#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#42476: py-mock @1.0.1: enable py33 and py34 as well ------------------------------+-------------------------------- Reporter: Peter.Danecek@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-mock | ------------------------------+-------------------------------- Comment (by patrik.hartlen@…): Replying to [comment:5 Peter.Danecek@…]:

Implementing this ticket would solve #42811. Ok I see no harm in adding support for Python 3.3 & 3.4 since it will fix upstream dependencies in other ports waiting for patches. I don't know if this will violate any rules so if it is ok with macport devs then lets add a patch for 3.3 and 3.4.

-- Ticket URL: <https://trac.macports.org/ticket/42476#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X