Bob Ippolito avatar Bob Ippolito committed 248638a

Prep for 1.3 release

Comments (0)

Files changed (11)

 of useful functions, constants, and "difficult" methods are wrapped.  If you
 run across a missing or incorrectly wrapped constant, function, or method
 please report it as a bug and/or post to pyobjc-dev about the issue.  This is
-one area we intend to improve after the release of 1.2 when our new
+one area we intend to improve after the release of 1.3 when our new
 wrapper-generators are in a more complete state.</p>
 <h3><a href="#id11" name="pickle-support">Pickle support</a></h3>
 <p>Objective-C objects don't support pickling.</p>
-<p>This is post-1.2 work, in general this is a hard problem because it may 
+<p>This is post-1.3 work, in general this is a hard problem because it may 
 involve object cycles that cross the Python-ObjC boundary.</p>
 <h3><a href="#id12" name="nscoder-support">NSCoder support</a></h3>
 <p>It might be useful to add default implementations of <code><span>encodeWithCoder:</span></code> and
 of useful functions, constants, and "difficult" methods are wrapped.  If you
 run across a missing or incorrectly wrapped constant, function, or method
 please report it as a bug and/or post to pyobjc-dev about the issue.  This is
-one area we intend to improve after the release of 1.2 when our new
+one area we intend to improve after the release of 1.3 when our new
 wrapper-generators are in a more complete state.
 
 Pickle support
 
 Objective-C objects don't support pickling.
 
-This is post-1.2 work, in general this is a hard problem because it may 
+This is post-1.3 work, in general this is a hard problem because it may 
 involve object cycles that cross the Python-ObjC boundary.
 
 NSCoder support

Doc/announcement.txt

    pythonmac-sig@python.org
    cocoa-dev@lists.apple.com
 
-subject: ANN: PyObjC 1.2
+subject: ANN: PyObjC 1.3
 
-PyObjC 1.2 is now available for download at http://pyobjc.sourceforge.net/  
+PyObjC 1.3 is now available for download at http://pyobjc.sourceforge.net/  
 
 PyObjC is a bridge between Python and Objective-C.  It allows full
 featured Cocoa applications to be written in pure Python.  It is also
 curve.  It combines remarkable power with very clear syntax.
 
 The installer package includes a number of Xcode templates 
-for easily creating new Cocoa-Python projects.
+for easily creating new Cocoa-Python projects, as well as py2app,
+a suite of tools for building redistributable Python applications
+and plugins.
 
 PyObjC also supports full introspection of Objective-C classes and 
 direct invocation of Objective-C APIs from the interactive interpreter.
 
 PyObjC requires Mac OS X 10.2 or later and Python 2.3 or later.  PyObjC works 
-both with the Apple provided Python installation in Mac OS X 10.3 (and later) 
-and with MacPython 2.3.  
+with the Apple provided Python installation in Mac OS X 10.3 (and later),
+MacPython 2.3, and MacPython 2.4.
 
 This release features several bugfixes, improved documentation as well as
 support for categories, easier customization and basic support for creating 
 Interface Builder palettes. See the news file at 
-http://pyobjc.sourceforge.net/NEWS-1.2.txt for more information.
+http://pyobjc.sourceforge.net/NEWS-1.3.txt for more information.
 
 PyObjC is released with an open source license (MIT style).
 
 argument.</p>
 <p>Python's <code><span>array.array</span></code> type may be used to represent a C array if the
 typestr and size match what is expected by the selector.  Numeric, numarray,
