On Tue, 14 Jul 2015 14:01:25 +1200, Robert Collins <robe...@robertcollins.net> wrote: > So unittest.mock regressed during 3.5, and I found out when I released > the mock backport. > > The regression is pretty shallow - I've applied the fix to 3.6, its a > one-liner and comes with a patch. > > Whats the process for getting this into 3.5? Its likely to affect a > lot of folk using mock (pretty much every OpenStack project got git > with it when I released mock 1.1).
3.5 hasn't been released yet. The patch ideally would have gone into 3.5 first, then been merged to 3.6. As it is, you'll apply it to 3.5, and then do a null merge to 3.6. It will get released in the next 3.5 beta. --David _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
