nocommandline/dev_appserver-python3-windows

A patch to allow you run Python 3 Apps on Windows using dev_appserver.py

NoCommandLine (v3.0.4)

A GUI for Google App Engine & Datastore Emulator. An improved replacement for the old Google App Engine Launcher.

• Click a button to run code on dev or deploy to production

  • Don't struggle to remember gcloud flags/commands
  • Don't fiddle around your command prompt
  • Non-technical folks can deploy code
  • Support for custom/user-defined environment variables & flags
  • Run app with dev_appserver.py or your language idiomatic way (e.g. python main.py, flask run)
    • Windows: Use our Patch to run Python 3 Apps with dev_appserver.py on Windows platform

• Tick a checkbox to set/unset an option

  • Don't struggle to remember gcloud flags/commands

• GUI for datastore emulator

  • Supports named databases (requires installation of gcloud alpha components) 🆕
  • View/Edit/Delete data from datastore emulator or production
  • Export datastore data as CSV or JSON (datastore emulator or production)
  • Import exported data into datastore (datastore emulator or production)
  • Import data from local/legacy datastore (created with older runtime generations such as Python 2; not linked to Cloud Datastore Emulator) into Cloud Datastore Emulator for use with newer runtimes such as Python 3

• See all projects on a single UI

  • Don't keep multiple folders open just to remember your different projects
  • Supports multiple services and/or versions of the same application 🆕

• Download your source code

• See full list of features - https://nocommandline.com/#features

Demos

https://nocommandline.com/#demo

Supported OS/Platform

• OS X
• Windows (10/11)

Download

https://nocommandline.com/download/

Features

https://nocommandline.com/#features

Website

https://nocommandline.com/

dev_appserver-python3-windows's Issues

Fails to run in debug mode from within PyCharm

From within PyCharm, I can run dev_appserver (with the patch applied), and everything appears to work.

1. Create a Python (not App Engine) project
2. In the Run config, set the script to C:/Users/XXX/AppData/Local/Google/Cloud SDK/google-cloud-sdk/bin/dev_appserver.py
3. In the Run config, set the params to: --runtime_python_path C:\Python\Python39\python.exe --application my_project_name --python_virtualenv_path C:\Users\XXX\AppData\Local\Temp\appengine_devappserver_venv app.yaml
4. In the Run config, set the environment var: CLOUDSDK_DEVAPPSERVER_PYTHON=C:\Python\Python27\python.exe

However, when I try to run in debug mode from PyCharm, I run into a problem in the modified instance_factory.py. Line 429 (call_res = subprocess.call(args)) returns a 1, indicating a problem. The fallback virtualenv code fails as well, and the exception that eventually gets thrown says "The system cannot find the file specified".

I'm not sure what the "specified file" is. Here are the arguments to that call:

args = ['C:\Python\Python39\python.exe', '-m', 'venv', 'C:\Users\XXX\AppData\Local\Temp\appengine_devappserver_venv\default']

I wasn't sure what the trailing 'default' meant, so I tried creating a 'default' subdirectory, but it didn't help, and strangely it got deleted during the fail. Just to cover all bases, I also tried not using the --python_virtualenv_path flag, but still ended up in a similar situation (different temporary folder name of course).

Note that to get PyCharm's editor to correctly handle code completion, I had to copy the google folder from the App Engine SDK installation (C:\Users\XXX\AppData\Local\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\google) into the project's venv\Lib\site-packages. I don't think this is related, though.

Fail run on windows using SDK 470.0.0 with pyhton 39

From CMD i'm trying this:

1. Install Python39 con Path C:\python39 (Version 3.9.13)
2. Install Python39 con Path C:\python27 (Version 2.7.18)
3. Install Google SDK with version Google Cloud SDK 470.0.0, app-engine-python 1.9.111
4. Download your copy of the file from the 'src' folder and overwrite the original file
5. Set CLOUDSDK_DEVAPPSERVER_PYTHON with python 2 Path, using set CLOUDSDK_DEVAPPSERVER_PYTHON=C:\Python27\python.exe
6. try run dev_appserver usign a simple hello_world example, using dev_appserver.py app.yaml

When i tried this its generate the next exception:

Traceback (most recent call last):
File "C:\CloudSDK\google-cloud-sdk\bin\dev_appserver.py", line 13, in
from bootstrapping import bootstrapping
File "C:\CloudSDK\google-cloud-sdk\bin\bootstrapping\bootstrapping.py", line 24, in
from . import setup # pylint:disable=g-import-not-at-top
File "C:\CloudSDK\google-cloud-sdk\bin\bootstrapping\setup.py", line 57, in
from googlecloudsdk.core.util import platforms
File "C:\CloudSDK\google-cloud-sdk\lib\googlecloudsdk_init_.py", line 23, in
import importlib.util
ImportError: No module named util

I Searched this and found that it's cause the version of python, but i'm not sure how to deal with that, can someone help me?

Flag to reuse virtual env for py3

The readme mentions a Flag to reuse virtual env for py3, but it was done 2 weeks ago in the gcloud devappserver, so no need to do it anymore here.

For the other path, I am studying it to see what we can do. Thanks!

Using `-python_virtualenv_path` causes an error on restarting your App (for SDK 470.0.0)

The version of the patch which supports gcloud SDK v470.0.0 gives an error if you restart your App and you're using -python_virtualenv_path flag.

The process is

1. You run your App the first time using -python_virtualenv_path
2. A new virtual environment is created in the specified path and your App starts successfully
3. You shut down your App and start it again
4. It will error out. The logs will show a permission denied entry to the -python_virtualenv_path or another folder

Workaround/Temporary Fix

Do not use the flag for now until the fix is out