summaryrefslogtreecommitdiffstats
path: root/Doc
Commit message (Collapse)AuthorAgeFilesLines
* Add Neil's suggestions for avoiding this warningAndrew M. Kuchling2003-02-101-2/+10
|
* C Code:Raymond Hettinger2003-02-091-66/+84
| | | | | | | | | | | | | | | * Removed the ifilter flag wart by splitting it into two simpler functions. * Fixed comment tabbing in C code. * Factored module start-up code into a loop. Documentation: * Re-wrote introduction. * Addede examples for quantifiers. * Simplified python equivalent for islice(). * Documented split of ifilter(). Sets.py: * Replace old ifilter() usage with new.
* Comparison for timedelta, time, date and datetime objects: __eq__ andTim Peters2003-02-071-1/+19
| | | | | | | | | | | | | | | | | __ne__ no longer complain if they don't know how to compare to the other thing. If no meaningful way to compare is known, saying "not equal" is sensible. This allows things like if adatetime in some_sequence: and somedict[adatetime] = whatever to work as expected even if some_sequence contains non-datetime objects, or somedict non-datetime keys, because they only call __eq__. It still complains (raises TypeError) for mixed-type comparisons in contexts that require a total ordering, such as list.sort(), use as a key in a BTree-based data structure, and cmp().
* Update URLAndrew M. Kuchling2003-02-071-1/+1
|
* - make some links into the reference documentation relative forFred Drake2003-02-071-30/+32
| | | | | off-line readers - fix some minor typos and markup errors
* SF bug #681003: itertools issuesRaymond Hettinger2003-02-071-0/+4
| | | | | | | | | | | * Fixed typo in exception message for times() * Filled in missing times_traverse() * Document reasons that imap() did not adopt a None fill-in feature * Document that count(sys.maxint) will wrap-around on overflow * Add overflow test to islice() * Check that starmap()'s argument returns a tuple * Verify that imap()'s tuple re-use is safe * Make a similar tuple re-use (with safety check) for izip()
* Fix SF bug #675259, os.environ leaks under FreeBSD and Mac OS XNeal Norwitz2003-02-071-1/+7
| | | | | | Even with the extra work to cleanup the env, *BSD still leaks. Add a note. Will backport.
* Update doc to reflect code changes for obsoleting use_statcache parameterNeal Norwitz2003-02-061-8/+3
|
* Remove another lie.Michael W. Hudson2003-02-061-4/+2
|
* Correct lie about METH_NOARGS functions.Michael W. Hudson2003-02-061-5/+5
| | | | Backport candidate.
* Typo fixesAndrew M. Kuchling2003-02-061-2/+2
|
* Mention FutureWarning for large intsAndrew M. Kuchling2003-02-061-0/+5
|
* Fix description of filterwarnings() parameters (error noted by Richard Jones atAndrew M. Kuchling2003-02-061-4/+5
| | | | http://mechanicalcat.net/cgi-bin/log/python/turning_warnings_off.html)
* Provide version changed infoNeal Norwitz2003-02-061-0/+1
|
* Updated version of [ 558544 ] cmd.py: add instance-specific stdin/outAnthony Baxter2003-02-061-5/+11
| | | | | | | | | | This patch adds stdin, stdout as optional arguments to the cmd.Cmd constructor (defaulting to sys.stdin, sys.stdout), and changes the Cmd methods throughout to use self.stdout.write() and self.stdin.foo for output and input. This allows much greater flexibility for using cmd - for instance, hooking it into a telnet server. Patch for library module and for documentation.
* Markup fixes; in particular, the tables are now reasonable widthAndrew M. Kuchling2003-02-051-104/+117
|
* supports_unicode_filenames was not in the right location.Fred Drake2003-02-041-7/+8
|
* Update to better reflect the usage of struct_time instances throughout;Fred Drake2003-02-041-24/+28
| | | | | continuing to call these "time tuples" is misleading at best. Closes SF bug #671731; will backport to 2.2.x.
* Twiddle.Fred Drake2003-02-041-1/+2
|
* Bug #678077: Suggest alternative to os.getlogin()Andrew M. Kuchling2003-02-031-1/+3
|
* [Bug #679251] Use correct constant nameAndrew M. Kuchling2003-02-031-6/+6
|
* * Add description of PyInt_FromString.Skip Montanaro2003-02-031-3/+23
| | | | | | * Correct description of PyFloat_FromString. While ignored, the pend argument still has to be given. * Typo in PyLong_FromString.
* Add PyFloat_FromString. Left the char **pend argument out of theSkip Montanaro2003-02-031-0/+5
| | | | | | description since while there, it is useless and ignored, according to Tim's commen. (PyInt_FromString is also not described, but PyLong_FromString is. Is the former deprecated?)
* Move itertools module from the sandbox and into production.Raymond Hettinger2003-02-012-0/+326
|
* Document __module__.Jeremy Hylton2003-01-311-3/+11
|
* Change the treatment of positions returned by PEP293Walter Dörwald2003-01-312-6/+17
| | | | | | | | | | | | | | | | error handers in the Unicode codecs: Negative positions are treated as being relative to the end of the input and out of bounds positions result in an IndexError. Also update the PEP and include an explanation of this in the documentation for codecs.register_error. Fixes a small bug in iconv_codecs: if the position from the callback is negative *add* it to the size instead of substracting it. From SF patch #677429.
* Fix typoRaymond Hettinger2003-01-311-1/+1
|
* SF bug #671447: StringIO doc doesn't say it's sometimes read-only.Raymond Hettinger2003-01-311-0/+5
|
* Fix markup error.Fred Drake2003-01-301-1/+1
|
* Author markup: Andrew got to it firstRaymond Hettinger2003-01-301-1/+0
|
* Make the footer at the end of a \verbatiminput stand out a littleFred Drake2003-01-291-0/+4
| | | | more, to make it easier to tell apart from the verbatim content.
* Move a footnote to the end of the sentence, so the note mark won'tFred Drake2003-01-291-3/+4
| | | | interfere with the flow of the sentence.
* More markup changes for consistency.Fred Drake2003-01-281-14/+14
|
* Various minor markup adjustments.Fred Drake2003-01-281-16/+25
|
* Added missing dependency.Fred Drake2003-01-281-0/+1
|
* Update register exampleAndrew M. Kuchling2003-01-271-10/+16
|
* Adjust some of Skip's latest changes slightly; these really are thingsFred Drake2003-01-271-5/+13
| | | | that should stand out.
* Make the "notice" environments somewhat similar, with less differenceFred Drake2003-01-271-1/+11
| | | | between the "note" and "warning" flavors.
* * add \versionadded{} strings as appropriateSkip Montanaro2003-01-271-5/+23
| | | | | | * remove doc for defunct IllegalKeywordArgument exception * add note that HTTP class is for backward compatibility and refer reader to online docstrings for help
* Fix minor typos.Raymond Hettinger2003-01-251-6/+6
|
* SF #638299, LaTeX documentation for logging packageNeal Norwitz2003-01-251-884/+846
| | | | | | Replace existing doc with new version from Vinay. Fixed markup and wrapped long lines from patch. Needs review.
* Fix markupNeal Norwitz2003-01-251-1/+1
|
* Include version annotation for PyObject_Call().Fred Drake2003-01-251-0/+1
|
* Fix typo reported to python-docs.Fred Drake2003-01-251-1/+1
|
* date and datetime comparison: when we don't know how toTim Peters2003-01-241-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | compare against "the other" argument, we raise TypeError, in order to prevent comparison from falling back to the default (and worse than useless, in this case) comparison by object address. That's fine so far as it goes, but leaves no way for another date/datetime object to make itself comparable to our objects. For example, it leaves Marc-Andre no way to teach mxDateTime dates how to compare against Python dates. Discussion on Python-Dev raised a number of impractical ideas, and the simple one implemented here: when we don't know how to compare against "the other" argument, we raise TypeError *unless* the other object has a timetuple attr. In that case, we return NotImplemented instead, and Python will give the other object a shot at handling the comparison then. Note that comparisons of time and timedelta objects still suffer the original problem, though.
* Fred drives and fixes a formatting nit.Barry Warsaw2003-01-241-2/+2
|
* SF bug 660872: datetimetz constructors behave counterintuitively (2.3a1).Tim Peters2003-01-231-10/+19
| | | | | | This gives much the same treatment to datetime.fromtimestamp(stamp, tz) as the last batch of checkins gave to datetime.now(tz): do "the obvious" thing with the tz argument instead of a senseless thing.
* Reimplemented datetime.now() to be useful.Tim Peters2003-01-231-8/+14
|
* "Premature" doc changes, for new astimezone() rules, and the newTim Peters2003-01-222-57/+161
| | | | | | | | | tzinfo.fromutc() method. The C code doesn't implement any of this yet (well, not the C code on the machine I'm using now), nor does the test suite reflect it. The Python datetime.py implementation and test suite in the sandbox do match these doc changes. The C implementation probably won't catch up before Thursday (Wednesday is a scheduled "black hole" day this week <0.4 wink>).
* SF bug 671779: Error in tzinfo.dst() docsTim Peters2003-01-211-2/+2
| | | | tzinfo dst() should return timedelta(0) if DST is not effect, not 0.
generated by cgit v0.12 at 2024-11-16 18:54:34 (GMT)