PyObjC

On Mar 21, 2005, at 2:54 PM, Scott Johnston wrote:

> Okay, so I probably shouldn't be trying beta1.3 with a dumb question 
> like this:
> What do I need to REMOVE to get the 1.3 installation to work?
> I have trouble getting examples to "python setup.py py2app" due to a 
> problem with py2app.

Yes, there are problems if you have sufficiently old versions of PyObjC 
(pre-1.2) and py2app (pre-0.1.6) installed.  You had both, so it went 
BOOM.

The installer used to remove files to attempt to work around such 
problems, but I removed that functionality because if a bad thing 
happens (i.e. during development) then you could possibly lose a big 
chunk of the files on your drive (especially since the installer will 
probably run with root).

This problem is documented in http://undefined.org/python/py2app.html 
(you need to clobber several things, I think you listed them all) -- 
for PyObjC you should just need to clobber the PyObjC dir and 
PyObjC.pth.

-bob

I missed a few things in /usr/local/bin, but they were all replaced by 
items from the new install.
So far, things are running fine under 1.3.

Thanks!

-S

> This problem is documented in http://undefined.org/python/py2app.html 
> (you need to clobber several things, I think you listed them all) -- 
> for PyObjC you should just need to clobber the PyObjC dir and 
> PyObjC.pth.
>
> -bob
>

On 21-mrt-05, at 21:14, Bob Ippolito wrote:

>
> On Mar 21, 2005, at 2:54 PM, Scott Johnston wrote:
>
>> Okay, so I probably shouldn't be trying beta1.3 with a dumb question 
>> like this:
>> What do I need to REMOVE to get the 1.3 installation to work?
>> I have trouble getting examples to "python setup.py py2app" due to a 
>> problem with py2app.
>
> Yes, there are problems if you have sufficiently old versions of 
> PyObjC (pre-1.2) and py2app (pre-0.1.6) installed.  You had both, so 
> it went BOOM.
>
> The installer used to remove files to attempt to work around such 
> problems, but I removed that functionality because if a bad thing 
> happens (i.e. during development) then you could possibly lose a big 
> chunk of the files on your drive (especially since the installer will 
> probably run with root).

IMHO we should reintroduce this functionality. That code was very 
simple and I've never had problems with it, even during development.

It is rather annoying that users have to manually remove files before 
they can install a new version of pyobjc. Especially because MacOS X 
doesn't have a package uninstaller.

Ronald
--
X|support bv            http://www.xsupport.nl/
T:  +31 610271479       F:  +31 204416173

On Mar 22, 2005, at 3:40 AM, Ronald Oussoren wrote:

>
> On 21-mrt-05, at 21:14, Bob Ippolito wrote:
>
>>
>> On Mar 21, 2005, at 2:54 PM, Scott Johnston wrote:
>>
>>> Okay, so I probably shouldn't be trying beta1.3 with a dumb question 
>>> like this:
>>> What do I need to REMOVE to get the 1.3 installation to work?
>>> I have trouble getting examples to "python setup.py py2app" due to a 
>>> problem with py2app.
>>
>> Yes, there are problems if you have sufficiently old versions of 
>> PyObjC (pre-1.2) and py2app (pre-0.1.6) installed.  You had both, so 
>> it went BOOM.
>>
>> The installer used to remove files to attempt to work around such 
>> problems, but I removed that functionality because if a bad thing 
>> happens (i.e. during development) then you could possibly lose a big 
>> chunk of the files on your drive (especially since the installer will 
>> probably run with root).
>
> IMHO we should reintroduce this functionality. That code was very 
> simple and I've never had problems with it, even during development.
>
> It is rather annoying that users have to manually remove files before 
> they can install a new version of pyobjc. Especially because MacOS X 
> doesn't have a package uninstaller.

During a particular refactoring of bdist_mpkg, the additions that 
PyObjC used were not updated in lock-step, so if you were using trunk 
of both and did a bdist_mpkg install it would (attempt to) erase your 
harddrive.  I don't want to be responsible for making sure that every 
install is safe on every checkin.

