XBlock SDK fails at 3.3.3 Create the SQLite Database

[Jim Van Riper]

My environment:

• Mac OSX 10.11.5 with 8GB
• Python 2.7.12
• virtualenv 15.0.2

Starting in 3.2.3. Clone the XBlock Software Development Kit...

(venv) xblock_development$ cd xblock-sdk

(venv) xblock-sdk$ pip install -r requirements/base.txt

Obtaining file:///Users/jvr/xblock_development/xblock-sdk (from -r requirements/base.txt (line 23))

Requirement already satisfied (use --upgrade to upgrade): cookiecutter==0.9.0 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): Django<1.9,>=1.8 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 2))

Requirement already satisfied (use --upgrade to upgrade): lxml in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 3))

Requirement already satisfied (use --upgrade to upgrade): requests in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 4))

Requirement already satisfied (use --upgrade to upgrade): webob in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 5))

Requirement already satisfied (use --upgrade to upgrade): simplejson in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 6))

Requirement already satisfied (use --upgrade to upgrade): lazy in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 7))

Obtaining XBlock==0.4.7 from git+https://github.com/edx/XBloc...@xblock-0.4.7#egg=XBlock==0.4.7 (from -r requirements/base.txt (line 11))

  Updating /Users/jvr/xblock_development/venv/src/xblock clone (to xblock-0.4.7)

Requirement already satisfied (use --upgrade to upgrade): fs in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 14))

Requirement already satisfied (use --upgrade to upgrade): pypng in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 15))

Obtaining django-pyfs==1.0.3 from git+https://github.com/edx/django-...@1.0.3#egg=django-pyfs==1.0.3 (from -r requirements/base.txt (line 16))

  Updating /Users/jvr/xblock_development/venv/src/django-pyfs clone (to 1.0.3)

Requirement already satisfied (use --upgrade to upgrade): django_nose==1.4.1 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from -r requirements/base.txt (line 20))

Requirement already satisfied (use --upgrade to upgrade): PyYAML>=3.10 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): binaryornot>=0.2.0 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): jinja2>=2.4 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): mock in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): markupsafe in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from XBlock==0.4.7->-r requirements/base.txt (line 11))

Requirement already satisfied (use --upgrade to upgrade): python-dateutil in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from XBlock==0.4.7->-r requirements/base.txt (line 11))

Requirement already satisfied (use --upgrade to upgrade): pytz in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from XBlock==0.4.7->-r requirements/base.txt (line 11))

Requirement already satisfied (use --upgrade to upgrade): setuptools in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from fs->-r requirements/base.txt (line 14))

Requirement already satisfied (use --upgrade to upgrade): six in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from fs->-r requirements/base.txt (line 14))

Requirement already satisfied (use --upgrade to upgrade): nose>=1.2.1 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from django_nose==1.4.1->-r requirements/base.txt (line 20))

Requirement already satisfied (use --upgrade to upgrade): chardet>=2.0.0 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from binaryornot>=0.2.0->cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): funcsigs>=1; python_version < "3.3" in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from mock->cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Requirement already satisfied (use --upgrade to upgrade): pbr>=0.11 in /Users/jvr/xblock_development/venv/lib/python2.7/site-packages (from mock->cookiecutter==0.9.0->-r requirements/base.txt (line 1))

Installing collected packages: XBlock, django-pyfs, xblock-sdk

  Running setup.py develop for XBlock

  Running setup.py develop for django-pyfs

  Running setup.py develop for xblock-sdk

Successfully installed XBlock-0.4.7 django-pyfs-1.0.3 xblock-sdk-0.1.2

(venv) xblock-sdk$ cd ..

(venv) xblock_development$ xblock-sdk/bin/workbench-make-xblock

This script will create a new XBlock project.

You will be prompted for two pieces of information:

* Short name: a single word, all lower-case, for directory and file names.

  For a hologram 3-D XBlock, you might choose "holo3d".

* Class name: a valid Python class name.  It's best if this ends with "XBlock",

  so for our hologram XBlock, you might choose "Hologram3dXBlock".

Once you specify those two words, a directory will be created in the current

directory containing the new project.

If you don't want to create the project here, or you enter a name incorrectly,

just type Ctrl-C to stop this script.  If you don't want the resulting project,

just delete the directory it created.

Short name: myxblock

Class name: MyXBlock

(venv) xblock_development$ ls myxblock

myxblock myxblock_xblock.egg-info setup.py

(venv) xblock_development$ pip install -e myxblock

Obtaining file:///Users/jvr/xblock_development/myxblock

Requirement already satisfied (use --upgrade to upgrade): XBlock in ./venv/src/xblock (from myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): lxml in ./venv/lib/python2.7/site-packages (from XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): markupsafe in ./venv/lib/python2.7/site-packages (from XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): python-dateutil in ./venv/lib/python2.7/site-packages (from XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): pytz in ./venv/lib/python2.7/site-packages (from XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): webob in ./venv/lib/python2.7/site-packages (from XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): fs in ./venv/lib/python2.7/site-packages (from XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): six>=1.5 in ./venv/lib/python2.7/site-packages (from python-dateutil->XBlock->myxblock-xblock==0.1)

Requirement already satisfied (use --upgrade to upgrade): setuptools in ./venv/lib/python2.7/site-packages (from fs->XBlock->myxblock-xblock==0.1)

Installing collected packages: myxblock-xblock

  Running setup.py develop for myxblock-xblock

Successfully installed myxblock-xblock-0.1

(venv) xblock_development$ python xblock-sdk/manage.py syncdb

Traceback (most recent call last):

  File "xblock-sdk/manage.py", line 10, in <module>

    execute_from_command_line(sys.argv)

  File "/Users/jvr/xblock_development/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line

    utility.execute()

  File "/Users/jvr/xblock_development/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 328, in execute

    django.setup()

  File "/Users/jvr/xblock_development/venv/lib/python2.7/site-packages/django/__init__.py", line 17, in setup

    configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)

  File "/Users/jvr/xblock_development/venv/lib/python2.7/site-packages/django/utils/log.py", line 86, in configure_logging

    logging_config_func(logging_settings)

  File "/usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/config.py", line 794, in dictConfig

    dictConfigClass(config).configure()

  File "/usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/logging/config.py", line 576, in configure

    '%r: %s' % (name, e))

ValueError: Unable to configure handler 'logfile': [Errno 2] No such file or directory: '/Users/jvr/xblock_development/var/workbench.log'

(venv) xblock_development$ 

Any guidance would be appreciated.

Thanks,

Jim

[Ned Batchelder]

It's failing because /Users/jvr/xblock_development/var doesn't exist.  You should be in the xblock-sdk directory when you run manage.py, so that it will find the xblock-sdk/var directory for the log.

--Ned.

--
You received this message because you are subscribed to the Google Groups "Open edX operations" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openedx-ops...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openedx-ops/4cacec86-3a00-441c-a12e-9b74ef32940f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jim Van Riper]

Cool.  Thanks, Ned.  I was dogmatically following the instructions.

Step 4 in 3.2.3. Clone the XBlock Software Development Kit explicitly says "Run the following command to return to the xblock_development directory, where you will perform the rest of your work."  so I have entered feedback letting the doc team know that is incorrect.

And Step 1 in 3.3.3 says 

In the xblock_development directory, run the following command to create the database.

(venv) $ python xblock-sdk/manage.py syncdb

Ned, your advice about running manage.py from within the xblock-sdk directory also worked for the runserver command as well.

Thanks a bunch!

Jim

[Ronald N. David Valencia]

Yo tuve el mismo problema, (venv) $ python xblock-sdk/manage.py migrate 

en vez de ejecutar el comando desde esa poción lo ejecute directo en la carpeta xblock-sdk

Solución: (venv) $ python manage.py migrate