Python Pre-release SDK 1.7.2 Is Out
230 views
Skip to first unread message
Bryce Cutt
Sep 14, 2012, 2:46:36 PM9/14/12
to google-a...@googlegroups.com
http://code.google.com/p/googleappengine/downloads/list
A ton of bug fixes in this one.
App Engine Python SDK - Release Notes
Version 1.7.2
===============================
- Paid applications can now upload Static files and Code > 1GB. Additional
storage will be billed at $0.13/GB per month. Free applications will
continue to be provided 1GB of storage at no charge. Free quota will apply
per application.
- PyCrypto 2.6 is now a GA feature for Python 2.7
- The Conversion API will be decommissioned soon. Developers using this API
will receive a warning message. Please find an alternative document
conversion/OCR service.
- You can now fetch Task Queue Statistics. This allows you to fetch
statistics and information about your task queue from within your
application. Statistics include information such as the number of tasks
in a queue, how many tasks were executed in the last minute and enforced
rate. This is an experimental feature.
- Added Timezone selection widget in Admin Console Admin Logs.
- Added a warning message about caching when modifying or deleting datastore
entities.
- Added a flush cache button to dev_appserver and Admin Console.
- Attempting to update multiple entity groups in a single transaction
in Datastore now throws an error suggesting to use XG transactions.
- Search API now has a string maximum length limit of 2000 characters.
- We now allow a user with multiple google accounts the ability to create an
app if they are an SMS verified user.
- A more useful error message now displays when a deployment fails
due to local date/time settings being improperly set.
- Cron Descriptions may now include non-ASCII characters.
- App Config Service Delete App Version Call Count quota raised to
10,000/day.
- Queries with transactions are now supported in Remote API.
- There are now more descriptive error messages for Datastore Admin
deadline exceeded errors in stack trace.
- Replaced error code “Administrators cannot be removed right now”
with a more descriptive message.
- Fixed an issue with namespace dropdown in Admin Console appearing blank
even though the URL specified namespace is correct.
- Fixed an issue where Model.get_by_id() returns none in dev_appserver
whereas this is not allowed in production.
- Fixed an issue with dev_appserver app_identity.get_default_version_hostname()
- Fixed an issue with mail service sendToAdmins() failing when using
multi-arg message constructor.
- Fixed an issue with dev_appserver for mimetypes.guess_type()
- Fixed an issue with runtime failing to use scope with OAuth under certain
conditions.
- Fixed an issue with AppConfigNotFound error.
- Fixed an issue with static path with + in dev_appserver.
- Fixed an issue with support for models with large numbers of properties in
Admin Console Dataviewer where previously the page would fail to render.
- Fixed an issue with multi-line string property not editing correctly
in Dataviewer.
- Fixed an issue with URLFetch mimetools.Message parsing incorrectly.
- Fixed an issue with the behavior of Expires header in dev_appserver
- Fixed an issue with Content-Disposition header being removed if filename
contains utf-8 characters.
- Fixed an issue with incoming Mail API where encoded headers failed to
decode.
- Fixed an issue with non-ascii text displaying incorrect values
when posted by URL created by blobstore.create_upload_url()
- Fixed an issue with using sendmail in Mail API.
- Fixed an issue with appcfg.py cron_info giving the wrong timezone information.
- Fixed an issue with Paging link in Datastore viewer not working with # or &
- Fixed an issue with rounding errors in crop image transform on dev_appserver.
- Fixed an issue with TypeError being incorrectly raised when attachment
has Character Set and Language Information.
- Fixed an issue with Mail API attachments in unicode failing
in_check_attachments()
- Fixed an issue with ereporter not reporting errors when applications
use namespaces.
- Fixed an issue with Dataviewer GQL stripping new lines after initial run
and a user paginates results.
- Fixed an issue with Python Unicode prefix in Datastore viewer.
- Fixed an issue with get_serving_url for images giving non-cacheable URLs
in dev_appserver.
- Fixed an issue with fancy_urllib using squid proxy server with
authentication.
- Fixed an issue with custom admin page not displaying when restricted to
only admins.
- Fixed an issue with dev_appserver_import_hook.py handling Crypto import
accounts.
- Fixed an issue with Remote API gzip compression for transmitted data.
- Fixed an issue with remote API shell not having pwd in Python Path.
- Fixed an issue with Admin Console Logs < 30 minutes not being available.
- Fixed an issue with Apps that are using Mail API reporting
“No Provider for address type rfc822” error.
- Fixed an issue with concurrent write access to Datastore stubs.
- Fixed an issue with Viewers being able to prohibit code downloads.
- Fixed an issue with billing applications that are disabled.
- Fixed an issue with deploying to an existing version
when an app has 10 versions.
- Fixed an issue with bulkloader “model” class not uploading correctly.
- Fixed an issue with TextProperty in Datastore viewer.
- Fixed an issue with appcfg.py request_logs failing with ~oauth2
- Fixed an issue with editing a bytestring field in Datastore viewer.
- Fixed an issue with dev_appserver clearing after restart. This is a
Windows only bug.
- Fixed an issue with Cron schedule failing on 1st day of month.
- Fixed an issue with gzip compression for application/plist content type.
- Fixed an issue with datetime.datetime.fromtimestamp() in python 2.7
Adam Sah
Sep 14, 2012, 3:58:50 PM9/14/12
to google-a...@googlegroups.com
holy mackerel!!! hats off on all the bugfixes, that's awesome!
Message has been deleted
PK
Sep 15, 2012, 2:37:27 AM9/15/12
to google-a...@googlegroups.com
Thanks for fixing all these bugs. I run all my tests and see no regressions. Using pycrypto 2.6 on Mountain Lion I was able to run for the first time in a long time without having to patch GAE!!! The next step is to remove workarounds for bugs you have fixed.
PK
Jason Collins
Sep 15, 2012, 11:46:28 AM9/15/12
to google-a...@googlegroups.com
"Attempting to update multiple entity groups in a single transaction in Datastore now throws an error suggesting to use XG transactions."
This is really unfortunate. So often, I see inexperienced devs slap an xg=True on something because of "suggestions" like this without understanding their data model or the implications.
I don't think it's wise to emit a message like this.
j
Jeff Schnitzer
Sep 16, 2012, 4:57:40 PM9/16/12
to google-a...@googlegroups.com
Bah. There are millions of decisions you make when building on GAE
which have all kinds of implications on performance and behavior. If
you have inexperienced devs which don't understand the implications of
the data model, you're going to have worse problems than transactions
that run slower than they otherwise would.
Requiring XG transactions to be explicitly enabled was an API design mistake.
Jeff
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/G5UG-1uMcQsJ.
>
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
which have all kinds of implications on performance and behavior. If
you have inexperienced devs which don't understand the implications of
the data model, you're going to have worse problems than transactions
that run slower than they otherwise would.
Requiring XG transactions to be explicitly enabled was an API design mistake.
Jeff
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/G5UG-1uMcQsJ.
>
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
timh
Sep 16, 2012, 7:01:10 PM9/16/12
to google-a...@googlegroups.com, je...@infohazard.org
Requiring explicit xg means preserving the current api and semantics. Which I would imagine
T
is the reason. xg transactions will fail if you have too many different entity groups in the transaction
so, requiring some thought before turning it on is probably a good idea, otherwise a lot of code will
get deployed that suddenly starts breaking on a bunch of corner cases.
Just my 2c worth ;-)
T
Jeff Schnitzer
Sep 16, 2012, 7:40:39 PM9/16/12
to timh, google-a...@googlegroups.com
Nonsense. Zero working code would be broken by permanently enabling
XG transactions. The only change is that code which was broken before
would no longer be broken. Which is kinda the point.
Jeff
XG transactions. The only change is that code which was broken before
would no longer be broken. Which is kinda the point.
Jeff
timh
Sep 16, 2012, 9:00:40 PM9/16/12
to google-a...@googlegroups.com, timh, je...@infohazard.org
Hey, I was just guessing as to their reasoning. I happen to agree with their position.
T
Reply all
Reply to author
Forward
0 new messages