id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
30816	Clarify how to test changes with an existing Django project.	Ad Timmering	Ad Timmering	"(Adding a ticket based on [https://groups.google.com/forum/#!topic/django-core-mentorship/Ix1rOFihCcE this discussion] on django-core-mentorship. The thread went dead and as far as I can tell no ticket was added but it seems like a useful addition to me.)

The [https://groups.google.com/forum/#!topic/django-core-mentorship/Ix1rOFihCcE current tutorial] on ""Writing your first patch for Django"" walks though the process of cloning the repository, installing in a virtual environment with `pip -e` and the test suite. 

This sets people up to start a branch to make changes to Django and run the tests, however it is not clear on how to make a test Django project that runs with the modified Django version.

**Suggested updates to documentation**
1. Slightly reword the section explaining to `pip -e` to explain how this sets up a virtual environment ''within'' the directory where you cloned Django - and that this becomes the environment you can start making changes and run the Django testsuite, as explain further on in the tutorial.

2. Add an ""admonition"" box, or point to a section later in the document, to explain:
  ""Do you want to start a test Django project that reflects the changed you have made?"" explaining that you should make a different directory with a different virtual env, then pip -e /path/to/your/local/clone/django/ again, and from there go as usual with django-admin. 
"	Cleanup/optimization	closed	Documentation	dev	Normal	fixed			Accepted	1	0	0	0	0	0