-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appengine 1.4 #58
Open
dragonx
wants to merge
66
commits into
django-nonrel:appengine-1.4
Choose a base branch
from
dragonx:appengine-1.4
base: appengine-1.4
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Appengine 1.4 #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ine into ancestor
…nonrel/djangoappengine into develop Conflicts: db/compiler.py
It's possible to use a django DateField or TimeField but have your own encoding in the datastore. In this case, we may not get a datetime value, so check type first.
…djangoappengine into django-1.4 Conflicts: db/compiler.py
The main benefit of both is to be able to pass in a Django model instead of a db.Model to get Keys or entities. Note that DjangoEntityInputReader returns a raw entity instead of a Django object instance. This is particularly useful for working with old entities in the datastore that may not match the latest Django model. Django's model classes could raise exceptions if properties were missing, but this class will allow fetching those entities. The developer can then add the missing properties, or whatever.
Fix socket retry code to find unused socket for next test.
This is really limited, a lot of things don't work (like tests and dumpdata)
Figured out how to get manage.py test, shell and dumpdata working.
…ngo-1.4 - Includes LiveServerTestCase which works with Selenium - Includes merging in AncestorKey implementation - Includes various other fixes for field types derived from DateTime fields causing breaks. - Includes fix for User API login not working. - Include switch to WSGI for python 2.7
Try original dev_appserver code, and fail to devappserver2 version.
….7.5 running dev_appserver, or devappserver2 0.8. Currently we detect between dev_appserver and devappserver2 based on availability of certain modules. In SDK 1.7.5, both dev_appserver and devappserver2 are available, and we default to dev_appserver for backwards compatibility. Does not have a current way to force devappserver2 in this case.
This makes the FileField's ClearableFileInput widget show up properly when there's an existing file in the model.
…b content-type, blob-key, and name.
Force use of devappserver2 by putting a file in the root of your project called force_devappserver.py The file should contain a single variable: devappsever_ver = 1 or 2 manage.py runserver, test and remote shell commands work on both devappserver1/2 manage.py shell works on devappserver1 but not devappserver2. Other commands have not been tested.
Can currently only run one test at a time, since server sometimes fails to shut down.
…commands like manage.py shell/dumpdat work. We need to patch runserver a bit so that it resets the stubs, otherwise we get an exception in devappserver2.
…pserver2. Make python manage.py deploy work. Removed the use of the appcfg -R flag, it shouldn't be necessary.
…e displayed without the blobkey (ie in form FileField)
…ine into appengine-1.4 Conflicts: djangoappengine/db/creation.py djangoappengine/db/stubs.py djangoappengine/db/utils.py djangoappengine/tests/__init__.py
This wasn't necessary on the original dev_appserver, but necessary on devappserver2 since it defaults to eventually consistent. We can remove the same call from testserver in this case.
…mapreduce library.
…re APIs. TODO: add PIL to Travis config
BTW I had looked into the Travis CI falure. I changed some settings to set up the Images API so I can test blobstore functionality. On the dev_server, this requires PIL, which isn't set up in the Travis environment, so you get Travis failures. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a pull request from my currently working repo. It's got a lot of stuff in it, but primarily:
aburgel's ancestor query work is merged in.
support for various devappserver2 issues, making stuff like dumpdata and loaddata work properly.
there's a hack in there for switching between dev_appserver and devappserver2. Create a file called "force_devappserver.py" in the project root with a single line "devappserver_ver = 1" (or 2)