case-insensitive username

[Mike Dewhirst]

I have seen the two tickets and read the developer list thread[1]on this 
subject. Is there a best-practice approach to preventing usernames which 
are case-insensitively equivalent


I'm hoping someone has achieved this and might be willing to share.

My common.User inherits auth.models.AbstractUser unchanged and 
CommonUserCreationForm inherits auth.forms.UserCreationForm unchanged.


Thanks

Mike

[1] #2273 and #25617 and 
https://groups.google.com/d/topic/django-developers/a4I7rHuT4Dw/discussion


--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/df7ec8a3-883b-e8e2-81a3-f4693ada82d4%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Re: How do I customize a user registration form so it only requires email and password fields?

['Amitesh Sahay' via Django users]

Hello Tom, 
Django comes inbuilt with user authentication functions which is almost more 
than enough in most of the requirements.In your case, you just need to import 
User model in models.py and in views.py under "if" statement just return 
HttpResponse. You dont need to write anything else. For email and password you 
don't need custom models and views. 
Amitesh

Sent from Yahoo Mail on Android 
 
  On Mon, Nov 20, 2017 at 8:50, Tom Tanner 
wrote:   I'm following this 
[tutorial](https://simpleisbetterthancomplex.com/tutorial/2017/02/18/how-to-create-user-sign-up-view.html)
 on making simple registration forms in Django. I'd like to make a user 
registration form that requires only two fields: "Email" and "Password." No 
second password field, just one.
So far, My `views.py` looks like this: 
    def register(request, template="register.html", redirect='/'):     if 
request.method=="POST":     form= RegisterForm(request.POST)     if 
form.is_valid():     form.save()     email= form.cleaned_data.get("email")     
raw_password= form.cleaned_data.get("password1")     user= 
authenticate(email=email, password=raw_password)     login(request, user)     
return redirect('/')     else:     form= RegisterForm()     return 
render(request, template, {"form": form}) `forms.py` has this class in it:
    class RegisterForm(UserCreationForm):     email= 
forms.EmailField(label=_("Email"), max_length=254)         class Meta:     
model= User     fields= ("email",)
`register.html` looks simple:
    {% extends "base.html" %}        {% block main %}     Register     
     {% csrf_token %}     {{ form.as_p }}     Register         {% endblock main %}
In `urls.py`, I have this line in `urlpatterns`: `url("^register/$", 
views.register, name="register"),`.
But my registration forms looks like this, with an Email field and two Password 
fields: http://i.imgur.com/b359A5Z.png. And if I fill out all three fields and 
hit "Register," I get this error: `UNIQUE constraint failed: 
auth_user.username`.
Any idea why I'm getting this error? And how can I make sure my form only has 
two fields: Email and Password?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/94d23f3b-25ee-437d-8302-ad80d6ecc1a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1182487239.1624860.1511152196078%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

How do I customize a user registration form so it only requires email and password fields?

[Tom Tanner]

I'm following this 
[tutorial](https://simpleisbetterthancomplex.com/tutorial/2017/02/18/how-to-create-user-sign-up-view.html)
 
on making simple registration forms in Django. I'd like to make a user 
registration form that requires only two fields: "Email" and "Password." No 
second password field, just one.

So far, My `views.py` looks like this: 

def register(request, template="register.html", redirect='/'):
if request.method=="POST":
form= RegisterForm(request.POST)
if form.is_valid():
form.save()
email= form.cleaned_data.get("email")
raw_password= form.cleaned_data.get("password1")
user= authenticate(email=email, password=raw_password)
login(request, user)
return redirect('/')
else:
form= RegisterForm()
return render(request, template, {"form": form})
 
`forms.py` has this class in it:

class RegisterForm(UserCreationForm):
email= forms.EmailField(label=_("Email"), max_length=254)

class Meta:
model= User
fields= ("email",)

`register.html` looks simple:

{% extends "base.html" %}
{% block main %}
Register

{% csrf_token %}
{{ form.as_p }}
Register

{% endblock main %}

In `urls.py`, I have this line in `urlpatterns`: `url("^register/$", 
views.register, name="register"),`.

But my registration forms looks like this, with an Email field and two 
Password fields: http://i.imgur.com/b359A5Z.png. And if I fill out all 
three fields and hit "Register," I get this error: `UNIQUE constraint 
failed: auth_user.username`.

Any idea why I'm getting this error? And how can I make sure my form only 
has two fields: Email and Password?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/94d23f3b-25ee-437d-8302-ad80d6ecc1a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Would it be feasible or an overkill to use channels for real time notification in a Django application.

[Andrew Godwin]

You can indeed use Channels as the backbone of a notifications system using
WebSockets, but you'll need to overlay your own state logic on top
(notably, "what has already been sent to the client?") You can also in
theory use Channels 1 to do long-polling, but this is likely going to make
a lot more sense once Channels 2 is out and you can write native async HTTP
handlers.

Given that not all browsers or corporate networks support WebSockets, I
would suggest you first build an AJAX short-polling based solution for
maximum compatability (but it's going to strain your servers as more people
use it), then add in either long-polling, WebSockets or both as options
based on what gives you the best return in terms of UX and development time.

Andrew

On Sun, Nov 19, 2017 at 4:41 AM, Rajesh Yogeshwar <
rajesh.yogesh...@gmail.com> wrote:

> I have a SAAS application built using django. I want to now add real time
> notifications to my application. Everywhere I have looked one of the top
> suggestions is to use channels. But what I would like get to know is
>
>- Would it be an overkill to use channels only for notifications
>purpose?
>- How scalable and future proof is it?
>
> I have also failed to find a single example that would demonstrate use of
> channels for notifications purpose.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/92674051-953c-4176-9ef9-05059b3be0a0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFwN1uo1oEOrwDT7iP%2BEF1BtjJjoNgr4xpJAMMrzaJezB%3D2FGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to Speed up Loading the First Page of Django Project?

[flora . xiaoyun . huang]

Hi,

The worker id and hit id are passed via GET. (It's a website for amazon 
mechanical turker to finish tasks.) And views.py checked their worker id 
and hit id to see whether they are valid. If they're valid, then the turker 
will be directed to the following pages.

On Sunday, November 19, 2017 at 5:40:21 AM UTC-5, Antonis Christofides 
wrote:
>
> Hello,
>
> How does the verification work?
>
> Regards,
>
> Antonis
>
> Antonis Christofideshttp://djangodeployment.com
>
> On 2017-11-19 02:38, flora.xia...@gmail.com  wrote:
>
> Thank you for your reply. The first page always loads slowly while the 
> rest of the pages loads at a normal speed. Whether I restart the apache or 
> not doesn't affect the speed of loading the first page - always slow. 
>
> Below is the configuration file in the sites-available folder under 
> apache. My apache is 2.4.
> 
> ServerAdmin webmaster@localhost
>
> DocumentRoot /var/www/html
> 
> Options FollowSymLinks
> AllowOverride None
> 
> 
> Options Indexes FollowSymLinks MultiViews
> AllowOverride None
> Require all granted
> 
>
> ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
> 
> AllowOverride None
> Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
> Require all granted
> 
> ErrorLog /var/log/apache2/error.log
>
> # Possible values include: debug, info, notice, warn, error, crit,
> # alert, emerg.
> LogLevel warn
>
> CustomLog /var/log/apache2/access.log combined
>
> Alias /doc/ "/usr/share/doc/"
> 
> Options Indexes MultiViews FollowSymLinks
> AllowOverride None
> Require all granted
> Allow from 127.0.0.0/255.0.0.0 ::1/128
> 
>
> Alias /static path/to/my/project/static
> 
> Require all granted
> 
>
>   
> 
> Require all granted
> 
> 
>
>
>   WSGIDaemonProcess myproject 
> python-path=path/to/my/project:path/to/my/project/lib/python2.7/site-packages
>   WSGIProcessGroup myproject
>   WSGIScriptAlias / path/to/my/project/myproject/wsgi.py
> 
>
> Thank you!
>
> 在 2017年11月17日星期五 UTC-5上午8:27:24，Jason写道： 
>>
>> I would suggest you post the configuration file here as well as the 
>> server specifications and average CPU/memory usage.  Because what you're 
>> describing is definitely not normal and is most likely related to how 
>> Apache is configured.
>>
>> A point of clarification: does the first page always load slowly, or is 
>> it just the first page after you restart the server?
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com .
> To post to this group, send email to django...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/4cb4d8a9-6709-4f89-923f-bf5cc311e05a%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/10f58d4b-fd3f-461f-81a3-f0f8d2a6554e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Limit a view to superuser only

[yingi keme]

All of a sudden and out of the blue, it just worked. I had the re-run my 
server

On Sunday, November 19, 2017 at 5:54:11 AM UTC-8, Jani Tiainen wrote:
>
> Hi.
>
> Could you paste the full traceback here because having an OSError sounds 
> like there is is something else wrong in your system.
>
> On 19 Nov 2017, at 15.22, yingi keme  
> wrote:
>
> I have a function that i want to be accessed only if the user is a 
> supersuser.
>
> I have tried this
>
> from django.contrib.admin.views.decorators import staff_member_required
>
> @staff_member_required
> def my_view(request):
> template_name = 'Core\CustomizedAdmin.html'
> return render(request, template_name)
>
>
> What happens is that when i try to access this view, it directs me to the 
> default login admin page. 
> And then when i login as a superuser, it gives an OSError invalid argument:
>
> I expected that after login in as a superuser it will redirect to the Page 
> i want.
>
> Am i doing it the wrong way?
>
> Is there an alternative way to Limit a view to superuser only?
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com .
> To post to this group, send email to django...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/fc05e300-5e71-4bc5-b388-2996c5b8bb0a%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/47bc5cb1-0b67-4849-b621-ef2f066f25e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Limit a view to superuser only

[Jani Tiainen]

Hi.

Could you paste the full traceback here because having an OSError sounds like 
there is is something else wrong in your system.

> On 19 Nov 2017, at 15.22, yingi keme  wrote:
> 
> I have a function that i want to be accessed only if the user is a supersuser.
> 
> I have tried this
> 
> from django.contrib.admin.views.decorators import staff_member_required
> 
> @staff_member_required
> def my_view(request):
> template_name = 'Core\CustomizedAdmin.html'
> return render(request, template_name)
> 
> 
> What happens is that when i try to access this view, it directs me to the 
> default login admin page. 
> And then when i login as a superuser, it gives an OSError invalid argument:
> 
> I expected that after login in as a superuser it will redirect to the Page i 
> want.
> 
> Am i doing it the wrong way?
> 
> Is there an alternative way to Limit a view to superuser only?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to django-users@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-users 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/fc05e300-5e71-4bc5-b388-2996c5b8bb0a%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/14120C38-4157-433C-8CBE-BFE471D8E2F8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Would it be feasible or an overkill to use channels for real time notification in a Django application.

[Rajesh Yogeshwar]

I have a SAAS application built using django. I want to now add real time 
notifications to my application. Everywhere I have looked one of the top 
suggestions is to use channels. But what I would like get to know is

   - Would it be an overkill to use channels only for notifications purpose?
   - How scalable and future proof is it?

I have also failed to find a single example that would demonstrate use of 
channels for notifications purpose.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/92674051-953c-4176-9ef9-05059b3be0a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Limit a view to superuser only

[yingi keme]

I have a function that i want to be accessed only if the user is a 
supersuser.

I have tried this

from django.contrib.admin.views.decorators import staff_member_required

@staff_member_required
def my_view(request):
template_name = 'Core\CustomizedAdmin.html'
return render(request, template_name)


What happens is that when i try to access this view, it directs me to the 
default login admin page. 
And then when i login as a superuser, it gives an OSError invalid argument:

I expected that after login in as a superuser it will redirect to the Page 
i want.

Am i doing it the wrong way?

Is there an alternative way to Limit a view to superuser only?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/fc05e300-5e71-4bc5-b388-2996c5b8bb0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to Speed up Loading the First Page of Django Project?

[Antonis Christofides]

Hello,

How does the verification work?

Regards,

Antonis

Antonis Christofides
http://djangodeployment.com

On 2017-11-19 02:38, flora.xiaoyun.hu...@gmail.com wrote:
> Thank you for your reply. The first page always loads slowly while the rest of
> the pages loads at a normal speed. Whether I restart the apache or not doesn't
> affect the speed of loading the first page - always slow.
>
> Below is the configuration file in the sites-available folder under apache. My
> apache is 2.4.
> 
>         ServerAdmin webmaster@localhost
>
>         DocumentRoot /var/www/html
>         
>                 Options FollowSymLinks
>                 AllowOverride None
>         
>         
>                 Options Indexes FollowSymLinks MultiViews
>                 AllowOverride None
>                 Require all granted
>         
>
>         ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
>         
>                 AllowOverride None
>                 Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
>                 Require all granted
>         
> ErrorLog /var/log/apache2/error.log
>
>         # Possible values include: debug, info, notice, warn, error, crit,
>         # alert, emerg.
>         LogLevel warn
>
>         CustomLog /var/log/apache2/access.log combined
>
>     Alias /doc/ "/usr/share/doc/"
>     
>         Options Indexes MultiViews FollowSymLinks
>         AllowOverride None
>         Require all granted
>         Allow from 127.0.0.0/255.0.0.0 ::1/128
>     
>
> Alias /static path/to/my/project/static
>         
>                 Require all granted
>         
>
>   
>         
>                 Require all granted
>         
>         
>
>
>   WSGIDaemonProcess myproject
> python-path=path/to/my/project:path/to/my/project/lib/python2.7/site-packages
>   WSGIProcessGroup myproject
>   WSGIScriptAlias / path/to/my/project/myproject/wsgi.py
> 
>
> Thank you!
>
> 在 2017年11月17日星期五 UTC-5上午8:27:24，Jason写道：
>
> I would suggest you post the configuration file here as well as the server
> specifications and average CPU/memory usage.  Because what you're
> describing is definitely not normal and is most likely related to how
> Apache is configured.
>
> A point of clarification: does the first page always load slowly, or is it
> just the first page after you restart the server?
>
> -- 
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com
> .
> To post to this group, send email to django-users@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/4cb4d8a9-6709-4f89-923f-bf5cc311e05a%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a9e4105e-fcbd-dc36-235c-97182ed730c4%40djangodeployment.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django field model for HTML parser?

[Antonis Christofides]

Hello,

First of all: If you are just starting to learn, and because the amount you have
to learn can be overwhelming, I'd suggest to not care about the wysiwyg editor
at this stage. Pretend that your users can enter HTML in the field, and do all
the rest. After you get some understanding of static files, only then come back
to this issue.

But to (prematurely) answer your question, if you have DEBUG=True and running
django with manage.py runserver, you shouldn't need to care about STATIC_ROOT
and STATIC_URL and collectstatic. Just forget about them. When the time comes to
deploy your application and turn DEBUG off, then you will need to understand how
static files work in production
.

Regards,

Antonis

Antonis Christofides
http://djangodeployment.com


On 2017-11-19 01:38, drone4four wrote:
>
> The official Django docs specify that STATIC_ROOT is indicated in settings.py
> at the STATIC_URL variable (which is near the bottom).  The official Django
> docs says:
>
> Configure your web server to serve the files in STATIC_ROOT
> 
> under
> the URL STATIC_URL
> 
> .
>  
>
> (link )
>
>
> I’m not running Apache. My Django serving is running locally. The absolute
> path in my file tree to my Django root directory is:
>
> /home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/dobbs_portal_blog/
>
> Inside dobbs_portal_blog is where I placed the static folder. Therefore, the
> line in my settings.py where I declare the variable, I changed from the 
> default:
>
> |
> *STATIC_URL ='/static/'*
> |
>
> to:
>
> *|
> STATIC_URL
> ='/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/dobbs_portal_blog/static/'
> |*
>
> That is my best guess at attempting resolve the “pretty obvious” error 
> message:
>
> You're using the staticfiles app without having set the STATIC_ROOT
> setting to a filesystem path.
>
>
> Yet I am still doing something wrong because invoking python3
> dobbs_portal_blog/manage.py collectstatic, I still get the same message:
>
>
> $ python3 dobbs_portal_blog/manage.py collectstatic
> You have requested to collect static files at the destination location as
> specified in your settings.
> This will overwrite existing files! Are you sure you want to do this?
> Type 'yes' to continue, or 'no' to cancel: yes Traceback (most recent call
> last):  File "dobbs_portal_blog/manage.py", line 22, in 
>    execute_from_command_line(sys.argv)  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/core/management/__init__.py",
> line 364, in execute_from_command_line    utility.execute()  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/core/management/__init__.py",
> line 356, in execute
>    self.fetch_command(subcommand).run_from_argv(self.argv)  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/core/management/base.py",
> line 283, in run_from_argv    self.execute(*args, **cmd_options)  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/core/management/base.py",
> line 330, in execute    output = self.handle(*args, **options)  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
> line 199, in handle    collected = self.collect()  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
> line 124, in collect    handler(path, prefixed_path, storage)  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
> line 354, in copy_file    if not self.delete_file(path, prefixed_path,
> source_storage):  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
> line 260, in delete_file    if self.storage.exists(prefixed_path):  File
> 
> "/home/gnull/Dropbox/TECH/python/2017/django-experiment-with-nick/subgenius-blog-env/lib/python3.6/site-packages/django/core/files/storage.py",
> line 392, in exists    return