$HOSTNAME not in os.environ?

2006-09-01 Thread slinkp 
Can anybody explain this one?

[EMAIL PROTECTED] ~ $ python
Python 2.4.3 (#1, Jul 27 2006, 13:07:44)
[GCC 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.environ['HOSTNAME']
Traceback (most recent call last):
  File "", line 1, in ?
  File "/usr/lib64/python2.4/UserDict.py", line 17, in __getitem__
def __getitem__(self, key): return self.data[key]
KeyError: 'HOSTNAME'
>>> print os.getenv('HOSTNAME')
None
>>>
[EMAIL PROTECTED] ~ $ echo $HOSTNAME
kermit
[EMAIL PROTECTED] ~ $ uname -a
Linux kermit 2.6.17-gentoo-r4amd64-preempt-noapic #1 PREEMPT Thu Jul 27
12:56:53 EDT 2006 x86_64 AMD Athlon(tm) 64 Processor 3500+ GNU/Linux


i-swear-it-used-to-be-there-ly-y'rs,

Paul Winkler

-- 
http://mail.python.org/mailman/listinfo/python-list

Re: $HOSTNAME not in os.environ?

2006-09-01 Thread slinkp 
Grant Edwards wrote:
> On 2006-09-01, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Can anybody explain this one?
>
>  print os.getenv('HOSTNAME')
> > None
> 
> > [EMAIL PROTECTED] ~ $ echo $HOSTNAME
> > kermit
>
> Perhaps the HOSTNAME variable isn't exported?

Aha. Right you are.  Thanks!

- PW

-- 
http://mail.python.org/mailman/listinfo/python-list

Python 2 releases after 2.6

2007-09-11 Thread slinkp 
This seems to be a bit of a FAQ (at least among worried Zope
developers  :-) ...
What  are the plans for Python 2 releases after Python 2.6 / Python 3
are released?

First, in the 2006 State of Python, Guido said:

"""
# 2.7: likely; may contain some 3.0 backports
# 2.9 is as far as we'll go (running out of digits :-)
"""

Then there's PEP 3000, which says:
"""
I expect that there will be parallel Python 2.x and 3.x releases for
some time; the Python 2.x releases will continue for a longer time
than the traditional 2.x.y bugfix releases. Typically, we stop
releasing bugfix versions for 2.x once version 2.(x+1) has been
released. But I expect there to be at least one or two new 2.x
releases even after 3.0 (final) has been released, probably well into
3.1 or 3.2. This will to some extent depend on community demand for
continued 2.x support, acceptance and stability of 3.0, and volunteer
stamina.
"""

Has any of that changed (insofar as anyone can predict the future of
course)?

Thanks,

-PW

-- 
http://mail.python.org/mailman/listinfo/python-list