You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just installed the latest djang-crm on Ubuntu using Django-CRM documentation and I ran into a small problem. When I tried to execute python manage.py runserver 0.0.0.0:8090
I got the error: /usr/bin/env: ‘python\r’: No such file or directory
After a bit of Googling, I found the reason for the problem and a perl script to fix it. The file manage.py has CRLF characters (Windows) at the end of each line instead of just LF characters (i.e. the \r above). I have never had this problem with any Django code I have installed.
When someone is installing some code for the first time and runs into a problem like this with a command that should just work out of the box, it puts doubts in the mind of the new user that perhaps this code is not really ready for prime time. What other hidden gotchas are waiting?
I am not saying you have to cater to the Linux crowd (LF), or the Windows crowd (CRLF) or the Mac crowd (CR). I am just pointing out the issue and saying I have not run into this before. I do not know if there is a way to mitigate the issue, as people installing on a Mac will probably run into the same problem. Maybe different manage.py versions and a note to tell the user to use the appropriate one? Dumb idea, but the best I have right now.
The text was updated successfully, but these errors were encountered:
I just installed the latest djang-crm on Ubuntu using Django-CRM documentation and I ran into a small problem. When I tried to execute
python manage.py runserver 0.0.0.0:8090
I got the error:
/usr/bin/env: ‘python\r’: No such file or directory
After a bit of Googling, I found the reason for the problem and a perl script to fix it. The file
manage.py
has CRLF characters (Windows) at the end of each line instead of just LF characters (i.e. the \r above). I have never had this problem with any Django code I have installed.When someone is installing some code for the first time and runs into a problem like this with a command that should just work out of the box, it puts doubts in the mind of the new user that perhaps this code is not really ready for prime time. What other hidden gotchas are waiting?
I am not saying you have to cater to the Linux crowd (LF), or the Windows crowd (CRLF) or the Mac crowd (CR). I am just pointing out the issue and saying I have not run into this before. I do not know if there is a way to mitigate the issue, as people installing on a Mac will probably run into the same problem. Maybe different manage.py versions and a note to tell the user to use the appropriate one? Dumb idea, but the best I have right now.
The text was updated successfully, but these errors were encountered: