1.8.9 Pre-Release SDKs are now available.
512 views
Skip to first unread message
Richmond Manzana
Jan 10, 2014, 7:26:59 PM1/10/14
to google-a...@googlegroups.com
Happy New Year!
We wanted to inform you that the pre-release SDKs for Python, PHP and Java are now available and are found here:
Please see the pre-release notes below.
Cheers,
Richmond Manzana
Technical Program Manager
Google App Engine
App Engine SDK - Pre-Release Notes
Version 1.8.9
Python & PHP
==============================
- Renamed appcfg start to appcfg start_module_version and stop to
stop_module_version.
- Fixed an issue with ID allocation collisions in the Datastore.
- Fixed an issue with Cloud Storage calls failing in the dev_appserver.
- Fixed an issue with the dev_appserver not starting on Windows when using
versions of Python earlier than 2.7.2.
Python
==============================
- Deprecated start_module, start_module_async, stop_module, stop_module_async
get_modules_async, get_versions_async, get_default_version_async,
get_num_instances_async, get_hostname_async and added start_version,
start_version_async, stop_version, stop_version_async as replacements in the
Modules API.
- Added verbose_name support for ComputedProperty in NDB.
- Fixed an issue with deffered.defer not waiting for async operations.
- Fixed an issue with LocalStructureProperty not handling None value in NDB.
- Fixed an issue NDB not working with sqlite.
- Fixed an issue with debug not working with PyDev in 1.8.8.
- Fixed an issue with object properties not being retrieved in NDB.
PHP
=============================
- Renamed startModule, stopModule to startVersion, stopVersion in the Modules
API.
- Added support for the ftp extension.
- Added support for the zip extension.
- Added support for the gethostname() function.
- A proper "billing required" message is now given when users attempt to use
Sockets API on free apps.
- Fixed an issue with header keys and values having whitespaces preventing
responses from being compressed.
- Fixed an issue with content-type and metadata not being updated when renaming
Google Cloud Storage objects.
- Fixed an issue with Cloud Storage rename requests failing when an object has
a space in its name.
Java
==============================- Renamed appcfg start to appcfg start_module_version and stop to
stop_module_version.
- The following methods are deprecated in the Modules API and will be removed
in an upcoming release:
getModulesAsync
getVersionsAsync
getDefaultVersionAsync
getNumInstancesAsync
getVersionHostnameAsync
getInstanceHostnameAsync
startModule (replaced by startVersion)
startModuleAsync (replaced by startVersionAsync)
stopModule (replaced by stopVersion)
stopModuleAsync (replaced by stopVersionAsync)
getModuleHostname (replaced by getVersionHostname and getInstanceHostname)
getModuleHostnameAsync
- The following exceptions have been deprecated in the Modules API and will be
removed in a following release:
InvalidInstanceException
InvalidModuloeException
InvalidVersionException
- The following exceptions have been removed in the Modules API:
ModuleAlreadyStartedException
ModuleAlreadyStoppedException
- Modules are now supported in the dev_appserver Development Console.
- Fixed an issue with ID allocation collisions in the Datastore.
husayt
Jan 14, 2014, 3:21:53 PM1/14/14
to google-a...@googlegroups.com
Hi Richmond,
how can I get the latest via maven? I have tried various repositories, but no luck.
Thanks
Prateek Malhotra
Jan 14, 2014, 6:26:28 PM1/14/14
to google-a...@googlegroups.com
Today all of the sudden in my Python app the code `str(datetime.datetime)` started producing results with a time zone offset (e.g. +0000) at the end where it wasn't done before. The only difference I can see to my app is the change from 1.8.8 to 1.8.9. It broke some code that was expecting datetime information in a certain format which we have since fixed but it was a nasty surprise none-the-less.
Was this an intended side effect of the SDK update?
Stephen Lewis
Jan 15, 2014, 12:39:27 PM1/15/14
to google-a...@googlegroups.com
Hi Richmond
This URL returns '403 Forbidden' for me:
Is that intentional? I can't find any discussion in this group about ID allocation collisions.
Thanks
Stephen
On Saturday, 11 January 2014 00:26:59 UTC, Richmond Manzana wrote:
R Samuel Klatchko
Jan 15, 2014, 3:43:08 PM1/15/14
to google-a...@googlegroups.com
Hi Prateek-
I'm unable to reproduce your results. If I use:
str(datetime.datetime.now())
str(datetime.datetime.today())
I do not see the timezone offset in either 1.8.8 or 1.8.9.
On the other hand, if I use:
class faketz(datetime.tzinfo):def utcoffset(self, _):return datetime.timedelta(0)def dst(self, _):return datetime.timedelta(0)
datetime.datetime.now(faketz())
I see the timezone offset in both 1.8.8 and 1.8.9. Can you provide more detailed reproduction steps.
samuel
Prateek Malhotra
Jan 16, 2014, 4:37:50 PM1/16/14
to google-a...@googlegroups.com
A reflective code sample:
import pytz
import datetime
str(pytz.utc.localize(datetime.datetime.now()))
This part of our code has been working fine for months with no change, though looking at it now I think the change occurred on one of the service API's we use from a 3rd party.
My apologies on jumping the gun there.
Thank you,
Prateek Malhotra
Project Manager/Lead Web Applications Developer
ReferABuyer.com - Developer of the Automatic$eller Software!
1973 Washington Valley Road
Martinsville, NJ 08836
Phone: 732-868-4421
Fax: 732-356-5875
--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/I-e4MfckrIk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
R. Samuel Klatchko
Jan 16, 2014, 8:59:09 PM1/16/14
to google-a...@googlegroups.com
Prateek-
I tried:
str(pytz.utc.localize(datetime.datetime.now()))
under both 1.8.8 and 1.8.9 and see the timezone offsets in both.
pytz is not included in App Engine so you must have included it yourself in your app (I tried both pytz-2013.9 and gae-pytz). Perhaps you are using a different version of pytz that has different behavior in 1.8.8 and 1.8.9.
samuel
Reply all
Reply to author
Forward
0 new messages