Opened 18 years ago
Closed 18 years ago
#3786 closed (fixed)
Misc small documentation fixes/suggestions
Reported by: | Ramiro Morales | Owned by: | Jacob |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Just some notes for stuff in django/trunk/docs
IMHO not worth having separate tickets:
django-admin.txt
, line 360 while describing the "sqlcustom" command it still talks about "sqlinitialdata".
- New
databases.txt
file:
- The "MySQLdb" section still has "If you are trying to use an older version of MySQL, then 1.2.0 *may* work for you."
- Also, this file and
distributions.txt
aren't linked from the main documentation contents nor any other ReST documentation file yet. I don't know if this is on purpose (in that case sorry for the noise) or an overlook.
Attachments (2)
Change History (18)
comment:1 by , 18 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 18 years ago
follow-up: 11 comment:4 by , 18 years ago
I see now
- In #3802 another occurence of "sqlinitaldata" in
docs/diango.admin.txt
was reported, and grepping shows another intutorial01.txt
. Find attached a mini-patch fixing this databases.txt
is linked fromrelease_notes_0.96.txt
so I guess it isn't an orphan documentdistributions.txt
is linked frominstall.txt
so I guess it isn't an orphan document
Sorry for the noise, next time will report as separate tickets and will include patches right from the start.
by , 18 years ago
Attachment: | sqlinitialdata.diff added |
---|
comment:5 by , 18 years ago
The Trac diff parser sees only the hunk in tutorial01.txt
file, see/download the file by using the 'original format' link to get to the hunk in django.admin.txt
by , 18 years ago
Attachment: | sqlinitialdata2.diff added |
---|
New diff with of another s/sqlinitialdata/sqlcustom/ replacement, this time in model-api.txt
comment:7 by , 18 years ago
Has patch: | set |
---|---|
Triage Stage: | Accepted → Ready for checkin |
Looks ready to go. I'm not seeing the issue with OP's request 2a, and I'll let one of the core devs decide about 2b.
follow-up: 9 comment:8 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
follow-up: 10 comment:9 by , 18 years ago
Has patch: | unset |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
Triage Stage: | Ready for checkin → Design decision needed |
comment:10 by , 18 years ago
Replying to Gary Wilson <gary.wilson@gmail.com>:
So is that a no for 2b?
Gary, see comment 4 (http://code.djangoproject.com/ticket/3786#comment:4)
comment:11 by , 18 years ago
Triage Stage: | Design decision needed → Ready for checkin |
---|
Thanks Ramiro...
Replying to Ramiro Morales:
databases.txt
is linked fromrelease_notes_0.96.txt
so I guess it isn't an orphan document
I would say this should be linked to from install.txt in the "Get your database running" section also since the 0.96 release notes won't be current forever.
comment:12 by , 18 years ago
follow-up: 14 comment:13 by , 18 years ago
Triage Stage: | Ready for checkin → Accepted |
---|
It's difficult to work out from all the above comments what remains to be done to close this ticket. It's certainly not "ready for checkin", since it's not clear there's anything needing checking in.
Can somebody who's familiar with the history give a succient summary of what remains to be done and/or decided, please?
comment:14 by , 18 years ago
Replying to mtredinnick:
Can somebody who's familiar with the history give a succient summary of what remains to be done and/or decided, please?
Malcolm, sorry because I'm the responsible of the messy state of this ticket. This is the summary you asked for:
Report | Status | Notes |
Replacement of "sqlinitialdata" occurences with "sqlcustom" | DONE by adrian in [4818] and [5009] | - |
Enhance visibility of the databases.txt file | DONE by Russell in [5009] | - |
Enhance visibility of the distributions.txt file | - | Later I realized it's linked from install.txt so this report could be flagged as bogus if core devs consider it is visible enough
|
The databases.txt contains "If you are trying to use an older version of MySQL, then 1.2.0 *may* work for you." | - | I opened the ticket without knowing the mysql_old backend had been re-added three days before so this report may be flagged as bogus
|
comment:15 by , 18 years ago
comment:16 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Thanks for the summary Ramiro. I've updated the databases.txt file a little to indicate when MySQLdb 1.2.0 may or definitely isn't appropriate. I think having distributions.txt linked from install.txt is sufficient, since it's definitely mentioned in the right place there (as step 1 of the installation process for Django).
I think we can call this closed now. Thanks for paying attention to the little details like this; it's definitely improved things.
As mentioned in #3802, which was marked a duplicate of this, sqlinitialdata is also mentiened in the model-api docs (http://www.djangoproject.com/documentation/model-api).