dh_auto_test failure with pybuild due to missing PYTHONPATH

I'm trying to package git-pw, and running the test suite fails like this: dh_auto_test -O--buildsystem=pybuild I: pybuild base:217: cd /build/git-pw-2.0.0/.pybuild/cpython3_3.8_git-pw/build; python3.8 -m pytest tests === test session starts

Example package using python3-pbr and Sphinx documentation with manual page

I'm trying to package pwclient, which depends on python3-pbr and has a rudimentary manual page generated from Sphinx documentation. Is there a similar example package which I can look at, to see how to trigger the manual page generation? I currently get this: dh_sphinxdoc: warning: Sphinx docume

Emacs python-mode confusion

Apparently, there are two different versions of python-mode floating around. From my perspective, they mainly differ in that the one in Emacs 22 doesn't come with the extremely handy "C-c C-c executes the file in a Python interpreter" shortcut. I think the version in python-mode provides this fun

Re: when and why did python(-minimal) become essential?

* Matt Zimmerman: > One of the appealing things about the Python language is their "batteries > included" philosophy: users can assume that the standard library is > available, documentation and examples are written to the full API, etc. Would this really be a problem if the minimal Python implem

Re: question on having . as LOAD_PATH (ruby)

* Junichi Uekawa: > Hi perl and pyhton people, > > Sorry for the crosspost; contrary to what's said in perl-policy and > python-policy, '.' seems to be included in module search-path. I find > it uneasy considering we have quite a few tools running as root. Is > this intentional or unintentional?

Re: Python-2.1 becoming Debian's default Python version

Gregor Hoffleit <[EMAIL PROTECTED]> writes: > I think we do agree that the License of Python 2.1.1, according to the > FSF, is compatible with the GPL ? Yes! > This section is incorrect, in that Python 1.6.1 has yet another > different license. It should read something like > > The License of

Re: Python-2.1 becoming Debian's default Python version

Gregor Hoffleit <[EMAIL PROTECTED]> writes: >> > Python 1.6.1 is essentially the same as Python 1.6, with a few minor >> > bug fixes, and with a different license that enables later versions >> > to be GPL-compatible. >> >> The license claims to be GPL compatible, but according to the

Re: Python-2.1 becoming Debian's default Python version

Neil Schemenauer <[EMAIL PROTECTED]> writes: > It's probably better to check if you're unsure rather than speculate or > guess. From the 2.1.1 LICENCE file: > > Python 1.6.1 is essentially the same as Python 1.6, with a few minor > bug fixes, and with a different license that enables late

Re: python-2.1 for unstable?

Gregor Hoffleit <[EMAIL PROTECTED]> writes: > > This is probably correct, but it is completely irrelevant in our case. > > Some parts of Python 2.1 are still covered by the GPL-incompatible > > CNRI license, so Python 2.1 as a whole is not GPL compatible. > > I'm glad to correct you, but accordin

Re: python-2.1 for unstable?

Matthias Klose <[EMAIL PROTECTED]> writes: > Florian Weimer writes: > > This is probably correct, but it is completely irrelevant in our case. > > Some parts of Python 2.1 are still covered by the GPL-incompatible > > CNRI license, so Python 2.1 as a whole is not

Re: python-2.1 for unstable?

Gregor Hoffleit <[EMAIL PROTECTED]> writes: > I talked to RMS, Eben Moglen and GvR. The bad news: According to RMS+Moglen, > the license used in Python 2.1 still is not yet compatible with the GPL. The > good news: The PSF decided to drop the choice of law clause. A modified > license is in CVS, a

Re: Python 2.1 out

Neil Schemenauer <[EMAIL PROTECTED]> writes: > Guido has recently checked in a license change that makes Python > GPL compatible. Here's the diff: Index: LICENSE === RCS file: /cvsroot/python/python/dist/src/LICENSE,v retrieving rev

Re: Python 2.1 out

Gregor Hoffleit <[EMAIL PROTECTED]> writes: [Python warning messages] > Could you mail an example of such a message ? y = None def fun(): y = None def bar(): y bar() fun() results in: :2: SyntaxWarning: local name 'y' in 'fun' shadows use of 'y' as global in nested scope

Re: Python 2.1 out

D-Man <[EMAIL PROTECTED]> writes: > On Wed, Apr 18, 2001 at 10:25:52PM +0200, Florian Weimer wrote: > | Steve Purcell <[EMAIL PROTECTED]> writes: > | > | > Licenses aside, there are the same technical issues with Python 2.1 > | > as with Python 2.0. > |

Re: Python 2.1 out

Steve Purcell <[EMAIL PROTECTED]> writes: > Licenses aside, there are the same technical issues with Python 2.1 > as with Python 2.0. Python 2.1 seems to print some diagnostic messages during run-time; this might affect scripts which are invoked in cron jobs.

Re: Do we prefer Tk8.0 or 8.2 ? (for python-tk, that is)

Gregor Hoffleit <[EMAIL PROTECTED]> writes: > Do we prefer our packages to use tk8.2 or on tk8.0 ? I'd like to suggest to keep Tk 8.0. That is what is usually used by Python on most if not all platforms, and it is well-tested.