Re: [Pyobjc-dev] Achieving 1.0....
Brought to you by:
ronaldoussoren
From: Bill B. <bb...@co...> - 2002-10-22 20:47:16
|
Agreed. The differences between 0.6.1 and 0.7.0 are huge and the visibility for the module within the dev community is going to grow quite a bit in the near future [I hope -- will say more when I know more]. How about a feature freeze -- fix the bugs we have right now that are relatively major [dictionary / array allocation, the instance identification] and add unit tests to ensure that whatever we ship as 0.7.0 (or whatever) is relatively solid? I'm pretty happy with the latest incarnation of bin-python-main.m -- need to commit a new version and update the python project template -- as it has proven to not be problematic in the production app I'm working on. It now supports standalone builds with frameworks (dynamically loading frameworks with @executable_path as their install_name AND dependencies on other frameworks w/@executable_path requires some fun to be had with the environment variables of the execve() process). I'll try to re-address the documentation on the examples that use Project Builder and put together a README for the Project Template stuff. b.bum On Tuesday, October 22, 2002, at 04:40 PM, Ronald Oussoren wrote: >> [This is not a request to do a 1.0 release without an official >> interim release -- just some planning for the real live 1.0] > Speaking of interim releases... Now that people are getting > interrested in PyObjC it would be better to get one out sometime soon. |