search

HassenPy / django-pdb

Gives you `manage.py runserver --pdb` and `manage.py test --pdb`
394 stars 61 forks source link

manage.py test does not work with south #7

Closed bubenkoff closed 12 years ago

bubenkoff commented 12 years ago

Hi, when i enable this app on project with south enabled, looks like it breakes it can you check.

[edit - tomchristie: updated title of ticket]

tomchristie commented 12 years ago

Any chance you could give a bit more info - what breaks? what would I be looking for? do you have a simple project on GitHub I could use to reproduce it? Can you double check that whatever problem your seeing reproduces with 'djangopdb' in INSTALLED_APPS and does not reproduce if you comment it out? etc...

bubenkoff commented 12 years ago

yes i have however, project isn't simple and it's not on github

without pdb

~/projects/wcms (t55_model-changes-according-to-project-needs-zojax ✘)✹ ᐅ bin/django test --settings=wcms.settings_product_finder_test highlight featured Creating test database for alias 'default'... Creating tables ... Creating table highlight_tests_somecontent Installing custom SQL ... Installing indexes ... No fixtures found. .Creating tables ... Creating table featured_tests_somecontent Installing custom SQL ... Installing indexes ... No fixtures found.

.

Ran 2 tests in 0.738s

OK Destroying test database for alias 'default'…

with pdb enabled

~/projects/wcms (t55_model-changes-according-to-project-needs-zojax ✘)✹ ᐅ bin/django test --settings=wcms.settings_product_finder_test highlight featured Creating test database for alias 'default'... Error: Database test_geodjango couldn't be flushed. Possible reasons:

project is here

git clone git@git.sandowmedia.com:wcms.git

git checkout t55_model-changes-according-to-project-needs-zojax

python bootstrap.py

bin/buildout -c product_finder-dev.cfg

bin/django test --settings=wcms.settings_product_finder_test highlight featured

thanks

On Dec 27, 2011, at 4:23 PM, Tom Christie wrote:

Any chance you could give a bit more info - what breaks? what would I be looking for? do you have a simple project on GitHub I could use to reproduce it? Can you double check that whatever problem your seeing reproduces with 'djangopdb' in INSTALLED_APPS and does not reproduce if you comment it out? etc...

Reply to this email directly or view it on GitHub: https://github.com/tomchristie/django-pdb/issues/7#issuecomment-3281697

Anatoly Bubenkov +380666358527 bubenkoff@gmail.com

tomchristie commented 12 years ago

Any chance you could try throwing an empty 'models.py' into the 'django_pdb' directory, and see if that does the trick?

There's nothing at all in the project that should be causing any obvious problems, but perhaps it's something like trying to find a 'models.py' for an app that doesn't have/need one, that's causing the bug.

bubenkoff commented 12 years ago

thanks with check this and return to you

On Tue, Dec 27, 2011 at 7:12 PM, Tom Christie reply@reply.github.com wrote:

Any chance you could try throwing an empty 'models.py' into the 'django_pdb' directory, and see if that does the trick?

There's nothing at all in the project that should be causing any obvious problems, but perhaps it's something like trying to find a 'models.py' for an app that doesn't have/need one, that's causing the bug.

Reply to this email directly or view it on GitHub: https://github.com/tomchristie/django-pdb/issues/7#issuecomment-3283142

Anatoly Bubenkov +380(66)6358527

bubenkoff commented 12 years ago

tried adding an empty models.py into django_pdb - no luck, same thing

tomchristie commented 12 years ago

Try moving 'django_pdb' to the top (or bottom) of your INSTALLED_APPS, sounds like it's conflicting with something else that's also providing a test and/or runserver management command. I'm updating the README to try to reflect this...

bubenkoff commented 12 years ago

looks like it's clear about the reson - south overrides test command as you do, so your app and south app are mutually exclusive

On Thu, Dec 29, 2011 at 6:45 PM, Tom Christie reply@reply.github.com wrote:

Try moving 'django_pdb' to the top (or bottom) of your INSTALLED_APPS, sounds like it's conflicting with something else that's also providing a test and/or runserver management command.  I'm updating the README to try to reflect this...

Reply to this email directly or view it on GitHub: https://github.com/tomchristie/django-pdb/issues/7#issuecomment-3302388

Anatoly Bubenkov +380(66)6358527

tomchristie commented 12 years ago

Yup. README updated. There will be some ways around this, but it's a little awkward.

tomchristie commented 12 years ago

Closing this, and added the more general ticket covering both cases.

bubenkoff commented 12 years ago

i think better is to just add custom command - test-pdb or something like that

On Thu, Dec 29, 2011 at 7:11 PM, Tom Christie reply@reply.github.com wrote:

Closing this, and added the more general ticket covering both cases.

Reply to this email directly or view it on GitHub: https://github.com/tomchristie/django-pdb/issues/7#issuecomment-3302666

Anatoly Bubenkov +380(66)6358527

tomchristie commented 12 years ago

Possibly. See if anyone has any good answers.