Re: Adding hard dependencies to Django's test suite

I'm -0 for freezegun, +0 for unittest. I see unittest as a polyfill that we'll only need to keep around for about 3 years, and I like the "nudging people to use python3" Freezegun is a less popular, less established library, and I'd personally still rather see it be an optional dependency. I

Re: Adding hard dependencies to Django's test suite

> On 28 Nov 2014, at 02:42, Tim Graham wrote: > > There have been some proposals to add new dependencies in Django's test suite: > > 1. #23289 - unittest.mock (included in Python 3.3+; a backport version would > need be installed when testing on Python 2.7 and 3.2) > 2. #23792 - freezegun (to

Re: Adding hard dependencies to Django's test suite

On 11/27/2014 06:42 PM, Tim Graham wrote: > There have been some proposals to add new dependencies in Django's test > suite: > > 1. #23289 - unittest.mock > (included in Python 3.3+; a backport version would need be installed > when testing on Python 2

Re: Adding hard dependencies to Django's test suite

I agree. Anyone wanting to contribute to Django should be able to run a pip install -r test_requirements.txt. Marc On 28 November 2014 at 04:03, Fabio Caritas Barrionuevo da Luz < bna...@gmail.com> wrote: > python 2.7.9 rc1 include a backported version of python3 ensurepip > > see: > > https://h

Re: Adding hard dependencies to Django's test suite

python 2.7.9 rc1 include a backported version of python3 ensurepip see: https://hg.python.org/cpython/rev/592a5414fabd https://docs.python.org/2/library/ensurepip.html -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django its

Adding hard dependencies to Django's test suite

There have been some proposals to add new dependencies in Django's test suite: 1. #23289 - unittest.mock (included in Python 3.3+; a backport version would need be installed when testing on Python 2.7 and 3.2) 2. #23792