pyobjc-dev — CVS commit notices go here

Re: [Pyobjc-dev] Incompatible change in CVS

[Just v. R. <ju...@le...>]

Ronald Oussoren wrote:

> I've just checked in a patch that introduces the package PyObjCTools 
> and moved Foundation.Conversion and AppKit.NibClassBuilder to this 
> package. The AppKit and Foundation packages now only contain wrappers 
> for functionality in Apple's Cocoa libraries.

Great, thanks. We could in theory provide a b/w compatible
AppKit.NibClassBuilder that issues a warning. Not sure if it's worth it,
though.

> It is also no longer necessary to call the release method on objects 
> allocated using the 'alloc' classmethod, due to a fix for bug 711700.

But does this also mean that code that _does_ release objects that were
allocated using alloc will now crash?

Just

[Pyobjc-dev] Incompatible change in CVS

[Ronald O. <ous...@ci...>]

I've just checked in a patch that introduces the package PyObjCTools 
and moved Foundation.Conversion and AppKit.NibClassBuilder to this 
package. The AppKit and Foundation packages now only contain wrappers 
for functionality in Apple's Cocoa libraries.

It is also no longer necessary to call the release method on objects 
allocated using the 'alloc' classmethod, due to a fix for bug 711700.

Ronald

Re: [Pyobjc-dev] 0.9 pkg

[Ronald O. <ous...@ci...>]

On Friday, Mar 28, 2003, at 14:03 Europe/Amsterdam, Richard Chamberlain 
wrote:

> Hello Folks,
>
> There was mention of a 0.9 pkg at the end of March. Is that still the 
> plan?

Yes, although it will probably early April.

Ronald

[Pyobjc-dev] [ pyobjc-Bugs-711700 ] NSMachPort.alloc() infinite recursion

[SourceForge.net <no...@so...>]

Bugs item #711700, was opened at 2003-03-28 20:16
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=711700&group_id=14534

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: NSMachPort.alloc() infinite recursion

Initial Comment:
#5002 0x907f4a0c in -[NSMachPort retain] ()
#5003 0x90131e74 in CFRetain ()
#5004 0x907f4a0c in -[NSMachPort retain] ()
#5005 0x90131e74 in CFRetain ()
#5006 0x907f4a0c in -[NSMachPort retain] ()
#5007 0x00575e18 in ObjCObject_New (objc_object=0x392c90) at Modules/objc/objc-object.m:333
#5008 0x0056ac18 in -[NSObject(PyObjCSupport) __pyobjc_PythonObject__] (self=0x392c90, _cmd=0x5889f0) at Modules/objc/objc_support.m:46
#5009 0x0056c5d0 in pythonify_c_value (type=0x58890c "@", datum=0xbffff380) at Modules/objc/objc_support.m:677
#5010 0x00581c04 in supercall_NSObject_alloc (method=0x392900, self=0x739170, arguments=0x338850) at Modules/objc/alloc_hack.m:66
#5011 0x00577bd0 in objcsel_call (self=0x392900, args=0x338850) at Modules/objc/selector.m:630
#5012 0x000590d4 in PyObject_Call (func=0x392c90, arg=0x9068d70c, kw=0x908c8ca3) at Objects/abstract.c:1688
#5013 0x00074c3c in do_call (func=0x392900, pp_stack=0xbffff914, na=0, nk=0) at Python/ceval.c:3271
#5014 0x00072704 in eval_frame (f=0x34daa0) at Python/ceval.c:2037
#5015 0x00073a40 in PyEval_EvalCodeEx (co=0x39b280, globals=0x9068d70c, locals=0x907f4a0c, args=0x2, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2595
#5016 0x00076564 in PyEval_EvalCode (co=0x392c90, globals=0x9068d70c, locals=0x908c8ca3) at Python/ceval.c:481
#5017 0x0002a558 in run_node (n=0x2, filename=0x9068d70c "self", globals=0x3914a3, locals=0x0, flags=0xffffffff) at Python/pythonrun.c:1079
#5018 0x00029ad4 in PyRun_InteractiveOneFlags (fp=0x39b280, filename=0x0, flags=0x3387f0) at Python/pythonrun.c:590
#5019 0x000298b4 in PyRun_InteractiveLoopFlags (fp=0x349944, filename=0x392060 "", flags=0xb98e0) at Python/pythonrun.c:526
#5020 0x0002b2cc in PyRun_AnyFileExFlags (fp=0xa0000cd4, filename=0xb2864 "<stdin>", closeit=3377136, flags=0xbffffc70) at Python/pythonrun.c:489
#5021 0x00006294 in Py_Main (argc=603980418, argv=0x0) at Modules/main.c:364
#5022 0x000021a4 in _start (argc=1, argv=0xbffffd74, envp=0xbffffd7c) at /SourceCache/Csu/Csu-45/crt.c:267
#5023 0x00002024 in start ()


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=711700&group_id=14534

[Pyobjc-dev] 0.9 pkg

[Richard C. <sun...@ma...>]

Hello Folks,

There was mention of a 0.9 pkg at the end of March. Is that still the 
plan?

If not I'll bite the bullet and download from CVS, but I was rather 
hoping for a nice convenient pkg.

Thanks a lot,

Richard

Re: [Pyobjc-dev] build error

[Just v. R. <ju...@le...>]

Ronald Oussoren wrote:

> > Current CVS fails to build for me (with CVS Python)
> 
> How recent is your CVS snapshot?

Not recent enough... It works great now. Sorry!

Just

Re: [Pyobjc-dev] build error

[Ronald O. <ous...@ci...>]

On Monday, Mar 24, 2003, at 18:07 Europe/Amsterdam, Just van Rossum 
wrote:

> Current CVS fails to build for me (with CVS Python)

How recent is your CVS snapshot? I'm using the newly introduced 
PyHeapTypeObject with Python 2.3 to get rid of a seperate datastructure 
for storing additional data for the class proxies. This was added very 
recently (I noticed it in the previous python-dev summary).

I currently don't have problems compiling the bridge (after earlier 
today fixing some stupid errors that broke Python 2.2 builds).

Ronald

[Pyobjc-dev] Fwd: I assume a similar fix would make initWithHTML work?

[Ronald O. <ous...@ci...>]

Direct reply got caught by TDMA (some kind of whitelisting software).

Begin forwarded message:

> From: Ronald Oussoren <ous...@ci...>
> Date: Mon Mar 24, 2003  18:50:54 Europe/Amsterdam
> To: Rod Morehead <rm...@rm...>
> Subject: Re: I assume a similar fix would make initWithHTML work?
>
> Yes, the signature strings for init methods should all start with 
> '@@:' or '@0@4:8' (the latter are magic numbers generated by the 
> compiler, but strangely enough not by the runtime).
>
> Ronald
>
> On Monday, Mar 24, 2003, at 18:21 Europe/Amsterdam, Rod Morehead wrote:
>
>> Message: 4
>> Date: Mon, 24 Mar 2003 09:01:47 +0100
>> Subject: Re: [Pyobjc-dev] 
>> NSAttributedString.initWithPath_documentAttributes_
>> Cc: pyo...@li...
>> To: Steve Reeves <st...@sy...>
>> From: Ronald Oussoren <ous...@ci...>
>>
>>
>> On Monday, Mar 24, 2003, at 08:16 Europe/Amsterdam, Steve Reeves 
>> wrote:
>>
>>> I'm trying to load some data into an NSAttributedString with the
>>> initWithPath_documentAttributes_ method (or one of the other
>>> initWith...
>>> variants in AppKit) and am having trouble:
>>>
>>> ~ % /usr/bin/python
>>> Python 2.2 (#1, 07/14/02, 23:25:09)
>>> [GCC Apple cpp-precomp 6.14] on darwin
>>> Type "help", "copyright", "credits" or "license" for more 
>>> information.
>>>>>> import objc
>>>>>> import Foundation
>>>>>> import AppKit
>>>>>> foo = Foundation.NSAttributedString.alloc()
>>>>>> foo. initWithPath_documentAttributes_('aFile', objc.nil)
>>> Traceback (most recent call last):
>>>   File "<stdin>", line 1, in ?
>>> objc.internal_error: objc_sizeof_type: Unhandled type '0x38
>>
>> That's a bug, but luckily an easy to solve one. I've just checked in a
>> fixed for this. A quick fix would be to change
>> objc/_FoundationSignatures.py. Look for
>> 'initWithPath:documentAttributes:' and add '@@:' at the start of the
>> signature string (currently starting with '8').
>>
>> Your code still won't work with that version: The last argument of the
>> method is an output parameter, those are not present in the python
>> argument list. The last call should be:
>>
>> 	foo, documentAttributes = 
>> foo.initWithPath_documentAttributes_('aFile')
>>
>> Ronald
>>
>>
>

[Pyobjc-dev] Re: PyObjC tutorial/talk at EuroPython

[Michael H. <mw...@py...>]

Ronald Oussoren <ous...@ci...> writes:

> On Monday, Mar 24, 2003, at 13:17 Europe/Amsterdam, Just van Rossum
> wrote:

[PyObjC@EuroPython]

>> I would be happy to do a little talk about PyObjC, but if Ronald also
>> wants to go (and he should!) and do a talk, then that should be
>> preferred. Or we could do a split talk.
>
> I was contemplating going to EuroPython as a visitor. Doing a talk on
> PyObjC would also be nice.

Please feel suitably encouraged!  As I said to Jack, I can nobble the
Python Language Track chairman[1] in you favour :-)

Cheers,
M.

[1] Me.

-- 
81. In computing, turning the obvious into the useful is a living
    definition of the word "frustration".
  -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html

Re: [Pyobjc-dev] PyObjC tutorial/talk at EuroPython

[Ronald O. <ous...@ci...>]

On Monday, Mar 24, 2003, at 13:17 Europe/Amsterdam, Just van Rossum 
wrote:

> Jack Jansen wrote:
>
>> I was thinking of submitting a talk on MacPython-OSX in general, but
>> I still have to check how the dates fit my agenda, and whether my
>> budget allows it.
>
> Europython was lots of fun last year, and it was very affordable,
> especially compared to your average conference. You should really go!
>
>> If there was also a talk on PyObjC that would make a nice split, and
>> would allow the two talks to each focus on their own subject, whereas
>> if there was only one talk it would have to cover a lot of material
>> of the other as well...
>
> I would be happy to do a little talk about PyObjC, but if Ronald also
> wants to go (and he should!) and do a talk, then that should be
> preferred. Or we could do a split talk.

I was contemplating going to EuroPython as a visitor. Doing a talk on 
PyObjC would also be nice.

Ronald

Re: [Pyobjc-dev] Re: beginner, base b64

[Zachery B. <zb...@ur...>]

On Monday, Mar 24, 2003, at 12:42 US/Eastern, jorjun wrote:

> Guys!
>
> Please help. I bet there is a simple Python module to unencode the 
> attachment include in the last digest, or OS X command line tools I am 
> not using properly.
> I tried saving the text, and applying <uudecode> to it, but it 
> complained about the lack of begin line.
> Stuffit was nice and created a .tgz of the correct name, tar -xvf 
> didn't recognise the format.

Close. `tar xvfz pyobjc-currencyconverter-stepbystep.tgz`

.tgz tells you it's a gzipped tar ball, no different than .tar.gz

Zac

[Pyobjc-dev] Re: beginner, base b64

[jorjun <jo...@ma...>]

Guys!

Please help. I bet there is a simple Python module to unencode the 
attachment include in the last digest, or OS X command line tools I am 
not using properly.
I tried saving the text, and applying <uudecode> to it, but it 
complained about the lack of begin line.
Stuffit was nice and created a .tgz of the correct name, tar -xvf 
didn't recognise the format.

TIA

[Pyobjc-dev] build error

[Just v. R. <ju...@le...>]

Current CVS fails to build for me (with CVS Python)

[ ... ]
creating build/temp.darwin-6.3-Power_Macintosh-2.3/Modules/objc
gcc -Wno-long-double -no-cpp-precomp -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -I/usr/local/include/python2.3 -c
Modules/objc/class-builder.m -o
build/temp.darwin-6.3-Power_Macintosh-2.3/Modules/objc/class-builder.o
-DOBJC_PARANOIA_MODE -DOC_WITH_LIBFFI -isystem libffi/include
-DOC_USE_FFI_SHORTCUTS -DMACOSX -no-cpp-precomp -Wno-long-double -g
-IInclude/
In file included from Modules/objc/class-builder.m:6:
Modules/objc/pyobjc.h:54: parse error before "PyHeapTypeObject"
Modules/objc/pyobjc.h:54: warning: no semicolon at end of struct or
union
Modules/objc/pyobjc.h:58: parse error before '}' token
Modules/objc/pyobjc.h:58: warning: type defaults to `int' in declaration
of `PyObjCClassObject'
Modules/objc/pyobjc.h:58: warning: data definition has no type or
storage class
Modules/objc/pyobjc.h:78: parse error before "PyObjCObject_Type"
Modules/objc/pyobjc.h:78: warning: type defaults to `int' in declaration
of `PyObjCObject_Type'
Modules/objc/pyobjc.h:78: warning: data definition has no type or
storage class
error: command 'gcc' failed with exit status 1


Just

Re: [Pyobjc-dev] Adding outlets and actions without rewiring it all

[<bb...@ma...>]

On Monday, Mar 24, 2003, at 11:19 US/Eastern, Jack Jansen wrote:
> 2. Decide on how to format it: plain text or html, one file with
>    step numbers or a number of linked files, how to organize the files
>    that I've now simply dumped into "src-afterstep6" and such, etc.

Restructured text -- that way, we can generate HTML, plain text, LaTeX 
and PDF from the ReST source.   ReST is really easy to write and the 
raw "source" is very readable.   We already have a bunch of ReST source 
in the repository.

I'll *try* to find some time to contribute to this.   Life has been 
rather, uh, hellish recently.

I'm currently mired deep in a Cocoa/Java project.   It definitely makes 
one appreciate the simple elegance of Cocoa/Python.

b.bum

Re: [Pyobjc-dev] Adding outlets and actions without rewiring it all

[Ronald O. <ous...@ci...>]

On Monday, Mar 24, 2003, at 11:27 Europe/Amsterdam, Antonio Rodriguez 
wrote:
>
> Hope this helps anyone reading this thread. I wholeheartedly agree 
> with Jack's point. PyObjC is true magic on the scale of pixie dust but 
> right now there are just too many hurdles to get through unless one is 
> really family with the cocoa way of doing things. I've found that the 
> PyObjC examples help a ton, especially the "WebServices Tool" one 
> which is the closest to being a real app. Perhaps one thing to do is 
> to have others who have created 'real' apps submit them to be included 
> in the examples dir?
>
Adding more real applications would be usefull, but I think it would be 
more usefull to add those as separate downloads and/or links to other 
projects.

You must pass a number of hurdles before being able to fully use the 
bridge, but in my experience those are mostly Cocoa hurdles in general. 
I am of course slightly biased :-).

Ronald

Re: [Pyobjc-dev] Adding outlets and actions without rewiring it all

[Jack J. <Jac...@cw...>]

Okay, I did a straw-man of a step-by-step tutorial:

Re: [Pyobjc-dev] Adding outlets and actions without rewiring it all

[Antonio R. <an...@me...>]

Here was the key to my original question (and looking at it, I think it 
may be more an IB question than a PyObjC question):

I thought that once one uses IB to "define" a class (pick the parent 
class and add outlets and actions) and subsequently to instantiate a 
class into an instance that goes into that palette window, the only way 
to add more outlets/actions after the instance has been wired was to 
delete the instance, add the outlets/actions to the class definition 
and then re-instantiate and re-wire it.

However, it seems as though all one needs to do is to switch over the 
class definition and add the actions/outlets as appropriate. After 
that, when ctr-clicking to/from the instance, the new actions/outlets 
of the class definition will appear.

Hope this helps anyone reading this thread. I wholeheartedly agree with 
Jack's point. PyObjC is true magic on the scale of pixie dust but right 
now there are just too many hurdles to get through unless one is really 
family with the cocoa way of doing things. I've found that the PyObjC 
examples help a ton, especially the "WebServices Tool" one which is the 
closest to being a real app. Perhaps one thing to do is to have others 
who have created 'real' apps submit them to be included in the examples 
dir?

Thanks to all who answered.

Antonio


On Monday, March 24, 2003, at 01:47 AM, Ronald Oussoren wrote:

>
> On Sunday, Mar 23, 2003, at 22:00 Europe/Amsterdam, Jack Jansen wrote:
>
>>
>> On zaterdag, maa 22, 2003, at 19:48 Europe/Amsterdam, Ronald Oussoren 
>> wrote:
>>> What I usually do is:
>>> - Paint a UI in Interface Builder, including the initial definition 
>>> of one or
>>>   more model classes/objects.
>>> - Generate a template using AppKit.NibClassBuilder (used a script)
>>> - Fill in the template.
>>>
>>> If the model interface changes later on I change the definition in 
>>> IB and update the python files. There is no need to rewire anything 
>>> in > IB.
>>
>> This procedure needs to be documented. and probably in a step-by-step 
>> way. It is essential to PyObjC
>> development, but it is also pretty obscure. Even more obscure than 
>> the corresponding ObjC procedure
>> (which you also will never find if you don't do one of Apple's 
>> examples).
>
> Thanks for the tip. It is pretty obvious to me, hence the lack of 
> documentation. I'm sure there are more features/procedures that are 
> obvious for someone familiar with PyObjC but not for a newby. Please 
> keep us informed of them. "There are no dumb questions, only lacking 
> documentation"
>
> Ronald
>
>

Re: [Pyobjc-dev] NSApplicationMain idiom: wish to standardize

[Jack J. <Jac...@cw...>]

On Thursday, Mar 20, 2003, at 15:23 Europe/Amsterdam, Just van Rossum 
wrote:

> I've been using the following idiom to enter the Cocoa main event loop 
> for
> some time now:
>
>
> def unexpectedErrorAlert():
>     exceptionInfo =
> traceback.format_exception_only(*sys.exc_info()[:2])[0].strip()
>     return NSRunAlertPanel("An unexpected error has occurred",
>             "(%s)" % exceptionInfo,
>             "Continue", "Quit", None)
>
>
> mainFunc = NSApplicationMain
> args = (sys.argv,)
> while 1:
>     try:
>         mainFunc(*args)
>     except:
>         traceback.print_exc()
>         if not unexpectedErrorAlert():
>             break
>         mainFunc = NSApp().run
>         args = ()
>     else:
>         break

Just,
I modified this a bit, by putting everything, including all needed 
imports,
into a main() program. Also, in stead of printing the traceback before 
calling
unexpectedErrorAlert() I call raise in stead of break, this keeps the 
console
log clean if the user decides to continue and it also enables debugging 
with the
standard trick of setting PYTHONINSPECT=1 before you run your program, 
and then
doing "import pdb; pdb.pm()" after the program has crashed.

Here it is:
def main():
     from AppKit import NSApplicationMain, NSRunAlertPanel, NSApp
     import traceback
     import sys
     def unexpectedErrorAlert():
         exceptionInfo = 
