On Jun 14, 2011, at 07:00 PM, Ben Finney wrote: >I think (as someone with no special authority on Python nor Debian) that >the people who know most detail about what's painful for packaging >Python software for Debian are burned out on the topic. They therefore >don't want to spend the effort to summarise the problems, nor to verify >whether they're still problems in current versions. If that's true, it's sad, but understandable. It happens in many communities. The shame of it is that the people who get most burned out are exactly the people with the most valuable experiences and best institutional knowledge on what's wrong and how to fix it. >If that's not true I'd love for your question to be answered in detail >and documented publicly, of course. > >But if it is true, and the people who know the answer aren't motivated >to work on answering your question, I think someone (perhaps you) will >need to go over a lot of already-trod ground to discover what's still >painful and why, in order to get those details documented. Blog references, email threads, or other links to existing artifacts would be very helpful. Has anybody ever written a "What's Wrong With Python and How It Hurts Debian" article? -Barry
Attachment:
signature.asc
Description: PGP signature