Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
40083373
Commit
40083373
authored
Sep 29, 2012
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bump version to 3.4.0 alpha 0.
parent
d31e544f
Changes
35
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
35 changed files
with
908 additions
and
1005 deletions
+908
-1005
Doc/license.rst
Doc/license.rst
+2
-0
Doc/tutorial/interpreter.rst
Doc/tutorial/interpreter.rst
+7
-7
Doc/tutorial/stdlib.rst
Doc/tutorial/stdlib.rst
+1
-1
Doc/tutorial/stdlib2.rst
Doc/tutorial/stdlib2.rst
+1
-1
Include/patchlevel.h
Include/patchlevel.h
+3
-3
LICENSE
LICENSE
+1
-0
Lib/distutils/__init__.py
Lib/distutils/__init__.py
+1
-1
Lib/idlelib/idlever.py
Lib/idlelib/idlever.py
+1
-1
Misc/NEWS
Misc/NEWS
+3
-103
Misc/RPM/python-3.4.spec
Misc/RPM/python-3.4.spec
+2
-2
PC/VC6/pythoncore.dsp
PC/VC6/pythoncore.dsp
+2
-2
PC/VC6/readme.txt
PC/VC6/readme.txt
+2
-2
PC/VS7.1/pythoncore.vcproj
PC/VS7.1/pythoncore.vcproj
+12
-12
PC/VS7.1/readme.txt
PC/VS7.1/readme.txt
+2
-2
PC/VS8.0/build_ssl.bat
PC/VS8.0/build_ssl.bat
+2
-2
PC/VS8.0/kill_python.c
PC/VS8.0/kill_python.c
+1
-1
PC/VS8.0/pyproject.vsprops
PC/VS8.0/pyproject.vsprops
+1
-1
PC/VS9.0/kill_python.c
PC/VS9.0/kill_python.c
+1
-1
PC/VS9.0/pyproject.vsprops
PC/VS9.0/pyproject.vsprops
+1
-1
PC/example_nt/example.vcproj
PC/example_nt/example.vcproj
+2
-2
PC/os2emx/Makefile
PC/os2emx/Makefile
+1
-1
PC/os2emx/README.os2emx
PC/os2emx/README.os2emx
+1
-1
PC/os2emx/python34.def
PC/os2emx/python34.def
+125
-125
PC/pyconfig.h
PC/pyconfig.h
+2
-2
PC/python3.def
PC/python3.def
+697
-697
PC/python3.mak
PC/python3.mak
+5
-5
PC/python34gen.py
PC/python34gen.py
+4
-4
PC/python34stub.def
PC/python34stub.def
+1
-1
PCbuild/build_ssl.bat
PCbuild/build_ssl.bat
+2
-2
PCbuild/kill_python.c
PCbuild/kill_python.c
+1
-1
PCbuild/pyproject.props
PCbuild/pyproject.props
+1
-1
PCbuild/readme.txt
PCbuild/readme.txt
+1
-1
README
README
+8
-8
configure
configure
+10
-10
configure.ac
configure.ac
+1
-1
No files found.
Doc/license.rst
View file @
40083373
...
...
@@ -122,6 +122,8 @@ been GPL-compatible; the table below summarizes the various releases.
+----------------+--------------+------------+------------+-----------------+
| 3.3.0 | 3.2 | 2012 | PSF | yes |
+----------------+--------------+------------+------------+-----------------+
| 3.4.0 | 3.3.0 | 2014 | PSF | yes |
+----------------+--------------+------------+------------+-----------------+
.. note::
...
...
Doc/tutorial/interpreter.rst
View file @
40083373
...
...
@@ -10,13 +10,13 @@ Using the Python Interpreter
Invoking the Interpreter
========================
The Python interpreter is usually installed as :file:`/usr/local/bin/python3.
3
`
The Python interpreter is usually installed as :file:`/usr/local/bin/python3.
4
`
on those machines where it is available; putting :file:`/usr/local/bin` in your
Unix shell's search path makes it possible to start it by typing the command:
.. code-block:: text
python3.
3
python3.
4
to the shell. [#]_ Since the choice of the directory where the interpreter lives
is an installation option, other places are possible; check with your local
...
...
@@ -24,11 +24,11 @@ Python guru or system administrator. (E.g., :file:`/usr/local/python` is a
popular alternative location.)
On Windows machines, the Python installation is usually placed in
:file:`C:\\Python3
3
`, though you can change this when you're running the
:file:`C:\\Python3
4
`, though you can change this when you're running the
installer. To add this directory to your path, you can type the following
command into the command prompt in a DOS box::
set path=%path%;C:\python3
3
set path=%path%;C:\python3
4
Typing an end-of-file character (:kbd:`Control-D` on Unix, :kbd:`Control-Z` on
Windows) at the primary prompt causes the interpreter to exit with a zero exit
...
...
@@ -95,8 +95,8 @@ with the *secondary prompt*, by default three dots (``...``). The interpreter
prints a welcome message stating its version number and a copyright notice
before printing the first prompt::
$ python3.
3
Python 3.
3
(default, Sep 24 2012, 09:25:04)
$ python3.
4
Python 3.
4
(default, Sep 24 2012, 09:25:04)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
...
...
@@ -149,7 +149,7 @@ Executable Python Scripts
On BSD'ish Unix systems, Python scripts can be made directly executable, like
shell scripts, by putting the line ::
#! /usr/bin/env python3.
3
#! /usr/bin/env python3.
4
(assuming that the interpreter is on the user's :envvar:`PATH`) at the beginning
of the script and giving the file an executable mode. The ``#!`` must be the
...
...
Doc/tutorial/stdlib.rst
View file @
40083373
...
...
@@ -15,7 +15,7 @@ operating system::
>>> import os
>>> os.getcwd() # Return the current working directory
'C:\\Python3
3
'
'C:\\Python3
4
'
>>> os.chdir('/server/accesslogs') # Change current working directory
>>> os.system('mkdir today') # Run the command mkdir in the system shell
0
...
...
Doc/tutorial/stdlib2.rst
View file @
40083373
...
...
@@ -275,7 +275,7 @@ applications include caching objects that are expensive to create::
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
d['primary'] # entry was automatically removed
File "C:/python3
3
/lib/weakref.py", line 46, in __getitem__
File "C:/python3
4
/lib/weakref.py", line 46, in __getitem__
o = self.data[key]()
KeyError: 'primary'
...
...
Include/patchlevel.h
View file @
40083373
...
...
@@ -17,13 +17,13 @@
/* Version parsed out into numeric values */
/*--start constants--*/
#define PY_MAJOR_VERSION 3
#define PY_MINOR_VERSION
3
#define PY_MINOR_VERSION
4
#define PY_MICRO_VERSION 0
#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_
FINAL
#define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_
ALPHA
#define PY_RELEASE_SERIAL 0
/* Version as a string */
#define PY_VERSION "3.
3.
0"
#define PY_VERSION "3.
4.0a
0"
/*--end constants--*/
/* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2.
...
...
LICENSE
View file @
40083373
...
...
@@ -75,6 +75,7 @@ the various releases.
3.2.2 3.2.1 2011 PSF yes
3.2.3 3.2.2 2012 PSF yes
3.3.0 3.2 2012 PSF yes
3.4.0 3.3.0 2014 PSF yes
Footnotes:
...
...
Lib/distutils/__init__.py
View file @
40083373
...
...
@@ -13,5 +13,5 @@ used from a setup script as
# Updated automatically by the Python release process.
#
#--start constants--
__version__
=
"3.
3.
0"
__version__
=
"3.
4.0a
0"
#--end constants--
Lib/idlelib/idlever.py
View file @
40083373
IDLE_VERSION
=
"3.
3.
0"
IDLE_VERSION
=
"3.
4.0a
0"
Misc/NEWS
View file @
40083373
...
...
@@ -2,120 +2,20 @@
Python
News
+++++++++++
What
's New in Python 3.
3.
1?
===========================
What
's New in Python 3.
4.0 Alpha
1?
===========================
========
*Rel
ease date: XX-XX-XXXX
*
*Rel
ase date: XX-XXX-2014
*
Core and Builtins
-----------------
- Issue #15379: Fix passing of non-BMP characters as integers for the charmap
decoder (already working as unicode strings). Patch by Serhiy Storchaka.
- Issue #15144: Fix possible integer overflow when handling pointers as
integer values, by using Py_uintptr_t instead of size_t. Patch by
Serhiy Storchaka.
- Issue #15965: Explicitly cast AT_FDCWD as (int). Required on Solaris 10
(which defines AT_FDCWD as 0xffd19553), harmless on other platforms.
- Issue #15839: Convert SystemErrors in super() to RuntimeErrors.
- Issue #15846: Fix SystemError which happened when using ast.parse in an
exception handler on code with syntax errors.
- Issue #15801: Make sure mappings passed to '
%
' formatting are actually
subscriptable.
Library
-------
- Issue #15323: improve failure message of Mock.assert_called_once_with
- Issue #16064: unittest -m claims executable is "python", not "python3"
- Issue #12376: Pass on parameters in TextTestResult.__init__ super call
- Issue #15222: Insert blank line after each message in mbox mailboxes
- Issue #16013: Fix CSV Reader parsing issue with ending quote characters.
Patch by Serhiy Storchaka.
- Issue #15421: Fix an OverflowError in Calendar.itermonthdates() after
datetime.MAXYEAR. Patch by Cédric Krier.
- Issue #15970: xml.etree.ElementTree now serializes correctly the empty HTML
elements '
meta
' and '
param
'.
- Issue #15842: The SocketIO.{readable,writable,seekable} methods now
raise ValueError when the file-like object is closed. Patch by Alessandro
Moura.
- Issue #15876: Fix a refleak in the curses module: window.encoding.
- Issue #15881: Fixed atexit hook in multiprocessing. Original patch
by Chris McDonough.
- Issue #15340: Fix importing the random module when /dev/urandom cannot
be opened. This was a regression caused by the hash randomization patch.
- Issue #15841: The readable(), writable() and seekable() methods of BytesIO
and StringIO objects now raise ValueError when the object has been closed.
Patch by Alessandro Moura.
- Issue #15447: Use subprocess.DEVNULL in webbrowser, instead of opening
os.devnull explicitly and leaving it open.
- Issue #15509: webbrowser.UnixBrowser no longer passes empty arguments to
Popen when %action substitutions produce empty strings.
- Issue #12776,#11839: call argparse type function (specified by add_argument)
only once. Before, the type function was called twice in the case where the
default was specified and the argument was given as well. This was
especially problematic for the FileType type, as a default file would always
be opened, even if a file argument was specified on the command line.
- Issue #15906: Fix a regression in argparse caused by the preceding change,
when action='
append
', type='
str
' and default=[].
Extension Modules
-----------------
Tests
-----
- Issue #15304: Fix warning message when os.chdir() fails inside
test.support.temp_cwd(). Patch by Chris Jerdonek.
- Issue #15802: Fix test logic in TestMaildir.test_create_tmp. Patch
by Serhiy Storchaka.
- Issue #15557: Added a test suite for the webbrowser module, thanks
to Anton Barkovsky.
Build
-----
- Issue #15819: Make sure we can build Python out-of-tree from a readonly
source directory. (Somewhat related to Issue #9860.)
Documentation
-------------
- Issue #16036: Improve documentation of built-in int()'
s
signature
and
arguments
.
-
Issue
#
15935
:
Clarification
of
argparse
docs
,
re
:
add_argument
()
type
and
default
arguments
.
Patch
contributed
by
Chris
Jerdonek
.
-
Issue
#
11964
:
Document
a
change
in
v3
.2
to
the
behavior
of
the
indent
parameter
of
json
encoding
operations
.
Tools
/
Demos
-----------
What'
s
New
in
Python
3.3.0
?
===========================
...
...
Misc/RPM/python-3.4.spec
View file @
40083373
...
...
@@ -39,8 +39,8 @@
%define name python
#--start constants--
%define version 3.
3.
0
%define libvers 3.
3
%define version 3.
4.0a
0
%define libvers 3.
4
#--end constants--
%define release 1pydotorg
%define __prefix /usr
...
...
PC/VC6/pythoncore.dsp
View file @
40083373
...
...
@@ -54,7 +54,7 @@ BSC32=bscmake.exe
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /dll /machine:I386
# ADD LINK32 largeint.lib kernel32.lib user32.lib advapi32.lib shell32.lib /nologo /base:"0x1e000000" /subsystem:windows /dll /debug /machine:I386 /nodefaultlib:"libc" /out:"./python3
3
.dll"
# ADD LINK32 largeint.lib kernel32.lib user32.lib advapi32.lib shell32.lib /nologo /base:"0x1e000000" /subsystem:windows /dll /debug /machine:I386 /nodefaultlib:"libc" /out:"./python3
4
.dll"
# SUBTRACT LINK32 /pdb:none
!ELSEIF "$(CFG)" == "pythoncore - Win32 Debug"
...
...
@@ -82,7 +82,7 @@ BSC32=bscmake.exe
# ADD BSC32 /nologo
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /dll /debug /machine:I386 /pdbtype:sept
# ADD LINK32 largeint.lib kernel32.lib user32.lib advapi32.lib shell32.lib /nologo /base:"0x1e000000" /subsystem:windows /dll /debug /machine:I386 /nodefaultlib:"libc" /out:"./python3
3
_d.dll" /pdbtype:sept
# ADD LINK32 largeint.lib kernel32.lib user32.lib advapi32.lib shell32.lib /nologo /base:"0x1e000000" /subsystem:windows /dll /debug /machine:I386 /nodefaultlib:"libc" /out:"./python3
4
_d.dll" /pdbtype:sept
# SUBTRACT LINK32 /pdb:none
!ENDIF
...
...
PC/VC6/readme.txt
View file @
40083373
...
...
@@ -12,7 +12,7 @@ and build the projects.
The proper order to build subprojects:
1) pythoncore (this builds the main Python DLL and library files,
python3
3
.{dll, lib} in Release mode)
python3
4
.{dll, lib} in Release mode)
2) python (this builds the main Python executable,
python.exe in Release mode)
...
...
@@ -23,7 +23,7 @@ The proper order to build subprojects:
to the subsystems they implement; see SUBPROJECTS below)
When using the Debug setting, the output files have a _d added to
their name: python3
3
_d.dll, python_d.exe, pyexpat_d.pyd, and so on.
their name: python3
4
_d.dll, python_d.exe, pyexpat_d.pyd, and so on.
SUBPROJECTS
-----------
...
...
PC/VS7.1/pythoncore.vcproj
View file @
40083373
...
...
@@ -39,15 +39,15 @@
<Tool
Name=
"VCLinkerTool"
AdditionalDependencies=
"getbuildinfo.o"
OutputFile=
"./python3
3
.dll"
OutputFile=
"./python3
4
.dll"
LinkIncremental=
"1"
SuppressStartupBanner=
"TRUE"
IgnoreDefaultLibraryNames=
"libc"
GenerateDebugInformation=
"TRUE"
ProgramDatabaseFile=
".\./python3
3
.pdb"
ProgramDatabaseFile=
".\./python3
4
.pdb"
SubSystem=
"2"
BaseAddress=
"0x1e000000"
ImportLibrary=
".\./python3
3
.lib"
ImportLibrary=
".\./python3
4
.lib"
TargetMachine=
"1"
/>
<Tool
Name=
"VCMIDLTool"
/>
...
...
@@ -99,15 +99,15 @@
<Tool
Name=
"VCLinkerTool"
AdditionalDependencies=
"getbuildinfo.o"
OutputFile=
"./python3
3
_d.dll"
OutputFile=
"./python3
4
_d.dll"
LinkIncremental=
"1"
SuppressStartupBanner=
"TRUE"
IgnoreDefaultLibraryNames=
"libc"
GenerateDebugInformation=
"TRUE"
ProgramDatabaseFile=
".\./python3
3
_d.pdb"
ProgramDatabaseFile=
".\./python3
4
_d.pdb"
SubSystem=
"2"
BaseAddress=
"0x1e000000"
ImportLibrary=
".\./python3
3
_d.lib"
ImportLibrary=
".\./python3
4
_d.lib"
TargetMachine=
"1"
/>
<Tool
Name=
"VCMIDLTool"
/>
...
...
@@ -166,15 +166,15 @@
Name=
"VCLinkerTool"
AdditionalOptions=
" /MACHINE:IA64 /USELINK:MS_SDK"
AdditionalDependencies=
"getbuildinfo.o"
OutputFile=
"./python3
3
.dll"
OutputFile=
"./python3
4
.dll"
LinkIncremental=
"1"
SuppressStartupBanner=
"FALSE"
IgnoreDefaultLibraryNames=
"libc"
GenerateDebugInformation=
"TRUE"
ProgramDatabaseFile=
".\./python3
3
.pdb"
ProgramDatabaseFile=
".\./python3
4
.pdb"
SubSystem=
"2"
BaseAddress=
"0x1e000000"
ImportLibrary=
".\./python3
3
.lib"
ImportLibrary=
".\./python3
4
.lib"
TargetMachine=
"0"
/>
<Tool
Name=
"VCMIDLTool"
/>
...
...
@@ -233,15 +233,15 @@
Name=
"VCLinkerTool"
AdditionalOptions=
" /MACHINE:AMD64 /USELINK:MS_SDK"
AdditionalDependencies=
"getbuildinfo.o"
OutputFile=
"./python3
3
.dll"
OutputFile=
"./python3
4
.dll"
LinkIncremental=
"1"
SuppressStartupBanner=
"TRUE"
IgnoreDefaultLibraryNames=
"libc"
GenerateDebugInformation=
"TRUE"
ProgramDatabaseFile=
".\./python3
3
.pdb"
ProgramDatabaseFile=
".\./python3
4
.pdb"
SubSystem=
"2"
BaseAddress=
"0x1e000000"
ImportLibrary=
".\./python3
3
.lib"
ImportLibrary=
".\./python3
4
.lib"
TargetMachine=
"0"
/>
<Tool
Name=
"VCMIDLTool"
/>
...
...
PC/VS7.1/readme.txt
View file @
40083373
...
...
@@ -12,7 +12,7 @@ the "Standard" toolbar"), and build the projects.
The proper order to build subprojects:
1) pythoncore (this builds the main Python DLL and library files,
python3
3
.{dll, lib} in Release mode)
python3
4
.{dll, lib} in Release mode)
NOTE: in previous releases, this subproject was
named after the release number, e.g. python20.
...
...
@@ -26,7 +26,7 @@ The proper order to build subprojects:
test slave; see SUBPROJECTS below)
When using the Debug setting, the output files have a _d added to
their name: python3
3
_d.dll, python_d.exe, parser_d.pyd, and so on.
their name: python3
4
_d.dll, python_d.exe, parser_d.pyd, and so on.
SUBPROJECTS
-----------
...
...
PC/VS8.0/build_ssl.bat
View file @
40083373
...
...
@@ -2,10 +2,10 @@
if
not
defined
HOST_PYTHON
(
if
%
1
EQU
Debug
(
set
HOST_PYTHON
=
python_d
.exe
if
not
exist
python3
3
_d
.dll
exit
1
if
not
exist
python3
4
_d
.dll
exit
1
)
ELSE
(
set
HOST_PYTHON
=
python
.exe
if
not
exist
python3
3
.dll
exit
1
if
not
exist
python3
4
.dll
exit
1
)
)
%HOST_PYTHON%
build_ssl
.py
%
1
%
2
%
3
...
...
PC/VS8.0/kill_python.c
View file @
40083373
...
...
@@ -106,7 +106,7 @@ main(int argc, char **argv)
/*
* XXX TODO: if we really wanted to be fancy, we could check the
* modules for all processes (not just the python[_d].exe ones)
* and see if any of our DLLs are loaded (i.e. python3
3
[_d].dll),
* and see if any of our DLLs are loaded (i.e. python3
4
[_d].dll),
* as that would also inhibit our ability to rebuild the solution.
* Not worth loosing sleep over though; for now, a simple check
* for just the python executable should be sufficient.
...
...
PC/VS8.0/pyproject.vsprops
View file @
40083373
...
...
@@ -38,7 +38,7 @@
/>
<UserMacro
Name=
"PyDllName"
Value=
"python3
3
"
Value=
"python3
4
"
/>
<UserMacro
Name=
"PythonExe"
...
...
PC/VS9.0/kill_python.c
View file @
40083373
...
...
@@ -106,7 +106,7 @@ main(int argc, char **argv)
/*
* XXX TODO: if we really wanted to be fancy, we could check the
* modules for all processes (not just the python[_d].exe ones)
* and see if any of our DLLs are loaded (i.e. python3
3
[_d].dll),
* and see if any of our DLLs are loaded (i.e. python3
4
[_d].dll),
* as that would also inhibit our ability to rebuild the solution.
* Not worth loosing sleep over though; for now, a simple check
* for just the python executable should be sufficient.
...
...
PC/VS9.0/pyproject.vsprops
View file @
40083373
...
...
@@ -38,7 +38,7 @@
/>
<UserMacro
Name=
"PyDllName"
Value=
"python3
3
"
Value=
"python3
4
"
/>
<UserMacro
Name=
"PythonExe"
...
...
PC/example_nt/example.vcproj
View file @
40083373
...
...
@@ -39,7 +39,7 @@
<Tool
Name=
"VCLinkerTool"
AdditionalOptions=
"/export:initexample"
AdditionalDependencies=
"odbc32.lib odbccp32.lib python3
3
.lib"
AdditionalDependencies=
"odbc32.lib odbccp32.lib python3
4
.lib"
OutputFile=
".\Release/example.pyd"
LinkIncremental=
"1"
SuppressStartupBanner=
"TRUE"
...
...
@@ -105,7 +105,7 @@
<Tool
Name=
"VCLinkerTool"
AdditionalOptions=
"/export:initexample"
AdditionalDependencies=
"odbc32.lib odbccp32.lib python3
3
_d.lib"
AdditionalDependencies=
"odbc32.lib odbccp32.lib python3
4
_d.lib"
OutputFile=
".\Debug/example_d.pyd"
LinkIncremental=
"1"
SuppressStartupBanner=
"TRUE"
...
...
PC/os2emx/Makefile
View file @
40083373
...
...
@@ -237,7 +237,7 @@ $(OUT)%$O: %.c
# Output file names
PYTHON_VER
=
2.6
PYTHON_LIB
=
python3
3
PYTHON_LIB
=
python3
4
PYTHON.LIB
=
$(PYTHON_LIB)
_s
$A
PYTHON.IMPLIB
=
$(PYTHON_LIB)$A
ifeq
($(EXEOMF),yes)
...
...
PC/os2emx/README.os2emx
View file @
40083373
...
...
@@ -305,7 +305,7 @@ Procedure
to be installed in a directory other than the PYTHONHOME directory, set
the value of the Makefile variable EXE_DIR to the appropriate directory.
3. If you wish the Python core DLL (python3
3
.dll) to be installed in a
3. If you wish the Python core DLL (python3
4
.dll) to be installed in a
directory other than the directory in which the Python executables are
installed (by default, the PYTHONHOME directory), set the value of the
Makefile variable DLL_DIR to the appropriate directory. This DLL must
...
...
PC/os2emx/python3
3
.def
→
PC/os2emx/python3
4
.def
View file @
40083373
This diff is collapsed.
Click to expand it.
PC/pyconfig.h
View file @
40083373
...
...
@@ -324,11 +324,11 @@ Py_NO_ENABLE_SHARED to find out. Also support MS_NO_COREDLL for b/w compat */
their Makefile (other compilers are generally
taken care of by distutils.) */
# if defined(_DEBUG)
# pragma comment(lib,"python3
3
_d.lib")
# pragma comment(lib,"python3
4
_d.lib")
# elif defined(Py_LIMITED_API)
# pragma comment(lib,"python3.lib")
# else
# pragma comment(lib,"python3
3
.lib")
# pragma comment(lib,"python3
4
.lib")
# endif
/* _DEBUG */
# endif
/* _MSC_VER */
# endif
/* Py_BUILD_CORE */
...
...
PC/python3.def
View file @
40083373
This diff is collapsed.
Click to expand it.
PC/python3.mak
View file @
40083373
$(OutDir)python3.dll
:
python3.def $(OutDir)python3
3
stub.lib
cl /LD /Fe
$(OutDir)
python3.dll python3dll.c python3.def
$(OutDir)
python3
3
stub.lib
$(OutDir)python3.dll
:
python3.def $(OutDir)python3
4
stub.lib
cl /LD /Fe
$(OutDir)
python3.dll python3dll.c python3.def
$(OutDir)
python3
4
stub.lib
$(OutDir)python3
3stub.lib
:
python33
stub.def
lib /def:python3
3stub.def /out:
$(OutDir)
python33
stub.lib /MACHINE:
$(MACHINE)
$(OutDir)python3
4stub.lib
:
python34
stub.def
lib /def:python3
4stub.def /out:
$(OutDir)
python34
stub.lib /MACHINE:
$(MACHINE)
clean
:
del
$(OutDir)
python3.dll
$(OutDir)
python3.lib
$(OutDir)
python3
3stub.lib
$(OutDir)
python3.exp
$(OutDir)
python33
stub.exp
del
$(OutDir)
python3.dll
$(OutDir)
python3.lib
$(OutDir)
python3
4stub.lib
$(OutDir)
python3.exp
$(OutDir)
python34
stub.exp
rebuild
:
clean $(OutDir)python3.dll
PC/python3
3
gen.py
→
PC/python3
4
gen.py
View file @
40083373
# Generate python3
3
stub.def out of python3.def
# Generate python3
4
stub.def out of python3.def
# The regular import library cannot be used,
# since it doesn't provide the right symbols for
# data forwarding
out
=
open
(
"python3
3
stub.def"
,
"w"
)
out
.
write
(
'LIBRARY "python3
3
"
\
n
'
)
out
=
open
(
"python3
4
stub.def"
,
"w"
)
out
.
write
(
'LIBRARY "python3
4
"
\
n
'
)
out
.
write
(
'EXPORTS
\
n
'
)
inp
=
open
(
"python3.def"
)
...
...
@@ -14,7 +14,7 @@ line = inp.readline() # LIBRARY
assert
line
.
strip
()
==
'EXPORTS'
for
line
in
inp
:
# SYM1=python3
3
.SYM2[ DATA]
# SYM1=python3
4
.SYM2[ DATA]
head
,
tail
=
line
.
split
(
'.'
)
if
'DATA'
in
tail
:
symbol
,
tail
=
tail
.
split
(
' '
)
...
...
PC/python3
3
stub.def
→
PC/python3
4
stub.def
View file @
40083373
LIBRARY "python3
3
"
LIBRARY "python3
4
"
EXPORTS
PyArg_Parse
PyArg_ParseTuple
...
...
PCbuild/build_ssl.bat
View file @
40083373
...
...
@@ -2,10 +2,10 @@
if
not
defined
HOST_PYTHON
(
if
%
1
EQU
Debug
(
set
HOST_PYTHON
=
python_d
.exe
if
not
exist
python3
3
_d
.dll
exit
1
if
not
exist
python3
4
_d
.dll
exit
1
)
ELSE
(
set
HOST_PYTHON
=
python
.exe
if
not
exist
python3
3
.dll
exit
1
if
not
exist
python3
4
.dll
exit
1
)
)
%HOST_PYTHON%
build_ssl
.py
%
1
%
2
%
3
...
...
PCbuild/kill_python.c
View file @
40083373
...
...
@@ -106,7 +106,7 @@ main(int argc, char **argv)
/*
* XXX TODO: if we really wanted to be fancy, we could check the
* modules for all processes (not just the python[_d].exe ones)
* and see if any of our DLLs are loaded (i.e. python3
3
[_d].dll),
* and see if any of our DLLs are loaded (i.e. python3
4
[_d].dll),
* as that would also inhibit our ability to rebuild the solution.
* Not worth loosing sleep over though; for now, a simple check
* for just the python executable should be sufficient.
...
...
PCbuild/pyproject.props
View file @
40083373
...
...
@@ -13,7 +13,7 @@
<IntDir>
$(SolutionDir)$(PlatformName)-temp-$(Configuration)\$(ProjectName)\
</IntDir>
</PropertyGroup>
<PropertyGroup
Label=
"UserMacros"
>
<PyDllName>
python3
3
$(PyDebugExt)
</PyDllName>
<PyDllName>
python3
4
$(PyDebugExt)
</PyDllName>
<PythonExe>
$(OutDir)python$(PyDebugExt).exe
</PythonExe>
<KillPythonExe>
$(OutDir)kill_python$(PyDebugExt).exe
</KillPythonExe>
<externalsDir>
..\..
</externalsDir>
...
...
PCbuild/readme.txt
View file @
40083373
...
...
@@ -37,7 +37,7 @@ NOTE:
running a Python core buildbot test slave; see SUBPROJECTS below)
When using the Debug setting, the output files have a _d added to
their name: python3
3
_d.dll, python_d.exe, parser_d.pyd, and so on. Both
their name: python3
4
_d.dll, python_d.exe, parser_d.pyd, and so on. Both
the build and rt batch files accept a -d option for debug builds.
The 32bit builds end up in the solution folder PCbuild while the x64 builds
...
...
README
View file @
40083373
This is Python version 3.
3.0
============================
This is Python version 3.
4.0 prerelease
============================
===========
Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011,
2012 Python Software Foundation. All rights reserved.
...
...
@@ -52,9 +52,9 @@ What's New
----------
We try to have a comprehensive overview of the changes in the "What's New in
Python 3.
3
" document, found at
Python 3.
4
" document, found at
http://docs.python.org/3.
3/whatsnew/3.3
.html
http://docs.python.org/3.
4/whatsnew/3.4
.html
For a more detailed change log, read Misc/NEWS (though this file, too, is
incomplete, and also doesn't list anything merged in from the 2.7 release under
...
...
@@ -67,9 +67,9 @@ entitled "Installing multiple versions".
Documentation
-------------
Documentation for Python 3.
3
is online, updated daily:
Documentation for Python 3.
4
is online, updated daily:
http://docs.python.org/3.
3
/
http://docs.python.org/3.
4
/
It can also be downloaded in many formats for faster access. The documentation
is downloadable in HTML, PDF, and reStructuredText formats; the latter version
...
...
@@ -87,7 +87,7 @@ backported versions of certain key Python 3.x 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. See
http://docs.python.org/3.
3
/library/2to3.html for more information.
http://docs.python.org/3.
4
/library/2to3.html for more information.
Testing
...
...
@@ -125,7 +125,7 @@ same prefix you must decide which version (if any) is your "primary" version.
Install that version using "make install". Install all other versions using
"make altinstall".
For example, if you want to install Python 2.6, 2.7 and 3.
3
with 2.7 being the
For example, if you want to install Python 2.6, 2.7 and 3.
4
with 2.7 being the
primary version, you would execute "make install" in your 2.7 build directory
and "make altinstall" in the others.
...
...
configure
View file @
40083373
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.68 for python 3.
3
.
# Generated by GNU Autoconf 2.68 for python 3.
4
.
#
# Report bugs to <http://bugs.python.org/>.
#
...
...
@@ -560,8 +560,8 @@ MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME
=
'python'
PACKAGE_TARNAME
=
'python'
PACKAGE_VERSION
=
'3.
3
'
PACKAGE_STRING
=
'python 3.
3
'
PACKAGE_VERSION
=
'3.
4
'
PACKAGE_STRING
=
'python 3.
4
'
PACKAGE_BUGREPORT
=
'http://bugs.python.org/'
PACKAGE_URL
=
''
...
...
@@ -1336,7 +1336,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat
<<
_ACEOF
\`
configure' configures python 3.
3
to adapt to many kinds of systems.
\`
configure' configures python 3.
4
to adapt to many kinds of systems.
Usage:
$0
[OPTION]... [VAR=VALUE]...
...
...
@@ -1401,7 +1401,7 @@ fi
if
test
-n
"
$ac_init_help
"
;
then
case
$ac_init_help
in
short
|
recursive
)
echo
"Configuration of python 3.
3
:"
;;
short
|
recursive
)
echo
"Configuration of python 3.
4
:"
;;
esac
cat
<<
\
_ACEOF
...
...
@@ -1539,7 +1539,7 @@ fi
test
-n
"
$ac_init_help
"
&&
exit
$ac_status
if
$ac_init_version
;
then
cat
<<
\
_ACEOF
python configure 3.
3
python configure 3.
4
generated by GNU Autoconf 2.68
Copyright (C) 2010 Free Software Foundation, Inc.
...
...
@@ -2370,7 +2370,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by python
$as_me
3.
3
, which was
It was created by python
$as_me
3.
4
, which was
generated by GNU Autoconf 2.68. Invocation command line was
$ $0
$@
...
...
@@ -2920,7 +2920,7 @@ rm confdefs.h
mv
confdefs.h.new confdefs.h
VERSION
=
3.
3
VERSION
=
3.
4
# Version number of Python's own shared library file.
...
...
@@ -15562,7 +15562,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by python
$as_me
3.
3
, which was
This file was extended by python
$as_me
3.
4
, which was
generated by GNU Autoconf 2.68. Invocation command line was
CONFIG_FILES =
$CONFIG_FILES
...
...
@@ -15624,7 +15624,7 @@ _ACEOF
cat
>>
$CONFIG_STATUS
<<
_ACEOF
|| ac_write_fail=1
ac_cs_config="`
$as_echo
"
$ac_configure_args
" | sed 's/^ //; s/[
\\
""
\`\$
]/
\\\\
&/g'`"
ac_cs_version="
\\
python config.status 3.
3
python config.status 3.
4
configured by
$0
, generated by GNU Autoconf 2.68,
with options
\\
"
\$
ac_cs_config
\\
"
...
...
configure.ac
View file @
40083373
...
...
@@ -3,7 +3,7 @@ dnl * Please run autoreconf to test your changes! *
dnl ***********************************************
# Set VERSION so we only need to edit in one place (i.e., here)
m4_define(PYTHON_VERSION, 3.
3
)
m4_define(PYTHON_VERSION, 3.
4
)
AC_PREREQ(2.65)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment