Opened 16 years ago
Closed 16 years ago
#5626 closed (wontfix)
Mac OS X permissions command could be more succinct.
| Reported by: | Owned by: | Matt Boersma | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | terminal Mac OS X | |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
In the Mac OSX Permissions box (at the top of Creating a Project), there is some text suggesting a possible permissions solution:
... To do this, open Terminal.app and navigate (using the cd command) to the directory where django-admin.py is installed, then run the command chmod +x django-admin.py.
|
This line could be made quicker and easier by replacing "and navigate... ." with "and run the command chmod +x `which django-admin.py`." This removes the work involved in locating the installation directory, making it a little less painless, and makes the fix a one-step process. It will also guarantee that the correct django-admin.py is modified.
Possible problem: Backticks can be difficult to recognize in some fonts, but monospace fonts usually show them correctly. The user will most likely copy and paste the command anyway, making this issue moot.
Attachments (1)
Change History (10)
Changed 16 years ago by
comment:1 Changed 16 years ago by
| Has patch: | set |
|---|---|
| Keywords: | Mac OS X added |
| Owner: | changed from nobody to Matt Boersma |
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Ready for checkin |
comment:2 Changed 16 years ago by
| Summary: | Mac OSX Permissions, command could be more succinct. → Mac OS X typo, permissions command could be more succinct. |
|---|
comment:3 follow-up: 4 Changed 16 years ago by
| Triage Stage: | Ready for checkin → Design decision needed |
|---|
Using which assumes the user has successfully gotten django/bin into the PATH, which isn't necessarily a safe assumption.
comment:4 Changed 16 years ago by
Replying to ubernostrum:
Using
whichassumes the user has successfully gottendjango/bininto thePATH, which isn't necessarily a safe assumption.
It is if they followed the previous instructions: python setup.py install places scripts in the path on OSX. However, even if they hadn't, the pull-out assumes that they have. (The first sentence ends with "... when you try to run django-admin.py startproject," which doesn't tell them where that script might be, if they don't already know.) It also doesn't help the user find that directory (django/bin), which could be difficult if it's installed into some random site-packages directory.
comment:5 Changed 16 years ago by
The tutorial context already implies django-admin.py is on the search PATH. If that's not a safe assumption, more of the tutorial needs to be changed. Otherwise, this patch seems sane to me. Let's fix the "Max OS X" typo at least.
comment:6 Changed 16 years ago by
comment:7 Changed 16 years ago by
| Description: | modified (diff) |
|---|---|
| Summary: | Mac OS X typo, permissions command could be more succinct. → Mac OS X permissions command could be more succinct. |
This was really two bugs if we're being pedantic, so I fixed the "Max OS X" typo separately and changed the description to focus on the "chmod +x which django-admin.py" issue.
comment:9 Changed 16 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
I think I'm just going to punt this; there's really not a bug here, and what remains is basically a bikeshed argument.
Fixes typo, shortens command to make django-admin.py executable