Hi John, There a full thread about this in GitHub <https://github.com/Trii/NoseGAE/issues/6>. I believe that's the best place to follow this conversation. Please have a look at it.
Kind regards, Mario C. Google Cloud Platform. On Wednesday, February 11, 2015 at 5:09:24 AM UTC+1, John Louis Del Rosario wrote: > > From the NoseGAE readme: > > Due to changes in the sandboxing mechanisms in dev_appserver2, it isn't > possible for NoseGAE to simulate the deployed environment any longer. The > sandboxing feature had to be removed since there is no longer any way to > toggle it between noses own internal workings. > > This means that certain tests may pass locally but the code in question > will fail in production due to restricted modules and functions. As of now > there is no workaround but pull requests are welcome! > > That sounds like a pretty big deal? Doesn't the limitation defeat the > purpose of testing? What exactly are the restricted modules and functions > mentioned? > > I posted here instead of opening an issue on Github to start a discussion > on whether we should be concerned (we've been using NoseGAE from the > start), and what alternatives can we use if it is cause for concern. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/707b890e-7743-49a0-991d-bef0da431416%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