-bob

On 22-mrt-05, at 17:00, Bob Ippolito wrote:

>
> On Mar 22, 2005, at 3:40 AM, Ronald Oussoren wrote:
>
>>
>> On 21-mrt-05, at 21:14, Bob Ippolito wrote:
>>
>>>
>>> On Mar 21, 2005, at 2:54 PM, Scott Johnston wrote:
>>>
>>>> Okay, so I probably shouldn't be trying beta1.3 with a dumb 
>>>> question like this:
>>>> What do I need to REMOVE to get the 1.3 installation to work?
>>>> I have trouble getting examples to "python setup.py py2app" due to 
>>>> a problem with py2app.
>>>
>>> Yes, there are problems if you have sufficiently old versions of 
>>> PyObjC (pre-1.2) and py2app (pre-0.1.6) installed.  You had both, so 
>>> it went BOOM.
>>>
>>> The installer used to remove files to attempt to work around such 
>>> problems, but I removed that functionality because if a bad thing 
>>> happens (i.e. during development) then you could possibly lose a big 
>>> chunk of the files on your drive (especially since the installer 
>>> will probably run with root).
>>
>> IMHO we should reintroduce this functionality. That code was very 
>> simple and I've never had problems with it, even during development.
>>
>> It is rather annoying that users have to manually remove files before 
>> they can install a new version of pyobjc. Especially because MacOS X 
>> doesn't have a package uninstaller.
>
> During a particular refactoring of bdist_mpkg, the additions that 
> PyObjC used were not updated in lock-step, so if you were using trunk 
> of both and did a bdist_mpkg install it would (attempt to) erase your 
> harddrive.  I don't want to be responsible for making sure that every 
> install is safe on every checkin.

I guess the proper way to solve this is writing or including a package 
uninstaller that can uninstall the packages created by bdist_mpkg.

Ronald

On Mar 23, 2005, at 2:44 AM, Ronald Oussoren wrote:

>
> On 22-mrt-05, at 17:00, Bob Ippolito wrote:
>
>>
>> On Mar 22, 2005, at 3:40 AM, Ronald Oussoren wrote:
>>
>>>
>>> On 21-mrt-05, at 21:14, Bob Ippolito wrote:
>>>
>>>>
>>>> On Mar 21, 2005, at 2:54 PM, Scott Johnston wrote:
>>>>
>>>>> Okay, so I probably shouldn't be trying beta1.3 with a dumb 
>>>>> question like this:
>>>>> What do I need to REMOVE to get the 1.3 installation to work?
>>>>> I have trouble getting examples to "python setup.py py2app" due to 
>>>>> a problem with py2app.
>>>>
>>>> Yes, there are problems if you have sufficiently old versions of 
>>>> PyObjC (pre-1.2) and py2app (pre-0.1.6) installed.  You had both, 
>>>> so it went BOOM.
>>>>
>>>> The installer used to remove files to attempt to work around such 
>>>> problems, but I removed that functionality because if a bad thing 
>>>> happens (i.e. during development) then you could possibly lose a 
>>>> big chunk of the files on your drive (especially since the 
>>>> installer will probably run with root).
>>>
>>> IMHO we should reintroduce this functionality. That code was very 
>>> simple and I've never had problems with it, even during development.
>>>
>>> It is rather annoying that users have to manually remove files 
>>> before they can install a new version of pyobjc. Especially because 
>>> MacOS X doesn't have a package uninstaller.
>>
>> During a particular refactoring of bdist_mpkg, the additions that 
>> PyObjC used were not updated in lock-step, so if you were using trunk 
>> of both and did a bdist_mpkg install it would (attempt to) erase your 
>> harddrive.  I don't want to be responsible for making sure that every 
>> install is safe on every checkin.
>
> I guess the proper way to solve this is writing or including a package 
> uninstaller that can uninstall the packages created by bdist_mpkg.

Which doesn't solve the actual problem - the package was reorganized 
before we used bdist_mpkg.

-bob