Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Django 1.6 #149

Closed
pombredanne opened this issue Jan 16, 2014 · 16 comments
Closed

Support for Django 1.6 #149

pombredanne opened this issue Jan 16, 2014 · 16 comments

Comments

@pombredanne
Copy link

Hi: what is the plan to support Django 1.6?

@benjaminEwhite
Copy link

Not to mention Django 1.7...

@brad
Copy link
Contributor

brad commented Apr 18, 2014

Can you elaborate on the problem you're seeing in django 1.6? I've been using it successfully and all the tests pass.

@cameel
Copy link

cameel commented Sep 2, 2014

django.test.simple is deprecated in 1.6. I'm getting warnings if I run tests with -Wall flag:

python -Wall manage.py test
/home/test/projects/lib/python2.7/site-packages/django/test/simple.py:23: PendingDeprecationWarning: The django.test.simple module and DjangoTestSuiteRunner are deprecated; use django.test.runner.DiscoverRunner instead.
/home/test/projects/lib/python2.7/site-packages/django/test/_doctest.py:57: PendingDeprecationWarning: The django.test._doctest module is deprecated; use the doctest module from the Python standard library instead.
  PendingDeprecationWarning)

The first one is imported by django_nose/runner.py#L23. The other probably by doctest plugin.

@hwkns
Copy link

hwkns commented Sep 17, 2014

Bump -- looks like this particular issue has been fixed. Is a new PyPI release on the horizon? :)

@adrianandreias
Copy link

+1 to pypi release :)

@stianpr
Copy link

stianpr commented Nov 27, 2014

+1 to PyPi release yeah!

@crane-denny
Copy link

also 👍 for the PyPi release :)

@hwkns
Copy link

hwkns commented Dec 5, 2014

@jbalogh @jsocol or anyone else who might be maintaining django-nose?

@jsocol
Copy link
Contributor

jsocol commented Dec 5, 2014

I don't have push access to PyPI but @erikrose and @jbalogh do

@jsocol
Copy link
Contributor

jsocol commented Dec 5, 2014

Me and my big mouth.

Merged #177 to pick up #164, #167, and #173. Fixing travis to stop building against 1.8 for now (see #175 #176 #178). We can turn 1.8 back on when we address those issues.

Once it builds, I'll push a 1.3. I know there are outstanding issues (and for some reason setup.py says 1.7) but this will help a lot of folks get Django 1.6 and 1.7 working.

@jbalogh
Copy link
Contributor

jbalogh commented Dec 5, 2014

💞 💞 💞 💞

@adepue
Copy link
Contributor

adepue commented Dec 5, 2014

awesome thank you!

@jsocol
Copy link
Contributor

jsocol commented Dec 5, 2014

Just pushed v1.3 to PyPI!

@erikrose
Copy link
Contributor

Good job! Thank you!

@Pike
Copy link

Pike commented Mar 10, 2015

Should this be closed now?

@jwhitlock
Copy link
Contributor

@Pike yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests