[Pythonmac-SIG] Re: [Pyobjc-dev] missing method?
You need to replace colons in the Cocoa method with underscores in Python, so [dictionaryWithContentsOfFile: @"/path"] // My ObjC may be off a bit, but something like this becomes dictionaryWithContentsOfFile_(u"/path") # note underscore --Dethe As for intelligent machines taking over, a machine does not have to be intelligent to conquer the world; it merely has to be desireable. We've already lost a war to a synthetic species--the automobile--that has killed more than 15 million people; occupied all of our cities except Venice, Italy; and continues to exact crushing taxes in resources, wealth, and time from over half the planet--and everybody wants one. --Grant Thompson smime.p7s Description: S/MIME cryptographic signature ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Some question about pyobjc and creating nib based application...
On Jan 4, 2005, at 8:14 PM, whamoo wrote:
On 05/gen/05, at 01:57, Bob Ippolito wrote:
from Foundation import NSLog
from PyObjCTools import NibClassBuilder
NibClassBuilder.extractClasses("MainMenu")
class provaAppDelegate(NibClassBuilder.AutoBaseClass):
def applicationDidFinishLaunching_(self, aNotification):
NSLog( "Application did finish launching." )
I have added:
def change_(self, sender):
print "hello"
Build all, launch and read this:
Could not connect the action change: to target of class helloworldAppDelegate
Well the class names you are talking about are different from the class name defined in that Python file. Where the heck is this "prova" coming from? I have no idea what you are doing or not doing. I am sorry but I do not know how to help you.
Note that there was a bug at some point with Xcode projects that have a space in their name, but I thought that got fixed. I rarely ever use the Xcode template personally, they mostly just get in my way and cause extra maintenance hassle.
Ok, i've find the problem, but look very strange, i've deleted this two line:
def applicationDidFinishLaunching_(self, aNotification):
NSLog( "Application did finish launching." )
And all works fine, but now, i can't add new function to the class because xcode tell me indentation error (i'm sure there isn't), bof, maybe template and xcode integration have some bug, thanks a lot for support.
This is not a bug in the integration, and it *is* an indentation error. You are mixing spaces and tabs. Don't do that. Turn tabs off in Xcode. I guess we should document this somewhere.
-bob
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] pychecker
Subject: Re: [Pythonmac-SIG] pychecker From: Bob Ippolito <[EMAIL PROTECTED]> Date: Mon, 3 Jan 2005 23:13:21 -0500 To: Robert Kern <[EMAIL PROTECTED]> To: Robert Kern <[EMAIL PROTECTED]> CC: pythonmac-sig@python.org On Jan 3, 2005, at 10:25 PM, Robert Kern wrote: Mike Hansen wrote: Does anyone have any ideas on how I can get pychecker to work? Create a file in your home directory called .pydistutils.cfg (yes, the first dot is important). Put the following text (between the two #-comment lines) into it: # Begin File [install] install-purelib=/Library/Python/2.3 install-platlib=/Library/Python/2.3 install-scripts=/usr/local/bin install-data=/usr/local/share # End File Now reinstall pychecker. Do this instead: # Begin File [install] install-scripts=/usr/local/bin install-data=/usr/local/share # End File Screwing with purelib and platlib is a terrible idea if you ever have multiple versions of Python installed, because they will all use the same .pydistutils.cfg. The standard Python 2.3.0 already puts its purelib and platlib there anyway (indirectly via symlink, but it still goes there), so it's not ever going to actually do anything helpful. -bob Argh.../usr/local/bin wasn't in my path. I also did the .pydistutils.cfg. Reinstalled pychecker, and it works now. Thanks for the help. Mike ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Some question about pyobjc and creating nib based application...
On Jan 4, 2005, at 7:42 PM, whamoo wrote:
On 04/gen/05, at 19:33, Bob Ippolito wrote:
I've tried xcode template, but if I modify the AppDelegate nib and add the function in python file, it give me this error:
Could not connect the action change_: to target of class provaDocument
Did you actually write "change_:" as the selector? That's not how it works. Underscores are used from Python and colons are used from Objective-C. Maybe you should read . The selector should be named "change:" in this case. Also, your source example does not define any class named "provaDocument".
Sorry, my mail was a little confusing, I'm able to build working program with nib starting by interface builder, in this case all works fine, no problem pyobjc is great, but I'm not able to use xcode template, because I'm so stupid
Step by step:
I create a new cocoa-python application "hello world"
open MainMenu.nib
click on window
put in the windows a button and a label
ok, then there is a helloworldAppDelegate class in IB and a helloworldAppDelegate.py in xcode
in IB i add two outlet and change: action to helloworldAppDelegate, connect the two outlet to the class and the action to the button.
Save the interface
Go to helloworldAppDelegate.py, inside it i found:
from Foundation import NSLog
from PyObjCTools import NibClassBuilder
NibClassBuilder.extractClasses("MainMenu")
class provaAppDelegate(NibClassBuilder.AutoBaseClass):
def applicationDidFinishLaunching_(self, aNotification):
NSLog( "Application did finish launching." )
I have added:
def change_(self, sender):
print "hello"
Build all, launch and read this:
Could not connect the action change: to target of class helloworldAppDelegate
Well the class names you are talking about are different from the class name defined in that Python file. Where the heck is this "prova" coming from? I have no idea what you are doing or not doing. I am sorry but I do not know how to help you.
Note that there was a bug at some point with Xcode projects that have a space in their name, but I thought that got fixed. I rarely ever use the Xcode template personally, they mostly just get in my way and cause extra maintenance hassle.
-bob
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Some question about pyobjc and creating nib based application...
On 04/gen/05, at 19:33, Bob Ippolito wrote:
I've tried xcode template, but if I modify the AppDelegate nib and add the function in python file, it give me this error:
Could not connect the action change_: to target of class provaDocument
Did you actually write "change_:" as the selector? That's not how it works. Underscores are used from Python and colons are used from Objective-C. Maybe you should read . The selector should be named "change:" in this case. Also, your source example does not define any class named "provaDocument".
Sorry, my mail was a little confusing, I'm able to build working program with nib starting by interface builder, in this case all works fine, no problem pyobjc is great, but I'm not able to use xcode template, because I'm so stupid
Step by step:
I create a new cocoa-python application "hello world"
open MainMenu.nib
click on window
put in the windows a button and a label
ok, then there is a helloworldAppDelegate class in IB and a helloworldAppDelegate.py in xcode
in IB i add two outlet and change: action to helloworldAppDelegate, connect the two outlet to the class and the action to the button.
Save the interface
Go to helloworldAppDelegate.py, inside it i found:
from Foundation import NSLog
from PyObjCTools import NibClassBuilder
NibClassBuilder.extractClasses("MainMenu")
class provaAppDelegate(NibClassBuilder.AutoBaseClass):
def applicationDidFinishLaunching_(self, aNotification):
NSLog( "Application did finish launching." )
I have added:
def change_(self, sender):
print "hello"
Build all, launch and read this:
Could not connect the action change: to target of class helloworldAppDelegate
Then I hit the wall with my face a lot of time
The same thing using only IB work fine =)
So, where is my stupid error? I've read the documentation =)
Whamoo www.rknet.it
Powered by:
- MacOsX
- Gnu / Linux Debian Sarge
- Amiga Os 3.9
- Milk
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] .pydistutils.cfg (was: pychecker)
On Jan 4, 2005, at 4:17 PM, Jack Jansen wrote: On 4-jan-05, at 14:42, Bob Ippolito wrote: On Jan 4, 2005, at 8:09 AM, Jack Jansen wrote: I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it. It has some more features in Python 2.4, you can use it to add new build command packages to distutils out-of-tree (like py2app, bdist_mpkg, etc.). Of course, very few distutils extensions are implemented in away that is compatible with this new feature, but it's there and I'll probably end up making py2app and bdist_mpkg compatible. Interesting... Although: you only need py2app and bdist_mpkg on the supplier-side (right?), so it doesn't really buy us all that much except a bit of convenience. If you want to create redistributable Mac applications, even "applets", then you are a "supplier". So I think it does buy *something* in this case, but not much. It saves you a line or two per setup.py, because right now py2app and bdist_mpkg jigger themselves into distutils by monkeypatch on import like py2exe does. Another thing that would be nice is to have some admin-writable place to put header files (in addition to Python's own headers) too. But that would require a patch to distutils and might need to happen in the 2.5 tree. [EVIL GRIN] What happens if we set both "include_dirs" and "headers" to, say, /Library/Python/2.3/python-includes in distutils.cfg? We'd need a bit of extra glue for PackMan binary installs (so it sends include files there too), but if this would cause include files to be installed there *and* that directory added to the -I flags we'd be all set, I think... If the person who created the package had it set that way, it would already work like that.. since it isn't done by symlink, it should show up in what bdist_dumb will create. -bob ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] .pydistutils.cfg (was: pychecker)
On 4-jan-05, at 14:42, Bob Ippolito wrote: On Jan 4, 2005, at 8:09 AM, Jack Jansen wrote: I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it. It has some more features in Python 2.4, you can use it to add new build command packages to distutils out-of-tree (like py2app, bdist_mpkg, etc.). Of course, very few distutils extensions are implemented in away that is compatible with this new feature, but it's there and I'll probably end up making py2app and bdist_mpkg compatible. Interesting... Although: you only need py2app and bdist_mpkg on the supplier-side (right?), so it doesn't really buy us all that much except a bit of convenience. Then I looked at the distutils code, and noticed that there's also an optional distutils.cfg inside the package. So that made me wonder: we could install a symlink in /System/yaddayaddayadda/lib/python2.3/distutils/distutils.cfg that points to, say, /Library/Python/2.3/distutils.cfg, and put an (admin-editable) file there that directs scripts tot the right place system wide (/usr/local/bin by default, probably). +1 on the idea +1 for /usr/local/bin as the "right place" Not so sure about install-data pointing to /usr/local/share (earlier on in the thread), because some packages might try and locate their data files using means other than distutils (sys.prefix relative). Yeah, I was wondering about that one too. I'll leave it out, if the end user wants it s/he can edit the file. Another thing that would be nice is to have some admin-writable place to put header files (in addition to Python's own headers) too. But that would require a patch to distutils and might need to happen in the 2.5 tree. [EVIL GRIN] What happens if we set both "include_dirs" and "headers" to, say, /Library/Python/2.3/python-includes in distutils.cfg? We'd need a bit of extra glue for PackMan binary installs (so it sends include files there too), but if this would cause include files to be installed there *and* that directory added to the -I flags we'd be all set, I think... -- Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] Python 2.3->2.4 "compatibility" package for Mac OS X 10.2
Is there a Mac OS X 10.2-compatible installer for the Python 2.3->2.4 "compatibility" package? When I double-click on the package from http://undefined.org/python/Python23Compat.zip it tells me that Mac OS X 10.3 is required. Thanks! - Bob Swerdlow ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Some question about pyobjc and creating nib based application...
On Jan 4, 2005, at 1:20 PM, whamoo wrote:
Hello,
There's somethings i cannot understand about creating nib based
application,
Ok I start interface builder, build gui, create outlet, create action,
saving, create python file starting by the nib, and having a thing
like this:
--
import objc
from Foundation import *
from AppKit import *
from PyObjCTools import NibClassBuilder, AppHelper
NibClassBuilder.extractClasses("MainMenu")
# class defined in gino.nib
class finestra(NibClassBuilder.AutoBaseClass):
# the actual base class is NSObject
# The following outlets are added to the class:
# button
# label
def change_(self, sender):
self.label.setStringValue_("Prova")
if __name__ == "__main__":
AppHelper.runEventLoop()
--
Ok, finestra is the base class and all works, but why is the base
class? if i create more class??
BTW: You should name your classes LikeThis, it is both Python and
Objective-C convention.
finestra is not "the base class". When you use
NibClassBuilder.AutoBaseClass, you are saying "ask the nib what my base
class is". For more information, see
I've tried xcode template, but if I modify the AppDelegate nib and add
the function in python file, it give me this error:
Could not connect the action change_: to target of class provaDocument
Did you actually write "change_:" as the selector? That's not how it
works. Underscores are used from Python and colons are used from
Objective-C. Maybe you should read
. The selector should be
named "change:" in this case. Also, your source example does not
define any class named "provaDocument".
And i don't know why =P
Did you read the documentation? I spent a lot of time on it before the
1.2 release ;)
I need to know what is the base class, i can chose? There's somethings
that I probably miss, someone can help?
Hopefully this question will be answered by the referenced
documentation...
-bob
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] Some question about pyobjc and creating nib based application...
Hello,
There's somethings i cannot understand about creating nib based
application,
Ok I start interface builder, build gui, create outlet, create action,
saving, create python file starting by the nib, and having a thing like
this:
--
import objc
from Foundation import *
from AppKit import *
from PyObjCTools import NibClassBuilder, AppHelper
NibClassBuilder.extractClasses("MainMenu")
# class defined in gino.nib
class finestra(NibClassBuilder.AutoBaseClass):
# the actual base class is NSObject
# The following outlets are added to the class:
# button
# label
def change_(self, sender):
self.label.setStringValue_("Prova")
if __name__ == "__main__":
AppHelper.runEventLoop()
--
Ok, finestra is the base class and all works, but why is the base
class? if i create more class??
I've tried xcode template, but if I modify the AppDelegate nib and add
the function in python file, it give me this error:
Could not connect the action change_: to target of class provaDocument
And i don't know why =P
I need to know what is the base class, i can chose? There's somethings
that I probably miss, someone can help?
Thanks a lot.
Whamoo www.rknet.it
Powered by:
- MacOsX
- Gnu / Linux Debian Sarge
- Amiga Os 3.9
- Milk
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] .pydistutils.cfg (was: pychecker)
On 4-jan-05, at 14:51, Bob Ippolito wrote: On Jan 4, 2005, at 8:42 AM, Bob Ippolito wrote: On Jan 4, 2005, at 8:09 AM, Jack Jansen wrote: I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it. It has some more features in Python 2.4, you can use it to add new build command packages to distutils out-of-tree (like py2app, bdist_mpkg, etc.). Of course, very few distutils extensions are implemented in away that is compatible with this new feature, but it's there and I'll probably end up making py2app and bdist_mpkg compatible. Then I looked at the distutils code, and noticed that there's also an optional distutils.cfg inside the package. So that made me wonder: we could install a symlink in /System/yaddayaddayadda/lib/python2.3/distutils/distutils.cfg that points to, say, /Library/Python/2.3/distutils.cfg, and put an (admin-editable) file there that directs scripts tot the right place system wide (/usr/local/bin by default, probably). +1 on the idea +1 for /usr/local/bin as the "right place" same here. Not so sure about install-data pointing to /usr/local/share (earlier on in the thread), because some packages might try and locate their data files using means other than distutils (sys.prefix relative). I have never seen one of these packages, but god knows one has to exist. In my experience, most packages seem to use install-data for documentation and maybe example code if anything. Another thing that would be nice is to have some admin-writable place to put header files (in addition to Python's own headers) too. But that would require a patch to distutils and might need to happen in the 2.5 tree. install-headers in distutils.cfg + a patch to the Makefile should do it, e.g. set install-headers to /Library/Python/2.3/Headers and add '-I/Library/Python/2.3/Headers' to CPPFLAGS in config/Makefile. Ronald ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] .pydistutils.cfg (was: pychecker)
On Jan 4, 2005, at 8:42 AM, Bob Ippolito wrote: On Jan 4, 2005, at 8:09 AM, Jack Jansen wrote: I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it. It has some more features in Python 2.4, you can use it to add new build command packages to distutils out-of-tree (like py2app, bdist_mpkg, etc.). Of course, very few distutils extensions are implemented in away that is compatible with this new feature, but it's there and I'll probably end up making py2app and bdist_mpkg compatible. Then I looked at the distutils code, and noticed that there's also an optional distutils.cfg inside the package. So that made me wonder: we could install a symlink in /System/yaddayaddayadda/lib/python2.3/distutils/distutils.cfg that points to, say, /Library/Python/2.3/distutils.cfg, and put an (admin-editable) file there that directs scripts tot the right place system wide (/usr/local/bin by default, probably). +1 on the idea +1 for /usr/local/bin as the "right place" Not so sure about install-data pointing to /usr/local/share (earlier on in the thread), because some packages might try and locate their data files using means other than distutils (sys.prefix relative). I have never seen one of these packages, but god knows one has to exist. In my experience, most packages seem to use install-data for documentation and maybe example code if anything. Another thing that would be nice is to have some admin-writable place to put header files (in addition to Python's own headers) too. But that would require a patch to distutils and might need to happen in the 2.5 tree. -bob ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] .pydistutils.cfg (was: pychecker)
On Jan 4, 2005, at 8:09 AM, Jack Jansen wrote: I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it. It has some more features in Python 2.4, you can use it to add new build command packages to distutils out-of-tree (like py2app, bdist_mpkg, etc.). Of course, very few distutils extensions are implemented in away that is compatible with this new feature, but it's there and I'll probably end up making py2app and bdist_mpkg compatible. Then I looked at the distutils code, and noticed that there's also an optional distutils.cfg inside the package. So that made me wonder: we could install a symlink in /System/yaddayaddayadda/lib/python2.3/distutils/distutils.cfg that points to, say, /Library/Python/2.3/distutils.cfg, and put an (admin-editable) file there that directs scripts tot the right place system wide (/usr/local/bin by default, probably). +1 on the idea +1 for /usr/local/bin as the "right place" Not so sure about install-data pointing to /usr/local/share (earlier on in the thread), because some packages might try and locate their data files using means other than distutils (sys.prefix relative). I have never seen one of these packages, but god knows one has to exist. In my experience, most packages seem to use install-data for documentation and maybe example code if anything. -bob ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] .pydistutils.cfg (was: pychecker)
Gosh, I'd never even heard of .pydistutils.cfg. I've added a note to the FAQ pointing to it. Then I looked at the distutils code, and noticed that there's also an optional distutils.cfg inside the package. So that made me wonder: we could install a symlink in /System/yaddayaddayadda/lib/python2.3/distutils/distutils.cfg that points to, say, /Library/Python/2.3/distutils.cfg, and put an (admin-editable) file there that directs scripts tot the right place system wide (/usr/local/bin by default, probably). -- Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations
On Jan 4, 2005, at 5:56 AM, Jack Jansen wrote: On 3 Jan 2005, at 23:40, Bob Ippolito wrote: Most people on Mac OS X have a lot of memory, and Mac OS X generally does a good job about swapping in and out without causing much of a problem, so I'm personally not very surprised that it could go unnoticed this long. *Except* when you're low on free disk space. 10.2 and before were really bad with this, usually hanging the machine, 10.3 is better but it's still pretty bad when compared to other unixen. It probably has something to do with the way OSX overcommits memory and swapspace, for which it apparently uses a different algorithm than FreeBSD or Linux. I wouldn't be surprised if the bittorrent problem report in this thread was due to being low on diskspace. And that could also be true for the original error report that sparked this discussion. I was able to trigger this bug with a considerable amount of free disk space using a laptop that has 1GB of RAM, although I did have to increase the buffer size from the given example quite a bit to get it to fail. After all, a 32-bit process can't have more than 4 GB of addressable memory. I am pretty sure that OS X is never supposed to overcommit memory. The disk thrashing probably has a lot to do with the fact that Mac OS X will grow and shrink its swap based on demand, rather than having a fixed size swap partition as is common on other unixen. I've never seen the problem myself, though. From what I remember about Linux, its malloc implementation merely increases the address space of a process. The actual allocation will happen when you try and access the memory, and if it's overcommitted things will fail in a bad way. -bob ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] Re: [Python-Dev] Darwin's realloc(...) implementation never shrinks allocations
On 3 Jan 2005, at 23:40, Bob Ippolito wrote: Most people on Mac OS X have a lot of memory, and Mac OS X generally does a good job about swapping in and out without causing much of a problem, so I'm personally not very surprised that it could go unnoticed this long. *Except* when you're low on free disk space. 10.2 and before were really bad with this, usually hanging the machine, 10.3 is better but it's still pretty bad when compared to other unixen. It probably has something to do with the way OSX overcommits memory and swapspace, for which it apparently uses a different algorithm than FreeBSD or Linux. I wouldn't be surprised if the bittorrent problem report in this thread was due to being low on diskspace. And that could also be true for the original error report that sparked this discussion. -- Jack Jansen, <[EMAIL PROTECTED]>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
