Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #89734 > unrolled thread

Re: GAE environment differences

Started byPeter Otten <__peter__@web.de>
First post2015-05-01 15:31 +0200
Last post2015-05-01 15:31 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: GAE environment differences Peter Otten <__peter__@web.de> - 2015-05-01 15:31 +0200

#89734 — Re: GAE environment differences

FromPeter Otten <__peter__@web.de>
Date2015-05-01 15:31 +0200
SubjectRe: GAE environment differences
Message-ID<mailman.16.1430487075.3347.python-list@python.org>
Chris Angelico wrote:

> On Fri, May 1, 2015 at 11:04 PM, Robin Becker <robin@reportlab.com> wrote:
>>>   File "python2.7/posixpath.py", line 268, in expanduser
>>>     import pwd
>>> ```
>>
>> the user suggests that even though claims are made that you can use a
>> filesystem, but stuff like pwd is missing. Apparently the user module has
>> no meaning, but there is a users module? I guess I'll need to keep
>> patching reportlab when GAE users find these glitches.
> 
> According to my Python installation, the pwd module is built-in. But
> you could bypass its usage by making sure $HOME is set before calling
> expanduser.
> 
> What happens if you fire up Python and just type "import pwd"? Does
> that work? If not, does it give any more useful error message?

I found (guess how)

https://cloud.google.com/appengine/kb/libraries

which states:

"""
As a result, these are the C modules that are not usable with the Python 2.7 
runtime:

ctypes
sqlite
ssl/_ssl
fcntl
spwd
pwd
grp
syslog
select
_socket
"""

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web