## Problem Builder and Step Builder
[](https://circleci.com/gh/open-craft/problem-builder)
This repository provides two XBlocks: Problem Builder and Step Builder.
Both blocks allow to create questions of various types. They can be
used to simulate the workflow of real-life mentoring, within an edX
course.
Supported features include:
* **Free-form answers** (textarea) which can be shared accross
different XBlock instances (for example, to allow a student to
review and edit an answer they gave before).
* **Self-assessment MCQs** (multiple choice questions), to display
predetermined feedback to a student based on his choices in the
self-assessment. Supports rating scales and arbitrary answers.
* **MRQs (Multiple Response Questions)**, a type of multiple choice
question that allows the student to select more than one choice.
* **Answer recaps** that display a read-only summary of a user's
answer to a free-form question asked earlier in the course.
* **Progression tracking**, to require that the student has
completed a particular step before allowing them to complete the
next step. Provides a link to the next step to the student.
* **Tables**, which allow to present answers from the student to
free-form answers in a concise way. Supports custom headers.
* **Dashboards**, for displaying a summary of the student's answers
to multiple choice questions. [Details](doc/Dashboard.md)
The following screenshot shows an example of a Problem Builder block
containing a free-form question, two MCQs and one MRQ:
## Installation
You can install Problem Builder from [PyPI](https://pypi.org/project/xblock-problem-builder/)
using this command:
```bash
pip install xblock-problem-builder
```
For full details, see "Open edX Installation", below.
## Usage
See [Usage Instructions](doc/Usage.md)
## Workbench Installation and Settings
### Prerequisites
* Python 3.5+
* Compiler/build tool chain
* Python headers
* MySQL development libraries and headers
* Virtualenv
On Ubuntu 16.04, these can be installed by running
```bash
sudo apt-get install build-essential libpython3-dev libmysqlclient-dev virtualenv
```
### Developer Installation
For developers, you can install this XBlock into an XBlock SDK workbench's virtualenv.
First, create a Python3 virtualenv:
```bash
~/xblock_development $ virtualenv -p python3 venv
~/xblock_development $ . venv/bin/activate
```
Now run the following commands from the problem builder repo
root to install the problem builder dependencies:
```bash
(venv) ~/xblock_development/problem-builder $ pip install -r requirements.txt
(venv) ~/xblock_development/problem-builder $ pip install -r requirements-dev.txt
```
Switch to the created XBlock SDK repository, install its dependencies, and
create its migrations:
```bash
(venv) ~/xblock_development/problem-builder $ cd ../venv/src/xblock-sdk
(venv) ~/xblock_development/venv/src/xblock-sdk $ make requirements
```
Create the following configuration file in `workbench/settings_pb.py`:
```python
from settings import *
INSTALLED_APPS += ('problem_builder',)
```
Testing `problem-builder` in the workbench requires MySQL instead of the standard SQLite
configuration it uses. You can quickly spin up an instance of MySQL with Docker using the
following command:
```bash
# -d for detach mode
docker run --rm -it -p 3307:3306 -e MYSQL_ROOT_PASSWORD=rootpw -e MYSQL_DATABASE=db -d mysql:5.6
```
By default, the `xblock-sdk` uses the SQLite database but MySQL
can be used by specifying an environment variable `WORKBENCH_DATABASES` in
the following format.
```bash
export WORKBENCH_DATABASES='{"default": {"ENGINE": "django.db.backends.mysql", "NAME": "db", "USER": "root", "PASSWORD": "rootpw", "HOST": "127.0.0.1", "PORT": "3306"}}'
```
Ensure that the database name and credentials match the ones configured in the docker container.
Run this from the XBlock repository root:
```bash
./manage.py migrate --settings=workbench.settings_pb
```
Running the workbench
---------------------
```bash
./manage.py runserver 8000 --settings=workbench.settings_pb
```
Access it at [http://localhost:8000/](http://localhost:8000).
Running tests
-------------
The integration tests require a recent Firefox and geckodriver (CI
uses Firefox 70 and geckodriver 0.26). These can be installed locally for
testing if required. For example on Linux:
```bash
mkdir external
cd external
wget https://archive.mozilla.org/pub/firefox/releases/70.0.1/linux-x86_64/en-US/firefox-70.0.1.tar.bz2
tar jxf firefox-70.0.1.tar.bz2
wget https://github.com/mozilla/geckodriver/releases/download/v0.26.0/geckodriver-v0.26.0-linux64.tar.gz
tar xzf geckodriver-v0.26.0-linux64.tar.gz
export PATH="$(pwd):$(pwd)/firefox/:$PATH"
# now can run integration tests using this firefox version
cd ..
make test.integration
```
From the problem-builder repository root, run the tests with the
following command:
```bash
make test
```
See also the following for more scoped tests:
```bash
make quality
make test.unit
make test.integration
```
Debugging CI Failures
---------------------
Sometimes it can be hard to figure out why some tests fail in the CI.
When Circle CI browser based tests fail for unknown reasons, it can be helpful to run them with VNC enabled
so that you can observe the browser (or even interact with it) while the tests are running.
To enable VNC on Circle CI, first re-run the failing test with SSH enabled: in the Circle CI UI,
click the "Rerun" dropdown and select "Rerun Job with SSH". The job will be re-run with SSH enabled.
You can find the IP/port combination that lets you log into the VM with your github SSH key under the "Enable SSH"
step in the pipeline UI.
SSH into the VM, forwarding the VNC port:
```bash
ssh -p <port> <ip-address> -L 5900:localhost:5900
```
Install the required packages:
```bash
sudo apt-get install -yq xvfb x11vnc fluxbox
```
Start up xvfb and the VNC server:
```bash
rm -f /tmp/.X$(echo ${DISPLAY:-:0} | cut -b2-)-lock
Xvfb ${DISPLAY:-:0} -ac -listen tcp -screen 0 1440x900x24 &
/usr/bin/fluxbox -display ${DISPLAY:-:0} -screen 0 &
x11vnc -display ${DISPLAY:-:0} -forever -noxdamage -rfbport 5900 -quiet -passwd pass &
```
You should now be able to connect to the server via VNC. On macOS, you can use the built-in VNC viewer
that you can launch by opening Finder and choosing the "Go -> Connect to Server.." from the menu.
Type in `localhost:5900` and enter `pass` when asked for the password.
You are all set up to run integration tests with screen sharing enabled.
For some reason Firefox does not want to start in foreground mode when run as non-root,
so you'll have to run the tests as root.
```bash
unset MOZ_HEADLESS
cd /home/circleci/project
source venv/bin/activate
make test
```
Working with Translations
-------------------------
For information about working with translations, see the
[Internationalization Support](http://edx.readthedocs.io/projects/xblock-tutorial/en/latest/edx_platform/edx_lms.html#internationalization-support)
section of the [Open edX XBlock Tutorial](https://xblock-tutorial.readthedocs.io/en/latest/).
[Prepare your virtualenv](#workbench-installation-and-settings) and ensure that the
[Transifex authentication file](https://openedx.atlassian.net/wiki/display/OpenOPS/Running+Fullstack)
(``~/.transifexrc``) is properly set up.
Push new strings to Transifex:
```bash
$ make extract_translations
$ make push_translations
```
To get the latest translations from Transifex:
```bash
$ make pull_translations
$ make compile_translations
```
For testing purposes it's faster to avoid Transifex and work on dummy Esperanto translations:
```bash
$ make build_dummy_translations
```
The Transifex configuration is stored in `.tx`. For more information read
[transifex's documentation](https://docs.transifex.com/client/client-configuration)
If you want to add a new language:
1. Add language to `problem_builder/translations/config.yaml`
2. Make sure all tagged strings have been extracted and push to Transifex as described above.
3. Go to Transifex and translate both of the
[Problem Builder](https://www.transifex.com/open-edx/xblocks/problem-builder/)
and the [Problem Builder JS](https://www.transifex.com/open-edx/xblocks/problem-builder-js/) resources.
4. When you're done with the translations pull from Transifex as described above.
Adding custom scenarios to the workbench
----------------------------------------
Within the xblock-problem-builder repository, create the `templates/xml` and
add XML scenarios to it - all files with the `*.xml` extension will be
automatically loaded by the workbench:
```bash
$ mkdir templates/xml
$ cat > templates/xml/my_pb_scenario.xml
```
Restart the workbench to take the new scenarios into account.
Upgrading from Version 1
------------------------
To upgrade a course from xblock-mentoring ("v1") to xblock-problem-builder
("v2"), run the following command on a system with edx-platform,
xblock-mentoring, and xblock-problem-builder installed:
```bash
$ SERVICE_VARIANT=cms DJANGO_SETTINGS_MODULE="cms.envs.devstack" python -m problem_builder.v1.upgrade "Org/Course/Run"
```
Where "Org/Course/Run" is replaced with the ID of the course to upgrade.
Open edX Installation
---------------------
Problem Builder releases are tagged with a version number, e.g.
[`v2.6.0`](https://github.com/open-craft/problem-builder/tree/v2.6.0),
[`v2.6.5`](https://github.com/open-craft/problem-builder/tree/v2.6.5). We recommend installing the most recently tagged
version, with the exception of the following compatibility issues:
* `edx-platform` version `open-release/ironwood.2` and earlier must use versions < 4.0.0. See
[PR 262](https://github.com/open-craft/problem-builder/pull/262) for details.
* `edx-platform` version `open-release/eucalyptus.2` and earlier must use
≤[v2.6.0](https://github.com/open-craft/problem-builder/tree/v2.6.0). See
[PR 128](https://github.com/open-craft/problem-builder/pull/128) for details.
* `edx-platform` version `named-release/dogwood.3` and earlier must use
[v2.0.0](https://github.com/open-craft/problem-builder/tree/v2.0.0).
The `edx-platform` `master` branch will generally always be compatible with the most recent Problem Builder tag. See
[the EDXAPP_PRIVATE_REQUIREMENTS setting](https://github.com/edx/configuration/blob/master/playbooks/roles/edxapp/defaults/main.yml) for the version
currently installed on [edx.org](https://edx.org).
To install new versions of Problem Builder (v3.1.3+), use `pip install xblock-problem-builder` or specify a version using e.g. `pip install xblock-problem-builder==3.1.3`. To do this on Open edX could look like:
```bash
$ sudo -Hu edxapp bash
edxapp $ cd && . edxapp_env && . ./venvs/edxapp/bin/activate && cd edx-platform/
edxapp $ pip install xblock-problem-builder
edxapp $ ./manage.py lms migrate --settings=aws # or openstack, as appropriate
```
Then, restart the edxapp services:
```bash
$ sudo /edx/bin/supervisorctl restart edxapp:
$ sudo /edx/bin/supervisorctl restart edxapp_workers:
```
To install old verions of Problem Builder (< v3.1.3) on an Open edX installation, choose the tag you wish to install, follow the above instructions but instead of the `pip install xblock-problem-builder` command, use:
```bash
TAG='v2.6.5' pip install "git+https://github.com/open-craft/problem-builder.git@$TAG#egg=xblock-problem-builder==$TAG"
```
Note that Problem Builder requires [xblock-utils](https://github.com/edx/xblock-utils).
If you are installing it into a virtualenv used by edx-platform, xblock-utils should
already be installed. But if you are installing it into another virtualenv, you may
need to first install xblock-utils manually (recent versions of it are not available
on PyPI so will not be automatically installed).
See [Usage Instructions](doc/Usage.md) for how to enable in Studio.
Publishing to PyPI
------------------
Whenever we tag a new version, e.g. `v3.1.3` and push it to GitHub, CircleCI will
build it and deploy it to PyPI automatically. For details on how this works, see
[this pull request](https://github.com/open-craft/problem-builder/pull/199).
License
-------
This XBlock is available under the GNU Affero General Public License (AGPLv3).
Raw data
{
"_id": null,
"home_page": "https://github.com/open-craft/problem-builder",
"name": "xblock-problem-builder",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "",
"keywords": "Python edx",
"author": "OpenCraft",
"author_email": "",
"download_url": "https://files.pythonhosted.org/packages/dc/34/0886c735f4834cb5fa33e5765e801360c9a52f326f59584c726de0952776/xblock-problem-builder-5.1.4.tar.gz",
"platform": null,
"description": "## Problem Builder and Step Builder\n\n[](https://circleci.com/gh/open-craft/problem-builder)\n\nThis repository provides two XBlocks: Problem Builder and Step Builder.\n\nBoth blocks allow to create questions of various types. They can be\nused to simulate the workflow of real-life mentoring, within an edX\ncourse.\n\nSupported features include:\n\n* **Free-form answers** (textarea) which can be shared accross\n different XBlock instances (for example, to allow a student to\n review and edit an answer they gave before).\n* **Self-assessment MCQs** (multiple choice questions), to display\n predetermined feedback to a student based on his choices in the\n self-assessment. Supports rating scales and arbitrary answers.\n* **MRQs (Multiple Response Questions)**, a type of multiple choice\n question that allows the student to select more than one choice.\n* **Answer recaps** that display a read-only summary of a user's\n answer to a free-form question asked earlier in the course.\n* **Progression tracking**, to require that the student has\n completed a particular step before allowing them to complete the\n next step. Provides a link to the next step to the student.\n* **Tables**, which allow to present answers from the student to\n free-form answers in a concise way. Supports custom headers.\n* **Dashboards**, for displaying a summary of the student's answers\n to multiple choice questions. [Details](doc/Dashboard.md)\n\nThe following screenshot shows an example of a Problem Builder block\ncontaining a free-form question, two MCQs and one MRQ:\n\n\n\n## Installation\n\nYou can install Problem Builder from [PyPI](https://pypi.org/project/xblock-problem-builder/)\nusing this command:\n\n```bash\npip install xblock-problem-builder\n```\n\nFor full details, see \"Open edX Installation\", below.\n\n## Usage\n\nSee [Usage Instructions](doc/Usage.md)\n\n## Workbench Installation and Settings\n\n### Prerequisites\n\n* Python 3.5+\n* Compiler/build tool chain\n* Python headers\n* MySQL development libraries and headers\n* Virtualenv\n\nOn Ubuntu 16.04, these can be installed by running\n\n```bash\nsudo apt-get install build-essential libpython3-dev libmysqlclient-dev virtualenv\n```\n\n### Developer Installation\n\nFor developers, you can install this XBlock into an XBlock SDK workbench's virtualenv.\n\nFirst, create a Python3 virtualenv:\n\n```bash\n~/xblock_development $ virtualenv -p python3 venv\n~/xblock_development $ . venv/bin/activate\n```\n\nNow run the following commands from the problem builder repo\nroot to install the problem builder dependencies:\n\n```bash\n(venv) ~/xblock_development/problem-builder $ pip install -r requirements.txt\n(venv) ~/xblock_development/problem-builder $ pip install -r requirements-dev.txt\n```\n\nSwitch to the created XBlock SDK repository, install its dependencies, and\ncreate its migrations:\n\n```bash\n(venv) ~/xblock_development/problem-builder $ cd ../venv/src/xblock-sdk\n(venv) ~/xblock_development/venv/src/xblock-sdk $ make requirements\n```\n\nCreate the following configuration file in `workbench/settings_pb.py`:\n\n```python\nfrom settings import *\n\nINSTALLED_APPS += ('problem_builder',)\n```\n\nTesting `problem-builder` in the workbench requires MySQL instead of the standard SQLite\nconfiguration it uses. You can quickly spin up an instance of MySQL with Docker using the\nfollowing command:\n\n```bash\n# -d for detach mode\ndocker run --rm -it -p 3307:3306 -e MYSQL_ROOT_PASSWORD=rootpw -e MYSQL_DATABASE=db -d mysql:5.6\n```\n\nBy default, the `xblock-sdk` uses the SQLite database but MySQL\ncan be used by specifying an environment variable `WORKBENCH_DATABASES` in\nthe following format.\n\n```bash\nexport WORKBENCH_DATABASES='{\"default\": {\"ENGINE\": \"django.db.backends.mysql\", \"NAME\": \"db\", \"USER\": \"root\", \"PASSWORD\": \"rootpw\", \"HOST\": \"127.0.0.1\", \"PORT\": \"3306\"}}'\n```\n\nEnsure that the database name and credentials match the ones configured in the docker container.\n\nRun this from the XBlock repository root:\n\n```bash\n./manage.py migrate --settings=workbench.settings_pb\n```\n\nRunning the workbench\n---------------------\n\n```bash\n./manage.py runserver 8000 --settings=workbench.settings_pb\n```\n\nAccess it at [http://localhost:8000/](http://localhost:8000).\n\nRunning tests\n-------------\n\nThe integration tests require a recent Firefox and geckodriver (CI\nuses Firefox 70 and geckodriver 0.26). These can be installed locally for\ntesting if required. For example on Linux:\n\n```bash\nmkdir external\ncd external\nwget https://archive.mozilla.org/pub/firefox/releases/70.0.1/linux-x86_64/en-US/firefox-70.0.1.tar.bz2\ntar jxf firefox-70.0.1.tar.bz2\nwget https://github.com/mozilla/geckodriver/releases/download/v0.26.0/geckodriver-v0.26.0-linux64.tar.gz\ntar xzf geckodriver-v0.26.0-linux64.tar.gz\nexport PATH=\"$(pwd):$(pwd)/firefox/:$PATH\"\n\n# now can run integration tests using this firefox version\ncd ..\nmake test.integration\n```\n\nFrom the problem-builder repository root, run the tests with the\nfollowing command:\n\n```bash\nmake test\n```\n\nSee also the following for more scoped tests:\n\n```bash\nmake quality\nmake test.unit\nmake test.integration\n```\n\nDebugging CI Failures\n---------------------\n\nSometimes it can be hard to figure out why some tests fail in the CI.\nWhen Circle CI browser based tests fail for unknown reasons, it can be helpful to run them with VNC enabled\nso that you can observe the browser (or even interact with it) while the tests are running.\n\nTo enable VNC on Circle CI, first re-run the failing test with SSH enabled: in the Circle CI UI,\nclick the \"Rerun\" dropdown and select \"Rerun Job with SSH\". The job will be re-run with SSH enabled.\nYou can find the IP/port combination that lets you log into the VM with your github SSH key under the \"Enable SSH\"\nstep in the pipeline UI.\n\nSSH into the VM, forwarding the VNC port:\n\n```bash\nssh -p <port> <ip-address> -L 5900:localhost:5900\n```\n\nInstall the required packages:\n\n```bash\nsudo apt-get install -yq xvfb x11vnc fluxbox\n```\n\nStart up xvfb and the VNC server:\n\n```bash\nrm -f /tmp/.X$(echo ${DISPLAY:-:0} | cut -b2-)-lock\nXvfb ${DISPLAY:-:0} -ac -listen tcp -screen 0 1440x900x24 &\n/usr/bin/fluxbox -display ${DISPLAY:-:0} -screen 0 &\nx11vnc -display ${DISPLAY:-:0} -forever -noxdamage -rfbport 5900 -quiet -passwd pass &\n```\n\nYou should now be able to connect to the server via VNC. On macOS, you can use the built-in VNC viewer\nthat you can launch by opening Finder and choosing the \"Go -> Connect to Server..\" from the menu.\nType in `localhost:5900` and enter `pass` when asked for the password.\n\nYou are all set up to run integration tests with screen sharing enabled.\nFor some reason Firefox does not want to start in foreground mode when run as non-root,\nso you'll have to run the tests as root.\n\n```bash\nunset MOZ_HEADLESS\ncd /home/circleci/project\nsource venv/bin/activate\nmake test\n```\n\nWorking with Translations\n-------------------------\n\nFor information about working with translations, see the\n[Internationalization Support](http://edx.readthedocs.io/projects/xblock-tutorial/en/latest/edx_platform/edx_lms.html#internationalization-support)\nsection of the [Open edX XBlock Tutorial](https://xblock-tutorial.readthedocs.io/en/latest/).\n\n[Prepare your virtualenv](#workbench-installation-and-settings) and ensure that the\n[Transifex authentication file](https://openedx.atlassian.net/wiki/display/OpenOPS/Running+Fullstack)\n(``~/.transifexrc``) is properly set up.\n\nPush new strings to Transifex:\n\n```bash\n$ make extract_translations\n$ make push_translations\n```\n\nTo get the latest translations from Transifex:\n\n```bash\n$ make pull_translations\n$ make compile_translations\n```\n\nFor testing purposes it's faster to avoid Transifex and work on dummy Esperanto translations:\n\n```bash\n$ make build_dummy_translations\n```\n\nThe Transifex configuration is stored in `.tx`. For more information read\n[transifex's documentation](https://docs.transifex.com/client/client-configuration)\n\nIf you want to add a new language:\n 1. Add language to `problem_builder/translations/config.yaml`\n 2. Make sure all tagged strings have been extracted and push to Transifex as described above.\n 3. Go to Transifex and translate both of the\n [Problem Builder](https://www.transifex.com/open-edx/xblocks/problem-builder/)\n and the [Problem Builder JS](https://www.transifex.com/open-edx/xblocks/problem-builder-js/) resources.\n 4. When you're done with the translations pull from Transifex as described above.\n\n\nAdding custom scenarios to the workbench\n----------------------------------------\n\nWithin the xblock-problem-builder repository, create the `templates/xml` and\nadd XML scenarios to it - all files with the `*.xml` extension will be\nautomatically loaded by the workbench:\n\n```bash\n$ mkdir templates/xml\n$ cat > templates/xml/my_pb_scenario.xml\n```\n\nRestart the workbench to take the new scenarios into account.\n\nUpgrading from Version 1\n------------------------\n\nTo upgrade a course from xblock-mentoring (\"v1\") to xblock-problem-builder\n(\"v2\"), run the following command on a system with edx-platform,\nxblock-mentoring, and xblock-problem-builder installed:\n\n```bash\n$ SERVICE_VARIANT=cms DJANGO_SETTINGS_MODULE=\"cms.envs.devstack\" python -m problem_builder.v1.upgrade \"Org/Course/Run\"\n```\nWhere \"Org/Course/Run\" is replaced with the ID of the course to upgrade.\n\n\nOpen edX Installation\n---------------------\n\nProblem Builder releases are tagged with a version number, e.g.\n[`v2.6.0`](https://github.com/open-craft/problem-builder/tree/v2.6.0),\n[`v2.6.5`](https://github.com/open-craft/problem-builder/tree/v2.6.5). We recommend installing the most recently tagged\nversion, with the exception of the following compatibility issues:\n\n* `edx-platform` version `open-release/ironwood.2` and earlier must use versions < 4.0.0. See\n [PR 262](https://github.com/open-craft/problem-builder/pull/262) for details.\n* `edx-platform` version `open-release/eucalyptus.2` and earlier must use\n \u2264[v2.6.0](https://github.com/open-craft/problem-builder/tree/v2.6.0). See\n [PR 128](https://github.com/open-craft/problem-builder/pull/128) for details.\n* `edx-platform` version `named-release/dogwood.3` and earlier must use\n [v2.0.0](https://github.com/open-craft/problem-builder/tree/v2.0.0).\n\nThe `edx-platform` `master` branch will generally always be compatible with the most recent Problem Builder tag. See\n[the EDXAPP_PRIVATE_REQUIREMENTS setting](https://github.com/edx/configuration/blob/master/playbooks/roles/edxapp/defaults/main.yml) for the version\ncurrently installed on [edx.org](https://edx.org).\n\nTo install new versions of Problem Builder (v3.1.3+), use `pip install xblock-problem-builder` or specify a version using e.g. `pip install xblock-problem-builder==3.1.3`. To do this on Open edX could look like:\n\n```bash\n$ sudo -Hu edxapp bash\nedxapp $ cd && . edxapp_env && . ./venvs/edxapp/bin/activate && cd edx-platform/\nedxapp $ pip install xblock-problem-builder\nedxapp $ ./manage.py lms migrate --settings=aws # or openstack, as appropriate\n```\n\nThen, restart the edxapp services:\n\n```bash\n$ sudo /edx/bin/supervisorctl restart edxapp:\n$ sudo /edx/bin/supervisorctl restart edxapp_workers:\n```\n\nTo install old verions of Problem Builder (< v3.1.3) on an Open edX installation, choose the tag you wish to install, follow the above instructions but instead of the `pip install xblock-problem-builder` command, use:\n\n```bash\nTAG='v2.6.5' pip install \"git+https://github.com/open-craft/problem-builder.git@$TAG#egg=xblock-problem-builder==$TAG\"\n```\n\nNote that Problem Builder requires [xblock-utils](https://github.com/edx/xblock-utils).\nIf you are installing it into a virtualenv used by edx-platform, xblock-utils should\nalready be installed. But if you are installing it into another virtualenv, you may\nneed to first install xblock-utils manually (recent versions of it are not available\non PyPI so will not be automatically installed).\n\nSee [Usage Instructions](doc/Usage.md) for how to enable in Studio.\n\nPublishing to PyPI\n------------------\n\nWhenever we tag a new version, e.g. `v3.1.3` and push it to GitHub, CircleCI will\nbuild it and deploy it to PyPI automatically. For details on how this works, see\n[this pull request](https://github.com/open-craft/problem-builder/pull/199).\n\nLicense\n-------\n\nThis XBlock is available under the GNU Affero General Public License (AGPLv3).\n",
"bugtrack_url": null,
"license": "AGPL v3",
"summary": "XBlock - Problem Builder",
"version": "5.1.4",
"project_urls": {
"Homepage": "https://github.com/open-craft/problem-builder"
},
"split_keywords": [
"python",
"edx"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a098868aa09da2630c34c431ee79d57ef5dcbde17dbf49de3ee5c12580e2ec07",
"md5": "1867ba57ca2b330758d776b00195f072",
"sha256": "89a2a6ef43707368b38ffb60d1c0943900972d8e82ec54b6f10d613010a4f59f"
},
"downloads": -1,
"filename": "xblock_problem_builder-5.1.4-py3-none-any.whl",
"has_sig": false,
"md5_digest": "1867ba57ca2b330758d776b00195f072",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 669087,
"upload_time": "2023-08-04T10:29:44",
"upload_time_iso_8601": "2023-08-04T10:29:44.239344Z",
"url": "https://files.pythonhosted.org/packages/a0/98/868aa09da2630c34c431ee79d57ef5dcbde17dbf49de3ee5c12580e2ec07/xblock_problem_builder-5.1.4-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "dc340886c735f4834cb5fa33e5765e801360c9a52f326f59584c726de0952776",
"md5": "13f59b2c6259c53ecad6c52b2e47a825",
"sha256": "6ec2e203e90178eebed91625e84a3684e81470029623ce025a3a5be0e43bb3ae"
},
"downloads": -1,
"filename": "xblock-problem-builder-5.1.4.tar.gz",
"has_sig": false,
"md5_digest": "13f59b2c6259c53ecad6c52b2e47a825",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 538919,
"upload_time": "2023-08-04T10:29:46",
"upload_time_iso_8601": "2023-08-04T10:29:46.118877Z",
"url": "https://files.pythonhosted.org/packages/dc/34/0886c735f4834cb5fa33e5765e801360c9a52f326f59584c726de0952776/xblock-problem-builder-5.1.4.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-08-04 10:29:46",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "open-craft",
"github_project": "problem-builder",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"tox": true,
"lcname": "xblock-problem-builder"
}
JSON
