Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 0164ffe

Browse filesBrowse files
farcepestfarcepest
committed
Let's not forget history...
1 parent 973660b commit 0164ffe
Copy full SHA for 0164ffe

File tree

Expand file treeCollapse file tree

1 file changed

+161
-152
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+161
-152
lines changed

‎MySQLdb/HISTORY

Copy file name to clipboard
+161-152Lines changed: 161 additions & 152 deletions
Original file line numberDiff line numberDiff line change
@@ -1,152 +1,161 @@
1-
=====================
2-
What's new in 1.2.4
3-
=====================
4-
5-
beta 2
6-
======
7-
8-
Reverted an accidental change in the exception format. (issue #1)
9-
10-
Reverted some raise statements so that they will continue to work with Python < 2.6
11-
12-
13-
beta 1
14-
======
15-
16-
A lot of work has been done towards Python 3 compatibility, and avoiding warnings with Python 2.7.
17-
This includes import changes, converting dict.has_kay(k) to k in dict, updating some test suite methods, etc.
18-
19-
Due to the difficulties of supporting Python 3 and Python < 2.7, 1.2.4 will support Python 2.4 though 2.7.
20-
1.3.0 will support Python 3 and Python 2.7 and 2.6.
21-
22-
MySQLdb-2.0 is instead going to become moist-1.0. See https://github.com/farcepest/moist
23-
24-
The Windows build has been simplified, and I plan to correct pre-built i386 packages built
25-
against the python.org Python-2.7 package and MySQL Connector/C-6.0. Contact me if you
26-
need ia64 packages.
27-
28-
The connection's cursorclass (if not default) was being lost on reconnect.
29-
30-
Newer versions of MySQL don't use OpenSSL and therefore don't have HAVE_SSL defined, but they do have
31-
a different SSL library. Fixed this so SSL support would be enabled in this case.
32-
33-
The regex that looked for SQL INSERT statement and VALUES in cursor.executemany() was made case-insensitive
34-
again.
35-
36-
37-
=====================
38-
What's new in 1.2.3
39-
=====================
40-
41-
ez_setup.py has been update to include various fixes that affect the build.
42-
43-
Better Python version and dependency detection as well as eliminate exception
44-
warnings under Python 2.6.
45-
46-
Eliminated memory leaks related to Unicode and failed connections.
47-
48-
Corrected connection .escape() functionality.
49-
50-
Miscellaneous cleanups and and expanded testing suite to ensure ongoing release
51-
quality.
52-
53-
=====================
54-
What's new in 1.2.2
55-
=====================
56-
57-
The build system has been completely redone and should now build
58-
on Windows without any patching; uses setuptools.
59-
60-
Added compatibility for Python 2.5, including support for with statement.
61-
62-
connection.ping() now takes an optional boolean argument which can
63-
enable (or disable) automatic reconnection.
64-
65-
Support returning SET columns as Python sets was removed due to an
66-
API bug in MySQL; corresponding test removed.
67-
68-
Added a test for single-character CHAR columns.
69-
70-
BLOB columns are now returned as Python strings instead of byte arrays.
71-
72-
BINARY character columns are always returned as Python strings, and not
73-
unicode.
74-
75-
Fixed a bug introduced in 1.2.1 where the new SHOW WARNINGS support broke
76-
SSCursor.
77-
78-
Only encode the query (convert to a string) when it is a unicode instance;
79-
re-encoding encoded strings would break things.
80-
81-
Make a deep copy of conv when connecting, since it can be modified.
82-
83-
Added support for new VARCHAR and BIT column types.
84-
85-
DBAPISet objects were broken, but nobody noticed.
86-
87-
88-
========================
89-
What's new in 1.2.1_p2
90-
========================
91-
92-
There are some minor build fixes which probably only affect MySQL
93-
older than 4.0.
94-
95-
If you had MySQL older than 4.1, the new charset and sql_mode
96-
parameters didn't work right. In fact, it was impossible to create
97-
a connection due to the charset problem.
98-
99-
If you are using MySQL-4.1 or newer, there is no practical difference
100-
between 1.2.1 and 1.2.1_p2, and you don't need to upgrade.
101-
102-
103-
=====================
104-
What's new in 1.2.1
105-
=====================
106-
107-
Switched to Subversion. Was going to do this for 1.3, but a
108-
SourceForge CVS outage has forced the issue.
109-
110-
Mapped a lot of new 4.1 and 5.0 error codes to Python exceptions
111-
112-
Added an API call for mysql_set_character_set(charset) (MySQL > 5.0.7)
113-
114-
Added an API call for mysql_get_character_set_info() (MySQL > 5.0.10)
115-
116-
Revamped the build system. Edit site.cfg if necessary (probably not
117-
in most cases)
118-
119-
Python-2.3 is now the minimum version.
120-
121-
Dropped support for mx.Datetime and stringtimes; always uses Python
122-
datetime module now.
123-
124-
Improved unit tests
125-
126-
New connect() options:
127-
* charset: sets character set, implies use_unicode
128-
* sql_mode: sets SQL mode (i.e. ANSI, etc.; see MySQL docs)
129-
130-
When using MySQL-4.1 or newer, enables MULTI_STATEMENTS
131-
132-
When using MySQL-5.0 or newer, enables MULTI_RESULTS
133-
134-
When using MySQL-4.1 or newer, more detailed warning messages
135-
are produced
136-
137-
SET columns returned as Python Set types; you can pass a Set as
138-
a parameter to cursor.execute().
139-
140-
Support for the new MySQL-5.0 DECIMAL implementation
141-
142-
Support for Python Decimal type
143-
144-
Some use of weak references internally. Cursors no longer leak
145-
if you don't close them. Connections still do, unfortunately.
146-
147-
ursor.fetchXXXDict() methods raise DeprecationWarning
148-
149-
cursor.begin() is making a brief reappearence.
150-
151-
cursor.callproc() now works, with some limitations.
152-
1+
=====================
2+
What's new in 1.2.4
3+
=====================
4+
5+
beta 3
6+
======
7+
8+
Unified test database configuration, and set up CI testing with Travis.
9+
10+
Applied several patches from André Malo (ndparker@users.sf.net) which fix some issues
11+
with exception handling and reference counting and TEXT/BLOB conversion.
12+
13+
14+
beta 2
15+
======
16+
17+
Reverted an accidental change in the exception format. (issue #1)
18+
19+
Reverted some raise statements so that they will continue to work with Python < 2.6
20+
21+
22+
beta 1
23+
======
24+
25+
A lot of work has been done towards Python 3 compatibility, and avoiding warnings with Python 2.7.
26+
This includes import changes, converting dict.has_kay(k) to k in dict, updating some test suite methods, etc.
27+
28+
Due to the difficulties of supporting Python 3 and Python < 2.7, 1.2.4 will support Python 2.4 though 2.7.
29+
1.3.0 will support Python 3 and Python 2.7 and 2.6.
30+
31+
MySQLdb-2.0 is instead going to become moist-1.0. See https://github.com/farcepest/moist
32+
33+
The Windows build has been simplified, and I plan to correct pre-built i386 packages built
34+
against the python.org Python-2.7 package and MySQL Connector/C-6.0. Contact me if you
35+
need ia64 packages.
36+
37+
The connection's cursorclass (if not default) was being lost on reconnect.
38+
39+
Newer versions of MySQL don't use OpenSSL and therefore don't have HAVE_SSL defined, but they do have
40+
a different SSL library. Fixed this so SSL support would be enabled in this case.
41+
42+
The regex that looked for SQL INSERT statement and VALUES in cursor.executemany() was made case-insensitive
43+
again.
44+
45+
46+
=====================
47+
What's new in 1.2.3
48+
=====================
49+
50+
ez_setup.py has been update to include various fixes that affect the build.
51+
52+
Better Python version and dependency detection as well as eliminate exception
53+
warnings under Python 2.6.
54+
55+
Eliminated memory leaks related to Unicode and failed connections.
56+
57+
Corrected connection .escape() functionality.
58+
59+
Miscellaneous cleanups and and expanded testing suite to ensure ongoing release
60+
quality.
61+
62+
=====================
63+
What's new in 1.2.2
64+
=====================
65+
66+
The build system has been completely redone and should now build
67+
on Windows without any patching; uses setuptools.
68+
69+
Added compatibility for Python 2.5, including support for with statement.
70+
71+
connection.ping() now takes an optional boolean argument which can
72+
enable (or disable) automatic reconnection.
73+
74+
Support returning SET columns as Python sets was removed due to an
75+
API bug in MySQL; corresponding test removed.
76+
77+
Added a test for single-character CHAR columns.
78+
79+
BLOB columns are now returned as Python strings instead of byte arrays.
80+
81+
BINARY character columns are always returned as Python strings, and not
82+
unicode.
83+
84+
Fixed a bug introduced in 1.2.1 where the new SHOW WARNINGS support broke
85+
SSCursor.
86+
87+
Only encode the query (convert to a string) when it is a unicode instance;
88+
re-encoding encoded strings would break things.
89+
90+
Make a deep copy of conv when connecting, since it can be modified.
91+
92+
Added support for new VARCHAR and BIT column types.
93+
94+
DBAPISet objects were broken, but nobody noticed.
95+
96+
97+
========================
98+
What's new in 1.2.1_p2
99+
========================
100+
101+
There are some minor build fixes which probably only affect MySQL
102+
older than 4.0.
103+
104+
If you had MySQL older than 4.1, the new charset and sql_mode
105+
parameters didn't work right. In fact, it was impossible to create
106+
a connection due to the charset problem.
107+
108+
If you are using MySQL-4.1 or newer, there is no practical difference
109+
between 1.2.1 and 1.2.1_p2, and you don't need to upgrade.
110+
111+
112+
=====================
113+
What's new in 1.2.1
114+
=====================
115+
116+
Switched to Subversion. Was going to do this for 1.3, but a
117+
SourceForge CVS outage has forced the issue.
118+
119+
Mapped a lot of new 4.1 and 5.0 error codes to Python exceptions
120+
121+
Added an API call for mysql_set_character_set(charset) (MySQL > 5.0.7)
122+
123+
Added an API call for mysql_get_character_set_info() (MySQL > 5.0.10)
124+
125+
Revamped the build system. Edit site.cfg if necessary (probably not
126+
in most cases)
127+
128+
Python-2.3 is now the minimum version.
129+
130+
Dropped support for mx.Datetime and stringtimes; always uses Python
131+
datetime module now.
132+
133+
Improved unit tests
134+
135+
New connect() options:
136+
* charset: sets character set, implies use_unicode
137+
* sql_mode: sets SQL mode (i.e. ANSI, etc.; see MySQL docs)
138+
139+
When using MySQL-4.1 or newer, enables MULTI_STATEMENTS
140+
141+
When using MySQL-5.0 or newer, enables MULTI_RESULTS
142+
143+
When using MySQL-4.1 or newer, more detailed warning messages
144+
are produced
145+
146+
SET columns returned as Python Set types; you can pass a Set as
147+
a parameter to cursor.execute().
148+
149+
Support for the new MySQL-5.0 DECIMAL implementation
150+
151+
Support for Python Decimal type
152+
153+
Some use of weak references internally. Cursors no longer leak
154+
if you don't close them. Connections still do, unfortunately.
155+
156+
ursor.fetchXXXDict() methods raise DeprecationWarning
157+
158+
cursor.begin() is making a brief reappearence.
159+
160+
cursor.callproc() now works, with some limitations.
161+

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.