Re: Incorrect number of bindings supplied. The current statement uses 0, and there are 1 supplied

This issue has been resolved. Please ignore it. I had a hard-coded query to debug a issue and it was not removed..Thanks for looking into it. On Monday, September 19, 2016 at 10:07:02 PM UTC-4, premdjango wrote: > > compiler sql == SELECT "django_migrations"."app", &

Re: Incorrect number of bindings supplied. The current statement uses 0, and there are 1 supplied

six.reraise(dj_exc_type, dj_exc_value, traceback) File "/Users/premanandlakshmanan/Documents/django-contribute/django/django/utils/six.py", line 685, in reraise raise value.with_traceback(tb) File "/Users/premanandlakshmanan/Documents/django-contribute/django/dja

Incorrect number of bindings supplied. The current statement uses 0, and there are 1 supplied

Im trying to run the tests in Django but get the following error. (djangodev) Anands-MacBook-Pro:tests premlaks$ ./runtests.py --settings=test_sqlite requests File "/Users/premanandlakshmanan/Documents/django-contribute/django/django/db/models/query.py", line 1072, in _fetch_all sel

Re: Adding new models to test Django unit test case

My pull requests failed - https://github.com/django/django/pull/7094 Looks like the test is running by default against sqllite. How do I run it against the postgres? On Monday, August 15, 2016 at 1:48:48 PM UTC-4, premdjango wrote: > > It worked..thanks. > > On Monday, August 15,

Re: Adding new models to test Django unit test case

It worked..thanks. On Monday, August 15, 2016 at 1:12:52 PM UTC-4, Tim Graham wrote: > > You'll need to modify the migrations manually. Take a look at a previous > commit on the migrations files for an example. > > On Monday, August 15, 2016 at 1:00:42 PM UTC-4, premdjango

Re: Adding new models to test Django unit test case

in tests/postgres_tests/migrations. > > On Sunday, August 14, 2016 at 10:53:45 PM UTC-4, premdjango wrote: >> >> I'm implementing a fix for a ticket-26819 and need to add new models to >> test it. >> >> The new models were added to tests/postgres_tests/models.py &g

Adding new models to test Django unit test case

I'm implementing a fix for a ticket-26819 and need to add new models to test it. The new models were added to tests/postgres_tests/models.py but would like to know how to run the migrations before I run the tests. Do I need to run the migrations explicitly or django run tests will take care of

Running Django tests for postgres_tests

I'm trying to run django tests for a particular module - postgres_tests. The tests runs but it says it skipped=312 tests, I believe none of the test case run. How do I fix this issue? (djangodev) Anands-MBP:tests laks$ ./runtests.py postgres_tests Testing against Django installed in '/

Re: Contribute to Django - Python 3 or Python 2

Thanks Michael, That was the confusion. I will go ahead with Python 3. On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote: > > Hello, > Im trying to contribute to Django project and started with this document. > > https://docs.djangoproject.com/en/dev/intro/contributi

Re: Contribute to Django - Python 3 or Python 2

Tim - The reason I said its used in most of the places is because - for example: pip install -e /path/to/your/local/clone/django/ I would expect pip3 install of pip.. On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote: > > Hello, > Im trying to contribute to Djang

Django tests failing for development env

I want to contribute to Django community, so I was trying to setup my env using the following doc - https://docs.djangoproject.com/en/dev/intro/contributing/ I ran the tests and get the following output - == FAIL: test_old_

Contribute to Django - Python 3 or Python 2

Hello, Im trying to contribute to Django project and started with this document. https://docs.djangoproject.com/en/dev/intro/contributing/ Here in couple of places I see Python3 is being used but in most places python2 is used. Should I use Python 3 or Python 2? -- You received this message