Why am I getting these Django security warnings, but not other developers on the team
<p>I am currently getting the following Django security warnings when running makemigrations:</p>

<pre><code>System check identified some issues:

WARNINGS:
?: (security.W004) You have not set a value for the SECURE_HSTS_SECONDS setting. If your entire site is served only over SSL, you may want to consider setting a value and enabling HTTP Strict Transport Security. Be sure to read the documentation first; enabling HSTS carelessly can cause serious, irreversible problems.
?: (security.W006) Your SECURE_CONTENT_TYPE_NOSNIFF setting is not set to True, so your pages will not be served with an 'x-content-type-options: nosniff' header. You should consider enabling this header to prevent the browser from identifying content types incorrectly.) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.(security.W019) You have 'django.middleware.clickjacking.XFrameOptionsMiddleware' in your MIDDLEWARE_CLASSES, but X_FRAME_OPTIONS is not set to 'DENY'. The default is 'SAMEORIGIN', but unless there is a good reason for your site to serve other parts of itself in a frame, you should change it to 'DENY'.
</code></pre>

<p>followed by a set of other warnings.  I plan on addressing these warnings, but I don't understand why everyone else on my team does not get these warnings.  I am using a Python virtualenv.  Does anyone have any ideas why I am the only one getting these warnings?</p>

<p>I've also verified I don't get these warnings using another computer, it is only my development machine.</p>