This seems to be problem with shell.appspot.com (it tries to persist the DES object in session).
On 5 Maj, 23:53, Devel63 <danstic...@gmail.com> wrote: > Doesn't seem to work onhttp://shell.appspot.com > > I can import a module (e.g., from Crypto.Cipher import DES), but when > I try to use it I get all sorts of errors about not being able to > pickle it (e.g., obj=DES.new('abcdefgh', DES.MODE_ECB). I picked > those 2 lines (and others) because they are straight out of the > pycrypto examples. > > On May 5, 1:24 pm, Devel63 <danstic...@gmail.com> wrote: > > > OK, I hear what you all are saying: I need to install the libraries on > > my dev server, but not upload them to my workspace because they will > > already be accessible there. > > > However, I don't know why people on this thread keep saying that this > > is the way it works with all the other 3rd party libraries. To the > > contrary, antlr3, django v0.96, webob, and yaml ... everything else > > mentioned > > onhttp://code.google.com/appengine/docs/python/tools/libraries.html > > ... gets installed with the SDK under the lib directory. > > > I guess I can give it a go and see what happens, but it seems weird to > > me that Google would make a custom version, tell us it is not based on > > the latest release of the public version, and then not distribute it > > with the SDK as they have with every other incorporated library > > (unless there's some security reason not to do so). So I guess we > > have to get it working locally, then upload and hope that it works > > with their modified and reduced functionality module, which we have no > > way of examining beforehand. > > > On May 5, 12:57 pm, Wooble <geoffsp...@gmail.com> wrote: > > > > The libraries are installed on the App Engine production servers. > > > They are not part of the SDK, so they're not on your machine unless > > > you installed them, the same as the other third party libraries usable > > > with App Engine. > > > > On May 5, 1:38 pm, Devel63 <danstic...@gmail.com> wrote: > > > > > What?? How does this reconcile with the 1.2.1 announcement: > > > > > App Engine includes a custom version of the Python Cryptography > > > > Toolkit, also known as PyCrypto. > > > > The version included with App Engine is based on pycrypto 2.0.1. > > > > This is not the latest version, but > > > > should be largely compatible with more recent versions. > > > > > http://code.google.com/appengine/docs/python/tools/libraries.html > > > > > On May 5, 7:54 am, "Nick Johnson (Google)" <nick.john...@google.com> > > > > wrote: > > > > > > PyCrypto is a third-party library. If it is installed, it will be in > > > > > your Python install's site-packages directory, not under the App > > > > > Engine SDK. > > > > > > -Nick Johnson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
