Urgent Question about Python licensing

[Dave LeBlanc]

Hi;

While reading up on the recent Python conference on O'Reilly's site
(http://python.oreilly.com/news/pythonday1_0301.html - actually on the
'day 2' page), I cam across the following:
----------------------------------------------------
"Some hurdles that still lie ahead for Python: Python's license is
still stuck between the Scylla of risk-averse CNRI and the Charybdis
of unbending Richard Stallman. The license that CNRI agreed to for
Python 1.6 was approved by the Open Source Initiative (OSI), but the
Free Software Foundation still objects to one small clause. 

Because later versions of Python are built on 1.6, they too are
affected by this license problem. This difficulty means that Python
can't be distributed with software licensed under the GPL. Discussions
continue between CNRI and FSF, and progress is being made; but as
Guido asked during the keynote: When will it end?"
----------------------------------------------------

My questions are these:
1. What prevents Python and GPL code from being distributed together?
If I write some Python code that drives a GPL'd app (but  which does
not depend on that app), what prevents me from offering both my python
code and the GPL'd app on the same medium (disk/CD/web)?

2. Is it currently so, or will Python end up with, some license that
requires that python scripts be covered by the GPL?

3. Is Python 2.0 covered by that evil CNRI 1.6 license? I avoided 1.6
mostly because of the license, and thought that 2.0 had "skipped" 1.6
and used a far more equitable license then the 1.6 one. (1.6's license
permits the copyright holder to suddenly decide that anyone using the
covered software must pay a fee (or any other thing they so desire -
this is only an example), and by virtue of your even so much as having
read the license are implicitly bound to their unilateral declaration
- lovely Virginia laws).

Regards,

Dave LeBlanc