Skip to content
Python Makefile HTML
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs [feature] create vuepy.js package Aug 16, 2019
examples [doc] updated examples page to use flask provider Jul 28, 2019
stubs [internal] updated pytest to 5.0.1 Aug 14, 2019
.editorconfig [docs] fix gallery Sep 8, 2018
.gitignore [bugfix] Updated pyyaml and Jinja2 because of security vulnerabilities Apr 13, 2019
.travis.yml [internal] release branch introduced Aug 14, 2019 [feature] create vuepy.js package Aug 16, 2019
LICENSE [feature] for packaging Sep 8, 2018
Makefile [feature] create vuepy.js package Aug 16, 2019 [internal] added first vuecli tests Aug 14, 2019
requirements.txt [internal] using brython pip package Aug 15, 2019

Build Status PyPI License

use Vue.js with pure Python provides Python bindings for Vue.js. It uses brython to run Python in the browser.

Here is a simple example of an component

from browser import alert
from vue import VueComponent

class HelloVuePy(VueComponent):
    greeting = "Hello"

    def greet(self, event):

    template = """
    <button @click="greet">click me</button>



$ pip install vuepy

Development Status

The goal is to provide a solution to write fully-featured Vue applications in pure Python.

To get an overview what currently is supported, have a look at the Documentation.

Have a look here to see whats planned!

See also the Limitations


Documentation is available here.

Examples can be found here. These are versions of the Vue.js examples


Initial loading times of apps can be very long. Especially when loading a lot of python files. Still figuring out how to solve this.

Have not done any peformance tests, but havent noticed any issues with performance as soon as the app was fully loaded.


Getting Started

Get the code

$ git clone
$ cd

Install required python packages, the chromedriver for selenium and brython

$ make env.up

Run tests

$ make tests           # runs all tets
$ make tests.unit      # runs unit tests
$ make tests.selenium  # runs selenium tests
$ make tests.cli       # runs cli tests

Clean up your working directory.

$ make env.clean

Reset your development environment (clean up, reinstall packages and redownload needed files)

$ make env.down
$ make env.up


Development happens on the master branch. This also means the latest documentation can be found here.

The release branch should always be even with the latest release. Changes to this branch also trigger a update of gh-pages. Therefor fixes to the documentation can be made on the release branch. So that the documentation is always valid for the latest release.


This project is licensed under the MIT License - see the LICENSE file for details

You can’t perform that action at this time.