[Python-Dev] Closing outdated Mac issues

[Daniel (ajax) Diniz]

Hi Ned,

Ned Deily wrote:
> Other than Mac/Modules, the rest of the Mac/ directory is mainly stuff
> used for building or going into the OS X installer images, including
> things like IDLE.app.  These are used in 2.x and in 3.x.

Thanks, knowing that makes the ticket handling easier!

>> There are 40 C files, two headers and 69 python files in /Mac in
>> trunk. The 2.6 (and 2.5.x) docs say development has stopped and that
>> they'd be replaced in 2.5. So ISTM closing RFEs for these modules
>> would be an improvement.
>>
>> > Honestly, fixing them is fine but since the modules are deprecated but
>> > still in existence in 2.x, but they are definitely nothing above a
>> > normal priority issue.
>> OK, I'll let the bug reports open. What about RFEs?
>
> I think the reasonable thing to do is close them as "not to be
> fixed/implemented".  At this point, the chances that someone would fix
> them are pretty slim and, in many cases, I'm sure the module is either
> obsolete because other, and better supported, solutions are now
> available, like PyObjC or appscript.  If people feel strongly about an
> issue, they can always ask to re-open it.

OK, Ronald is helping sort them and I'll clean whatever is left based
on your combined feedback.

> Taking a quick look at your list, the only ones that may be worth
> looking at are the plistlib ones since it lives on in 3.x.  I think all
> the rest are deprecated and gone in 3.x.

OK, plistlib is a keeper in my list now.

Thanks a lot for the feedback (and for helping with the Mac installers!)  :)

Regards,
Daniel