-
Notifications
You must be signed in to change notification settings - Fork 173
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
monkeytype run manage.py test
doesn't produce sqllite file
#34
Comments
Sorry, to add more detail I'm running this on: |
Do you get an error or any output at all from |
Closing for now since there's not enough information here to do any debugging; will reopen if we get full paste of shell session, with all output. Most likely issue is that you are hitting #28. |
Other than some warnings generated by my tests, there's no output that seems like it's from
|
That's odd. Do you have a |
The test runner could affect this; for example, when using
If my theory is correct, then MonkeyType whould be tracing just the main test supervisor process, which is (I guess) Django-only code. @nsillik Can you try running the tests with just one process? |
@mandx I'm still not able to generate stubs, but I think that's a separate issue. @carljm I do not have a I'm going to close this while I see what the issue with stub generation is. Thanks for your help! |
Thanks for identifying the problem, @mandx ! I'll add an entry about this issue to the FAQ. |
@carljm I came back to say just that, a note about this "gotcha" would be really appreciated by newcomers, specially because Django has this behavior enabled by default, and most likely people will try out this tool by running unit tests in a local development environment. BTW, thanks for opensourcing this! |
FAQ entry added: http://monkeytype.readthedocs.io/en/latest/faq.html |
I've run
monkeytype run manage.py test
in my django project afterpip install monkeytype
(inside of a virtual env) and I'm not seeing any output of the sqllite file described in the README.Running
monkeytype stub
for any of my modules doesn't work either. If there's something different that I have to do for django tests, let's add that to the README. Otherwise, am I missing something?The text was updated successfully, but these errors were encountered: