Re: [Pyobjc-dev] GNUstep.
Brought to you by:
ronaldoussoren
From: Ronald O. <ous...@ci...> - 2003-01-06 06:58:35
|
On Sunday, Jan 5, 2003, at 19:19 Europe/Amsterdam, bb...@ma... wrote: > Wow! I'm really happy to see that the GNUstep effort has such > momentum. Very cool! I'm going to add a news item to that effect > shortly. > > I'm thinking that it might be wise to start a pyobjc-dev-gnustep > mailing list as the GNUstep effort is going to generate a lot of > traffic that is highly specific in nature. It would give people new > to the project an easy way to scan the archives to find relevant notes > regarding the state of GNUstep compatibility. I don't think this is worth the effort. Porting to GNUstep is likely to generate a lot of specific traffic, but only for a short time. After that people on GNUstep will have the same questions as those on MacOS. BTW. Is there anyone that is still using NeXTstep and is interested in using PyObjC? Porting to NeXTstep shouldn't be too much of an effort ;-) ;-) > > Also-- for those working on GNUstep, there are a couple (maybe only > one now?) of places where the PyObjC module does something like the > following (found in objc/__init__.py): > > try: > import _FoundationMapping > del _FoundationMapping > except ImportError: > pass We might as wel remove the try:except: block. I had what I thought was a good reason for doing it this way, but I forgot was it is. > > As the port progresses, it is likely that an import error will occur > in this context that is indicative of a real problem. It is also likely that there is a real problem when this occurs on MacOS X. Ronald |