Django

Code

Ticket #5626 (closed: wontfix)

Opened 1 year ago

Last modified 1 year ago

Mac OS X permissions command could be more succinct.

Reported by: blinks@acm.org Assigned to: mboersma
Milestone: Component: Documentation
Version: SVN Keywords: terminal Mac OS X
Cc: Triage Stage: Design decision needed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description (Last modified by mboersma)

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

5626.diff (0.9 kB) - added by mboersma on 09/27/07 13:48:20.
Fixes typo, shortens command to make django-admin.py executable

Change History

09/27/07 13:48:20 changed by mboersma

  • attachment 5626.diff added.

Fixes typo, shortens command to make django-admin.py executable

09/27/07 13:48:51 changed by mboersma

  • status changed from new to assigned.
  • needs_better_patch changed.
  • needs_tests changed.
  • owner changed from nobody to mboersma.
  • keywords changed from terminal to terminal Mac OS X.
  • needs_docs changed.
  • has_patch set to 1.
  • stage changed from Unreviewed to Ready for checkin.

09/27/07 13:51:03 changed by mboersma

  • summary changed from Mac OSX Permissions, command could be more succinct. to Mac OS X typo, permissions command could be more succinct..

(follow-up: ↓ 4 ) 09/27/07 21:59:05 changed by ubernostrum

  • stage changed from Ready for checkin to Design decision needed.

Using which assumes the user has successfully gotten django/bin into the PATH, which isn't necessarily a safe assumption.

(in reply to: ↑ 3 ) 09/28/07 10:29:59 changed by anonymous

Replying to ubernostrum:

Using which assumes the user has successfully gotten django/bin into the PATH, 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.

10/02/07 11:09:09 changed by mboersma

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.

10/19/07 10:43:45 changed by mboersma

(In [6535]) Fixed #5633, refs #5626: Change "Max OS X" to "Mac OS X" in tutorial01.

10/19/07 10:45:41 changed by mboersma

  • description changed.
  • summary changed from Mac OS X typo, permissions command could be more succinct. to 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.

10/24/07 21:32:17 changed by derelm

Will all this work without sudo-ing? Just a thought…

12/01/07 12:45:38 changed by ubernostrum

  • status changed from assigned to closed.
  • resolution set to wontfix.

I think I'm just going to punt this; there's really not a bug here, and what remains is basically a bikeshed argument.

Add/Change #5626 (Mac OS X permissions command could be more succinct.)




Change Properties
Action