traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
35,199 Commits 9 Branches 456 Tags 1.7 GiB
Python 57.8%
C 37.1%
reStructuredText 2.9%
C++ 0.7%
HTML 0.4%
Other 0.7%
Go to file
Brett Cannon 4043001f5d Make str/str8 comparisons return True/False for !=/==. 
Code that has been returning str8 becomes much more apparent thanks to this
(e.g., struct module returning str8 for all string-related formats or sqlite3
passing in str8 instances when converting objects that had a __conform__
method).  One also has to watch out in C code when making a key from char *
using PyString in the C code but a str instance in Python code as that will not
longer compare equal.

Once str8 gains a constructor like the current bytes type then
test_modulefinder needs a cleanup as the fix is a little messy in that file.

Thanks goes to Thomas Lee for writing the patch for the change giving an
initial run-down of why most of the tests were failing.
 		2007-10-22 20:24:51 +00:00
Demo Remove more cruft leftover from nb_coerce. Rename nb_coerce to 2007-09-21 20:19:23 +00:00
Doc Issue 1267, continued. 2007-10-22 00:09:51 +00:00
Grammar Issue #1066: implement PEP 3109, 2/3 of PEP 3134. 2007-08-31 00:04:24 +00:00
Include Issue 1267, continued. 2007-10-22 00:09:51 +00:00
Lib Make str/str8 comparisons return True/False for !=/==. 2007-10-22 20:24:51 +00:00
Mac Merged revisions 58095-58132,58136-58148,58151-58197 via svnmerge from 2007-09-19 03:06:30 +00:00
Misc Make str/str8 comparisons return True/False for !=/==. 2007-10-22 20:24:51 +00:00
Modules Make str/str8 comparisons return True/False for !=/==. 2007-10-22 20:24:51 +00:00
Objects Make str/str8 comparisons return True/False for !=/==. 2007-10-22 20:24:51 +00:00
PC Remove more hotshot cruft. 2007-10-13 18:56:00 +00:00
PCbuild ssue 1309: fix by Christian Heimes to be able to build on Windows. 2007-10-22 16:00:45 +00:00
PCbuild8 Remove more hotshot cruft. 2007-10-13 18:56:00 +00:00
Parser Issue 1267, continued. 2007-10-22 00:09:51 +00:00
Python Issue 1267, continued. 2007-10-22 00:09:51 +00:00
Tools In followup to #1310: Remove more exception indexing. 2007-10-22 16:16:13 +00:00
.hgtags Tagging for release of Python 3.0a1. 2007-08-31 15:07:53 +00:00
INTBENCH Merged the int/long unification branch, by very crude means (sorry Thomas!). 2007-01-14 03:31:43 +00:00
LICENSE Add 2.6 and 3.0 to the silly list. 2007-08-30 17:21:12 +00:00
Makefile.pre.in For PEP3137: Adds missing methods to the mutable PyBytes object (soon 2007-10-16 06:31:30 +00:00
README Fix typo 2007-08-30 17:22:44 +00:00
RELNOTES Minor tweaks. 2007-08-31 00:38:53 +00:00
configure Add macros for checking for long double and defining the size of long double on the platform. Ctypes and Struct module will both need them. 2007-10-12 22:06:37 +00:00
configure.in Add macros for checking for long double and defining the size of long double on the platform. Ctypes and Struct module will both need them. 2007-10-12 22:06:37 +00:00
install-sh Patch #746366: Update to current automake install-sh. Will backport to 2.2. 2003-06-14 06:58:32 +00:00
pyconfig.h.in Add macros for checking for long double and defining the size of long double on the platform. Ctypes and Struct module will both need them. 2007-10-12 22:06:37 +00:00
runtests.sh Unset PYTHONPATH, for my convenience. 2007-08-29 18:15:48 +00:00
setup.py remove hotshot profiler from Py3k 2007-10-11 18:01:43 +00:00

README 

This is Python version 3.0 alpha 1
==================================

For notes specific to this release, see RELNOTES in this directory.

Python 3000 (a.k.a. "Py3k", and released as Python 3.0) is a new
version of the language, which is incompatible with the 2.x line of
releases.  The language is mostly the same, but many details,
especially how built-in objects like dictionaries and strings work,
have changed considerably, and a lot of deprecated features have
finally been removed.

This is an ongoing project; the cleanup isn't expected to be complete
until 2008.  In particular there are plans to reorganize the standard
library namespace.


Release Schedule
----------------

The release plan is to have a series of alpha releases in 2007, beta
releases in 2008, and a final release in August 2008.  The alpha
releases are primarily aimed at developers who want a sneak peek at
the new langauge, especially those folks who plan to port their code
to Python 3000.  The hope is that by the time of the final release,
many 3rd party packages will already be available in a 3.0-compatible
form.


Documentation
-------------

Documentation for Python 3000 is online, updated twice a day:

    http://docs.python.org/dev/3.0/

This is a work in progress; please help improve it!

The design documents for Python 3000 are also online.  While the
reference documentation is being updated, the PEPs are often the best
source of information about new features.  Start by reading PEP 3000:

    http://python.org/dev/peps/pep-3000/


What's New
----------

For an overview of what's new in Python 3000, see Guido van Rossum's
blog at artima.com:

    http://www.artima.com/weblogs/index.jsp?blogger=guido

We'll eventually have a comprehensive overview of the changes in a
"What's New in Python 3.0" document.  Please help write it!


Converting From Python 2.x to 3.0
---------------------------------

Python 2.6 (not yet released) will contain features to help locating
code that needs to be changed, such as optional warnings when
deprecated features are used, and backported versions of certain key
Python 3000 features.

A source-to-source translation tool, "2to3", can take care of the
mundane task of converting large amounts of source code.  It is not a
complete solution but is complemented by the deprecation warnings in
2.6.  This tool is currently available via the Subversion sandbox:

    http://svn.python.org/view/sandbox/trunk/2to3/


Issue Tracker and Mailing List
------------------------------

We're soliciting bug reports about all aspects of the language.  Fixes
are also welcome, preferable in unified diff format.  Please use the
issue tracker:

    http://bugs.python.org/

If you're not sure whether you're dealing with a bug or a feature, use
the mailing list:

    python-3000@python.org

To subscribe to the list, use the mailman form:

    http://mail.python.org/mailman/listinfo/python-3000/


Build Instructions
------------------

On Unix, Linux, BSD, OSX, and Cygwin:

    ./configure
    make
    make test
    sudo make install    # or "make altinstall"

You can pass many options to the configure script; run "./configure
--help" to find out more.  On OSX and Cygwin, the executable is called
python.exe; elsewhere it's just python.

On Mac OS X, if you have configured Python with --enable-framework,
you should use "make frameworkinstall" to do the installation.  Note
that this installs the Python executable in a place that is not
normally on your PATH, you may want to set up a symlink in
/usr/local/bin.

On Windows, see PCbuild/readme.txt.

If you wish, you can create a subdirectory and invoke configure from
there.  For example:

    mkdir debug
    cd debug
    ../configure --with-pydebug
    make
    make test

(This will fail if you *also* built at the top-level directory.  You
should do a "make clean" at the toplevel first.)


Copyright and License Information
---------------------------------

Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007 
Python Software Foundation.
All rights reserved.

Copyright (c) 2000 BeOpen.com.
All rights reserved.

Copyright (c) 1995-2001 Corporation for National Research Initiatives.
All rights reserved.

Copyright (c) 1991-1995 Stichting Mathematisch Centrum.
All rights reserved.

See the file "LICENSE" for information on the history of this
software, terms & conditions for usage, and a DISCLAIMER OF ALL
WARRANTIES.

This Python distribution contains *no* GNU General Public License
(GPL) code, so it may be used in proprietary projects.  There are
interfaces to some GNU code but these are entirely optional.

All trademarks referenced herein are property of their respective
holders.