-and other third party array types are not supported in PyObjC 1.2.</p>
+and other third party array types are not supported in PyObjC 1.3.</p>
 <p>When you define methods in a subclass of an Objective-C class, the bridge has
 to tell the Objective-C runtime what the signature of those methods is.  The
 basic rule is that all arguments as well as the return value are objects (just
 
 Python's ``array.array`` type may be used to represent a C array if the
 typestr and size match what is expected by the selector.  Numeric, numarray,
-and other third party array types are not supported in PyObjC 1.2.
+and other third party array types are not supported in PyObjC 1.3.
 
 When you define methods in a subclass of an Objective-C class, the bridge has
 to tell the Objective-C runtime what the signature of those methods is.  The

Doc/structure.html

 <p>The original, unwrapped, <code><span>NSString</span></code> instance is accessible from Python
 with the <code><span>nsstring()</span></code> method of <code><span>objc.pyobjc_unicode</span></code>, primarily used
 to access an updated copy of an <code><span>NSMutableString</span></code>'s contents.  Since
-PyObjC 1.2, <code><span>NSString</span></code> and <code><span>NSMutableString</span></code> methods are available from
+PyObjC 1.3, <code><span>NSString</span></code> and <code><span>NSMutableString</span></code> methods are available from
 the <code><span>objc.pyobjc_unicode</span></code> object, though they do not show up via Python's
 introspection mechanisms.</p>
-<p>For legacy and convenience, Python <code><span>str</span></code> instances are automatically coerced
-to <code><span>unicode</span></code> when they cross the bridge using the same mechanism that
-automatically converts from <code><span>str</span></code> to <code><span>unicode</span></code> (using 
-<code><span>sys.getdefaultencoding()</span></code>).  This automatic conversion can cause terrible
-things to happen at runtime that are hard to test for, so you may enable an
-<code><span>objc.PyObjCStrBridgeWarning</span></code> at each coercion attempt by calling
-<code><span>objc.setStrBridgeEnabled(False)</span></code>.  To promote this warning to an exception,
-see the documentation for the <code><span>warnings</span></code> module in the standard library.</p>
+<p>The <code><span>str</span></code> bridge is now disabled by default, and will issue
+<code><span>objc.PyObjCStrBridgeWarning</span></code> warnings.  To promote these to an
+exception, do the following:</p>
+<pre>
+import objc
+import warnings
+warnings.filterwarnings('error', objc.PyObjCStrBridgeWarning)
+</pre>
+<p>To enable the str bridge, without warnings, use:</p>
+<pre>
+import objc
+objc.setStrBridgeEnabled(True)
+</pre>
+<p>In PyObjC 1.4, this warning will go away, and <code><span>str</span></code> objects will not be
+usable as <code><span>NSString</span></code> instances.  To pass text across the bridge,
+always use <code><span>unicode</span></code>.</p>
 </body>
 </html>

Doc/structure.txt

 The original, unwrapped, ``NSString`` instance is accessible from Python
 with the ``nsstring()`` method of ``objc.pyobjc_unicode``, primarily used
 to access an updated copy of an ``NSMutableString``'s contents.  Since
-PyObjC 1.2, ``NSString`` and ``NSMutableString`` methods are available from
+PyObjC 1.3, ``NSString`` and ``NSMutableString`` methods are available from
 the ``objc.pyobjc_unicode`` object, though they do not show up via Python's
 introspection mechanisms.
 
-For legacy and convenience, Python ``str`` instances are automatically coerced
-to ``unicode`` when they cross the bridge using the same mechanism that
-automatically converts from ``str`` to ``unicode`` (using 
-``sys.getdefaultencoding()``).  This automatic conversion can cause terrible
-things to happen at runtime that are hard to test for, so you may enable an
-``objc.PyObjCStrBridgeWarning`` at each coercion attempt by calling
-``objc.setStrBridgeEnabled(False)``.  To promote this warning to an exception,
-see the documentation for the ``warnings`` module in the standard library.
+The ``str`` bridge is now disabled by default, and will issue
+``objc.PyObjCStrBridgeWarning`` warnings.  To promote these to an
+exception, do the following::
+
+      import objc
+      import warnings
+      warnings.filterwarnings('error', objc.PyObjCStrBridgeWarning)
+
+To enable the str bridge, without warnings, use::
+
+      import objc
+      objc.setStrBridgeEnabled(True)
+
+In PyObjC 1.4, this warning will go away, and ``str`` objects will not be
+usable as ``NSString`` instances.  To pass text across the bridge,
+always use ``unicode``.

Doc/tutorial/tutorial.html

 <p>To follow the tutorial you need:</p>
 <blockquote>
 <ul>
-<li>PyObjC 1.2</li>
-<li>py2app 0.1.6 or later (included in the binary installer for PyObjC)</li>
+<li>PyObjC 1.3</li>
+<li>py2app 0.1.8 or later (included in the binary installer for PyObjC)</li>
 <li>Python 2.3 or later (note: PyObjC is NOT compatible with MacPython-OS9)</li>
 <li>Mac OS X 10.2 or later</li>
 <li>Xcode Tools (was Developer Tools for Mac OS X 10.2)</li>

Doc/tutorial/tutorial.txt

 
 To follow the tutorial you need:
 
- * PyObjC 1.2
- * py2app 0.1.6 or later (included in the binary installer for PyObjC)
+ * PyObjC 1.3
+ * py2app 0.1.8 or later (included in the binary installer for PyObjC)
  * Python 2.3 or later (note: PyObjC is NOT compatible with MacPython-OS9)
  * Mac OS X 10.2 or later
  * Xcode Tools (was Developer Tools for Mac OS X 10.2)
 <body>
 <h2>PyObjC NEWS</h2>
 <p>An overview of the relevant changes in new, and older, releases.</p>
-<h2><a name="version-1-3-2005-03">Version 1.3 (2005-03-??)</a></h2>
+<h2><a name="version-1-3-2005-03-31">Version 1.3 (2005-03-31)</a></h2>
 <ul>
 <li>The <code><span>str</span></code> bridge is now disabled by default, and will issue 
 <code><span>objc.PyObjCStrBridgeWarning</span></code> warnings.  To promote these to an
 
 An overview of the relevant changes in new, and older, releases.
 
-Version 1.3 (2005-03-??)
+Version 1.3 (2005-03-31)
 ------------------------
 
 - The ``str`` bridge is now disabled by default, and will issue 
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.