Hey Vimarsh, Since Django contains no C code, a segmentation fault usually indicates a bug in Python.
Did you search https://code.djangoproject.com/ for similar issues? This error happened on some versions of a popular OS distribution, although it hasn’t been reported in the last few months. If you can’t find anything, please report your OS / Python / sqlite versions. Thanks, -- Aymeric. PS - I’d love it if you said hello to everyone on this mailing list, and not just men. Try “hey folks” next time? > On 1 Dec 2016, at 09:00, Vimarsh Chaturvedi <vimars...@gmail.com> wrote: > > Hey guys, > > My first time posting here. > I downloaded the Django source code and I was going through the instructions > given in "Writing your first patch for Django" > <https://docs.djangoproject.com/en/1.10/intro/contributing/#writing-your-first-patch-for-django>. > I am working with Python 2. So, I installed packages via the py2.txt in the > requirements directory. > > So, first with the possible bug. > So, the documentation says, after your done with the installation run: > > ./runtests.py > > which gave me the following error: > ImportError: No module named django > > The README inside the tests directory says to run: > > PYTHONPATH=..:$PYTHONPATH ./runtests.py > > This command didn't give any error and the tests started running. > So, Is this a bug in the documentation, or is there something I'm missing? > > Moving on to the segmentation. > I run the test suite thrice. The first time it gave a seg fault w/o running > any tests the other two times it gave the same error after running about 3k - > 4k tests. > The exact error is: > > 16858 segmentation fault PYTHONPATH=..:$PYTHONPATH ./runtests.py > > Can any one help with this? > Is this because I'm running Python 2.x and not Python 3? > > > Thanks > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com > <mailto:django-developers+unsubscr...@googlegroups.com>. > To post to this group, send email to firstname.lastname@example.org > <mailto:email@example.com>. > Visit this group at https://groups.google.com/group/django-developers > <https://groups.google.com/group/django-developers>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/d164b3ba-d089-401d-9d92-00667e6e48d6%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/d164b3ba-d089-401d-9d92-00667e6e48d6%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6086F30D-9415-4491-A9C8-4EAD366BFFDF%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.