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
51c18166
Commit
51c18166
authored
Oct 22, 2001
by
Andrew M. Kuchling
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix some typos
parent
c8e5645f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
Misc/NEWS
Misc/NEWS
+4
-4
No files found.
Misc/NEWS
View file @
51c18166
...
...
@@ -67,7 +67,7 @@ Core and builtins
- Weak reference objects are now part of the core and offers a C API.
A bug which could allow a core dump when binary operations involved
proxy reference has been fixed. we
e
kref.ReferenceError is now a
proxy reference has been fixed. we
a
kref.ReferenceError is now a
built-in exception.
- unicode(obj) now behaves more like str(obj), accepting arbitrary
...
...
@@ -279,7 +279,7 @@ Type/class unification and new-style classes
- For new-style classes, what was previously called __getattr__ is now
called __getattribute__. This method, if defined, is called for
*every* attribute access. A new __getattr__ hook mor similar to the
*every* attribute access. A new __getattr__ hook mor
e
similar to the
one in classic classes is defined which is called only if regular
attribute access raises AttributeError; to catch *all* attribute
access, you can use __getattribute__ (for new-style classes). If
...
...
@@ -323,8 +323,8 @@ Core
makes unicode() behave like str() when applied to non-string/buffer
objects.
- PyFile_WriteObject now passes Unicode object to the file's write
method. As a result, all file-like object which may be the target
- PyFile_WriteObject now passes Unicode object
s
to the file's write
method. As a result, all file-like object
s
which may be the target
of a print statement must support Unicode objects, i.e. they must
at least convert them into ASCII strings.
...
...
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