traceback.format_exception_only(*sys.exc_info()[:2])[0].strip()
         return NSRunAlertPanel("An unexpected error has occurred",
                 "(%s)" % exceptionInfo,
                 "Continue", "Quit", None)


     mainFunc = NSApplicationMain
     args = (sys.argv,)
     while 1:
         try:
             mainFunc(*args)
         except:
             if not unexpectedErrorAlert():
                 raise
             mainFunc = NSApp().run
             args = ()
         else:
             break

if __name__ == '__main__':
     main()
--
Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman

[Pyobjc-dev] Re: PyObjC tutorial/talk at EuroPython

[Michael H. <mw...@py...>]

Jack Jansen <Jac...@cw...> writes:

> On Monday, Mar 24, 2003, at 10:54 Europe/Amsterdam, Michael Hudson
> wrote:
>
>> I seem to have gotten landed with running a track at the upcoming
>> EuroPython conference in Charleroi in June 2003, and I'd love for it
>> to contain a talk on PyObjC (or maybe general Python/OS X integration
>> issues).
>>
>> Could anyone here give such a talk? (more details at
>> http://www.europython.org).
>
> I was thinking of submitting a talk on MacPython-OSX in general, but
> I still have to check how the dates fit my agenda, and whether my
> budget allows it.

Please do!  If you submit it to the Python Language track, it has a
fairly good chance of being accepted <wink>.

As Just says, EuroPython last year was cheap and fun (well, it was
expensive for me because I contrived to lose my glasses, but...).

> If there was also a talk on PyObjC that would make a nice split, and
> would allow the two talks to each focus on their own subject,
> whereas if there was only one talk it would have to cover a lot of
> material of the other as well...

That'd be cool.  What's the point of running a track if you can't
schedule talks you want to hear?

Cheers,
M.

-- 
  In general, I'd recommend injecting LSD directly into your temples,
  Syd-Barret-style, before mucking with Motif's resource framework.
  The former has far lower odds of leading directly to terminal
  insanity.                                            -- Dan Martinez

Re: [Pyobjc-dev] PyObjC tutorial/talk at EuroPython

[Just v. R. <ju...@le...>]

Jack Jansen wrote:

> I was thinking of submitting a talk on MacPython-OSX in general, but
> I still have to check how the dates fit my agenda, and whether my
> budget allows it.

Europython was lots of fun last year, and it was very affordable,
especially compared to your average conference. You should really go!

> If there was also a talk on PyObjC that would make a nice split, and
> would allow the two talks to each focus on their own subject, whereas
> if there was only one talk it would have to cover a lot of material
> of the other as well...

I would be happy to do a little talk about PyObjC, but if Ronald also
wants to go (and he should!) and do a talk, then that should be
preferred. Or we could do a split talk.

Just

Re: [Pyobjc-dev] PyObjC tutorial/talk at EuroPython

[Jack J. <Jac...@cw...>]

On Monday, Mar 24, 2003, at 10:54 Europe/Amsterdam, Michael Hudson 
wrote:

> I seem to have gotten landed with running a track at the upcoming
> EuroPython conference in Charleroi in June 2003, and I'd love for it
> to contain a talk on PyObjC (or maybe general Python/OS X integration
> issues).
>
> Could anyone here give such a talk? (more details at
> http://www.europython.org).

I was thinking of submitting a talk on MacPython-OSX in general, but I 
still
have to check how the dates fit my agenda, and whether my budget allows 
it.

If there was also a talk on PyObjC that would make a nice split, and 
would allow
the two talks to each focus on their own subject, whereas if there was 
only
one talk it would have to cover a lot of material of the other as 
well...
--
Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman

Re: [Pyobjc-dev] Adding outlets and actions without rewiring it all

[Jack J. <Jac...@cw...>]

On Monday, Mar 24, 2003, at 07:47 Europe/Amsterdam, Ronald Oussoren 
wrote:

>
> On Sunday, Mar 23, 2003, at 22:00 Europe/Amsterdam, Jack Jansen wrote:
>
>>
>> On zaterdag, maa 22, 2003, at 19:48 Europe/Amsterdam, Ronald Oussoren 
>> wrote:
>>> What I usually do is:
>>> - Paint a UI in Interface Builder, including the initial definition 
>>> of one or
>>>   more model classes/objects.
>>> - Generate a template using AppKit.NibClassBuilder (used a script)
>>> - Fill in the template.
>>>
>>> If the model interface changes later on I change the definition in 
>>> IB and update the python files. There is no need to rewire anything 
>>> in > IB.
>>
>> This procedure needs to be documented. and probably in a step-by-step 
>> way. It is essential to PyObjC
>> development, but it is also pretty obscure. Even more obscure than 
>> the corresponding ObjC procedure
>> (which you also will never find if you don't do one of Apple's 
>> examples).
>
> Thanks for the tip. It is pretty obvious to me, hence the lack of 
> documentation. I'm sure there are more features/procedures that are 
> obvious for someone familiar with PyObjC but not for a newby.

I think I may have some time on my hands today, and it's been long 
enough ago that I did something from scratch with PyObjC that I may be 
a reasonable guinea-pig. I'll give the Apple Cocoa introduction a go 
(in Python, of course) and I'll keep notes.
> --
Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman

[Pyobjc-dev] PyObjC tutorial/talk at EuroPython

[Michael H. <mw...@py...>]

I seem to have gotten landed with running a track at the upcoming
EuroPython conference in Charleroi in June 2003, and I'd love for it
to contain a talk on PyObjC (or maybe general Python/OS X integration
issues).

Could anyone here give such a talk? (more details at
http://www.europython.org).

Cheers,
M.

-- 
  And not only in the sense that they imagine heretics where these
  do not exist, but also that inquistors repress the heretical
  putrefaction so vehemently that many are driven to share in it,
  in their hatred of the judges.  -- The Name Of The Rose, Umberto Eco

Re: [Pyobjc-dev] NSAttributedString.initWithPath_documentAttributes_

[Ronald O. <ous...@ci...>]

On Monday, Mar 24, 2003, at 08:16 Europe/Amsterdam, Steve Reeves wrote:

> I'm trying to load some data into an NSAttributedString with the
> initWithPath_documentAttributes_ method (or one of the other 
> initWith...
> variants in AppKit) and am having trouble:
>
> ~ % /usr/bin/python
> Python 2.2 (#1, 07/14/02, 23:25:09)
> [GCC Apple cpp-precomp 6.14] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import objc
>>>> import Foundation
>>>> import AppKit
>>>> foo = Foundation.NSAttributedString.alloc()
>>>> foo. initWithPath_documentAttributes_('aFile', objc.nil)
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> objc.internal_error: objc_sizeof_type: Unhandled type '0x38

That's a bug, but luckily an easy to solve one. I've just checked in a 
fixed for this. A quick fix would be to change 
objc/_FoundationSignatures.py. Look for 
'initWithPath:documentAttributes:' and add '@@:' at the start of the 
signature string (currently starting with '8').

Your code still won't work with that version: The last argument of the 
method is an output parameter, those are not present in the python 
argument list. The last call should be:

	foo, documentAttributes = foo.initWithPath_documentAttributes_('aFile')

Ronald

[Pyobjc-dev] NSAttributedString.initWithPath_documentAttributes_

[Steve R. <st...@sy...>]

I'm trying to load some data into an NSAttributedString with the
initWithPath_documentAttributes_ method (or one of the other initWith...
variants in AppKit) and am having trouble:

~ % /usr/bin/python
Python 2.2 (#1, 07/14/02, 23:25:09)
[GCC Apple cpp-precomp 6.14] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import objc
>>> import Foundation
>>> import AppKit
>>> foo = Foundation.NSAttributedString.alloc()
>>> foo.initWithPath_documentAttributes_('aFile', objc.nil)
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
objc.internal_error: objc_sizeof_type: Unhandled type '0x38

-- 
Steve Reeves
st...@sy...