Lawrence D'Oliveiro wrote:
> .. I expect an apology.
> Otherwise, it becomes grounds for an abuse complaint to your ISP.
>
Yes, I do apologize profusely and publicly, and would have done so
regardless of threat.
I had trouble with posts making it through to the list and so was also
posting in
Aahz wrote:
> ... That seems to demonstrate that regrtest.py is indeed a good mechanism for
> finding out whether it's a b0rked install!
>
I agree that regrtest.py looks a good mechanism. It just appears that
`apt-get install python` on Debian and Ubuntu brings no tests with it.
@Lawrence D'Ol
Aahz wrote:
>
> What directory are you running this from? What happens if you switch to
> running "python Lib/test/regrtest.py"? Taking a closer look, this looks
> more like a plain import error.
>
Thank you for your suggestion.
I couldn't do quite that because there's no Lib, but inste
Aahz wrote:
> How important is the apt-get requirement?
That's a significant point, thank you. Two parts to the response:
a) I don't feel that I am sufficiently expert to launch into compilation
of Python if I can avoid it.
b) I hope that I can put all platform risk into the lap of the hosting
How do I assure myself of the integrity of a Python installation
acquired using apt-get install on Debian and Ubuntu?
I can run regrtest but there's nothing in the basic installation to run,
viz.:
geg...@gegard:~$ python
Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52)
[GCC 4.2.3 (Ubuntu 4.2.3-2u
