Tutorial information about Unicode strings in Python, with some markup
adjustments from FLD.

API documentation for Unicode support from C.

those markups!  <with-mixed-feelings>

Added Unicode type to the language reference.

(Mark Hammond.)

B. Hartwell <slt5v@cc.usu.edu>.

Removed second copy of the "See also" section!

in the mimetools documentation.
Suggested by Skip Montanaro <skip@mojam.com>.

his copy of test_contains.py seems to be broken -- the lines he
deleted were already absent).  Checkin messages:


New Unicode support for int(), float(), complex() and long().

- new APIs PyInt_FromUnicode() and PyLong_FromUnicode()
- added support for Unicode to PyFloat_FromString()
- new encoding API PyUnicode_EncodeDecimal() which converts
  Unicode to a decimal char* string (used in the above new
  APIs)
- shortcuts for calls like int(<int object>) and float(<float obj>)
- tests for all of the above

Unicode compares and contains checks:
- comparing Unicode and non-string types now works; TypeErrors
  are masked, all other errors such as ValueError during
  Unicode coercion are passed through (note that PyUnicode_Compare
  does not implement the masking -- PyObject_Compare does this)
- contains now works for non-string types too; TypeErrors are
  masked and 0 returned; all other errors are passed through

Better testing support for the standard codecs.

Misc minor enhancements, such as an alias dbcs for the mbcs codec.

Changes:
- PyLong_FromString() now applies the same error checks as
  does PyInt_FromString(): trailing garbage is reported
  as error and not longer silently ignored. The only characters
  which may be trailing the digits are 'L' and 'l' -- these
  are still silently ignored.
- string.ato?() now directly interface to int(), long() and
  float(). The error strings are now a little different, but
  the type still remains the same. These functions are now
  ready to get declared obsolete ;-)
- PyNumber_Int() now also does a check for embedded NULL chars
  in the input string; PyNumber_Long() already did this (and
  still does)

Followed by:

Looks like I've gone a step too far there... (and test_contains.py
seem to have a bug too).

I've changed back to reporting all errors in PyUnicode_Contains()
and added a few more test cases to test_contains.py (plus corrected
the join() NameError).

Tcl/Tk 8.2 instead of 8.3, because 8.3.0 often crashes on closing a
window.

Added the bitmaps back, and added the wizard style program group
selection dialog.

Got rid of references to backup etc. inserted by the installer wizard
-- we don't use these.

Got rid of conditionals for Windows 3.1, ditto.

Changed version to 1.6a2.

Changed default install directory to "C:\Python16" (not really, but close).

Install only one copy of python16.lib.

Install the two MS DLLs (versioned) and python16.dll (unversioned) in
the system directory.

Install Tcl/Tk and expat in the DLLs directory.

Fixed up descriptions of altzone and timezone not to refer to the
0th meridian, which doesn't exist.  Reference is now to UTC.

Directionality of up/down were confused.

Note in the "Caveats" section should refer to the exit() function, not
exit_thread().

This patch fixes the mmap module on Windows 9x.

Also updates the mmap test to remove the test file.

This patch fixes the mmap module on Windows 9x.

recognize the '7bit' and '8bit' encodings, to simplify use.

(re-written).

<lipman@sphere.niddk.nih.gov>.

This patch solves 2 problems of the os module.
1) Bug ID #50 (case-mismatch wiht "environ.get(..,..)" and "del environ[..]")
2) os.environ.update (dict) doesn't propagate changes to the 'real'
   environment (i.e doesn't call putenv)

This patches also has minor changes specific for 1.6a
The string module isn't used anymore, instead the strings own methods are
used.

The bug is in mmap_read_line_method(), and its loop that searches for
newlines.  After the loop reaches EOF, eol is incremented and points
after the end of the memory.  This results in readline() method
sometimes picking up and returning a byte after the end of the string.
This is usually a bogus \0, but it could cause SIGSEGV if it's after
the end of the page).

The patch fixes the problem.  Also, it uses memchr() for finding a
character, which is in fact the "strnchr" the comment is asking for.
memchr() is already used in Python sources, so there should be no
portability problems.

connect(), and connect_ex().

I didn't make these deprecation notices since it was never a
documented feature.

backwards compatibility, and to avoid a revolution.

Unix From lines, change the UnixMailbox class so that _search_start()
positions the file *before* the Unix From line instead of after it;
change _search_end() to skip one line before looking for the next From
line.  The rfc822.Message class automatically recognizes these Unix
From lines and squirrels them away in the 'unixfrom' instance variable.

  - file_util.py: operations on single files
  - dir_util.py: operations on whole directories or directory trees
  - dep_util.py: simple timestamp-based dependency analysis
  - archive_util.py: creation of archive (tar, zip, ...) files
The functions left in util.py are miscellany that don't fit in any of the
new files.

the Command class from core.py to cmd.py.  No other code needs changing
though; distutils.core still provides the Command and Distribution classes,
although indirectly now.

(Very rough.)

Hopefully I got all this right!

Small cleanups noted by Detlef Lannert
<lannert@lannert.rz.uni-duesseldorf.de>.

Make the spelling of Unicode always uppercase.