Right, but this kind of problem is also one of the major reasons I tend to harp on about the fact that the commercial redistributors active in the Python community aren't contributing as effectively as they could be, and their existing customers aren't holding them accountable for the failure. Python's origins as a "scripting language for Linux" means it is often still perceived that way in the commercial sector and treated accordingly, even though it has subsequently matured into a full-fledged cross-platform application development and data analysis platform.

Even those of us already working for redistributors can't readily provide that missing accountability, as any reasonable business is going to weigh the costs of additional investment in any given area against the potential for increased future revenue. That means the most effective pressure comes from industry partners, governments, existing customers, and credible potential customers (i.e. folks that have the ability to affect redistributor revenue directly) rather than from redistributor staff or community volunteers (as we're pretty much limited to using risk management and hiring pipeline based lines of argument, rather than being able to push the "future revenue potential" line directly).

Cheers,

Nick.

--