Just letting you know my delay in responding about this is because I am tied up with a conference and preparing a talk. May be another couple of days before I can look at it properly.
Graham > On 5 Nov 2017, at 00:23, Johan Larsson Hörkén <[email protected]> wrote: > > Great, fixed the warpdrive location. > > I have the XcodeDefault.xctoolchain/ > > Yes, I have marked the setup-script as executable > (~/.warpdrive/action_hooks/setup set -x). It can be run, and I see the > comments. But still nothing when running warpdrive setup. > > Sure, I mean warpdrive start, but still getting same problems. > > > >> On Saturday, 4 November 2017 12:34:55 UTC+1, Graham Dumpleton wrote: >> >>> On 4 Nov 2017, at 10:14 pm, Johan Larsson Hörkén <[email protected]> wrote: >>> >>> I have tried to follow the steps in >>> http://warpdrive.readthedocs.io/en/latest/getting-started.html, but have >>> been running into some problems. Background: >>> >>> OS: macOS 10.13.1 >>> Python: 3.6.3 (installed via Homebrew, as in >>> http://docs.python-guide.org/en/latest/starting/install3/osx/, into >>> /usr/local/bin/python3) >>> Warpdrive: 0.31.0 (installed via pip3 into >>> /usr/local/lib/python3.6/site-packages) >>> Django: 1.11.7 (used for test project) >>> >>> Edited ~/.bash_profile to include: >>> WARPDRIVE=$HOME/../../usr/local/lib/python3.6/site-packages/warpdrive >>> export WARPDRIVE >>> >>> >>> source `$WARPDRIVE rcfile` >> >> WARPDRIVE should be set to the 'warpdrive' command in the 'bin' directory, >> not the package. >> >> Eg. >> >> $ which warpdrive >> /Users/graham/.local/bin/warpdrive >> >> $ echo $WARPDRIVE >> /Users/graham/.local/bin/warpdrive >> >> BTW, pipsi is a great package for installing Python based applications into >> their own separate environments without polluting your main Python >> installation. >> >>> (I suspect that the path might be wrong, but I verified the location of the >>> package using pip3 show warpdrive) >>> >>> Also made sure apr and apr-util are installed for good measure, thus also >>> adding following to my ~/.bash_profile: >>> export PATH="/usr/local/opt/apr/bin:$PATH" >>> export PATH="/usr/local/opt/apr-util/bin:$PATH" >>> >>> Even though I have command line tools installed, verified with: >>> xcode-select --install >> >> On MacOS X you now need to have Xcode installed as well. You should not >> though need to use the Homebrew apr packages as when you use 'pip install >> mod_wsgi' it uses a workaround so that the 'apr' programs aren't needed. >> >> What version of Xcode do you have installed though? Apple keeps breaking >> stuff with each Xcode release. I also haven't tested on MacOS X 10.3 as yet >> so they could have broken new things in that version I don't know about. >> >> Which of these exists on your computer: >> >> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk >> >> >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-migrator/sdks/MacOSX.sdk >> >> Or neither? >> >>> CAN run warpdrive build without errors >>> >>> First problem - warpdrive setup not running: >>> Created the file ~/.warpdrive/action_hooks/setup, and added commands as >>> described in tutorial. When running the command warpdrive setup, nothing is >>> happening, not even an error message. >> >> Was the 'setup' script marked as executable? >> >> Add: >> >> set -x >> >> to the 'setup' script so it shows if it is being run as the commands in it >> are run. >> >>> >>> Second problem - warpdrive startserver: >> >> You mean: >> >> warpdrive start >> >>> When running warpdrive startserver I get following error: >>> -----> Executing server command 'mod_wsgi-express start-server >>> --server-root /Users/horken7/.warpdrive/warpdrive+mydjangosite/mod_wsgi >>> --log-to-terminal --startup-log --port 8080 --application-type module >>> --entry-point mydjangosite.wsgi --callable-object application --url-alias >>> /static/ >>> /Users/horken7/.warpdrive/warpdrive+mydjangosite/tmp/django/static/' >>> Traceback (most recent call last): >>> File >>> "/Users/horken7/.warpdrive/warpdrive+mydjangosite/bin/mod_wsgi-express", >>> line 7, in <module> >>> from mod_wsgi.server import main >>> ModuleNotFoundError: No module named 'mod_wsgi' >>> >>> I find that odd, since I expected that warpdrive would take care of all >>> mod_wsgi integration for me. But to make sure, I explicitly installed >>> mod_wsgi into warpdrives virtualenv (using pip3 install mod_wsgi). To get >>> some further information I also located and ran following: >>> >>> python3 ~/.warpdrive/warpdrive+mydjangosite/bin/mod_wsgi-express >>> Traceback (most recent call last): >>> File >>> "/Users/USERNAME/.warpdrive/warpdrive+mydjangosite/bin/mod_wsgi-express", >>> line 7, in <module> >>> from mod_wsgi.server import main >>> File >>> "/Users/USERNAME/.warpdrive/warpdrive+mydjangosite/lib/python3.6/site-packages/mod_wsgi/server/__init__.py", >>> line 24, in <module> >>> from . import apxs_config >>> File >>> "/Users/USERNAME/.warpdrive/warpdrive+mydjangosite/lib/python3.6/site-packages/mod_wsgi/server/apxs_config.py", >>> line 8, in <module> >>> from mod_wsgi_packages.httpd import __file__ as PACKAGES_ROOTDIR >>> ModuleNotFoundError: No module named 'mod_wsgi_packages' >>> >>> There are many potential problems and fixes, but after hours of googling I >>> still haven't found a solution. Hoping the problem to be simple, like some >>> incorrect directory reference. But apxs has been popping up multiple times >>> whilst troubleshooting previous errors, so I am suspecting that Apache >>> might have something to do with it. Unfortunately, getting warpdrive to >>> work hasn't been as easy as pip install warpdrive. Maybe a suggestion would >>> be to make a Youtube tutorial to show the process from a totally clean >>> environment (no python3, commandline tools or apache pre-installed)? >>> >>> Please tell me if you need any further information. Thanks! >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "modwsgi" 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 https://groups.google.com/group/modwsgi. >>> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" 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 https://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "modwsgi" 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 https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
