mirror of
https://github.com/kristoferssolo/School.git
synced 2025-10-21 20:10:38 +00:00
Added web UI
This commit is contained in:
Kristofers Solo
parent
e1996ea454
commit
4ae684acdb
@ -6,30 +6,47 @@ Home-page: https://github.com/samuelhwilliams/Eel
|
||||
Author: Chris Knott
|
||||
Author-email: chrisknott@hotmail.co.uk
|
||||
License: UNKNOWN
|
||||
Description: # Eel
|
||||
Keywords: gui,html,javascript,electron
|
||||
Platform: UNKNOWN
|
||||
Classifier: Development Status :: 3 - Alpha
|
||||
Classifier: Natural Language :: English
|
||||
Classifier: Operating System :: MacOS
|
||||
Classifier: Operating System :: POSIX
|
||||
Classifier: Operating System :: Microsoft :: Windows :: Windows 10
|
||||
Classifier: Programming Language :: Python :: 3
|
||||
Classifier: Programming Language :: Python :: 3.6
|
||||
Classifier: Programming Language :: Python :: 3.7
|
||||
Classifier: Programming Language :: Python :: 3.8
|
||||
Classifier: Programming Language :: Python :: Implementation :: CPython
|
||||
Classifier: License :: OSI Approved :: MIT License
|
||||
Requires-Python: >=3.6
|
||||
Description-Content-Type: text/markdown
|
||||
Provides-Extra: jinja2
|
||||
|
||||
[](https://pypi.org/project/Eel/)
|
||||
[](https://pypistats.org/packages/eel)
|
||||
|
||||
[](https://pypi.org/project/Eel/)
|
||||
# Eel
|
||||
|
||||
[](https://pypi.org/project/Eel/)
|
||||
[](https://pypistats.org/packages/eel)
|
||||
|
||||
[](https://pypi.org/project/Eel/)
|
||||
|
||||
|
||||
[](https://lgtm.com/projects/g/samuelhwilliams/Eel/alerts/)
|
||||
[](https://lgtm.com/projects/g/samuelhwilliams/Eel/context:javascript)
|
||||
[](https://lgtm.com/projects/g/samuelhwilliams/Eel/context:python)
|
||||
[](https://lgtm.com/projects/g/samuelhwilliams/Eel/alerts/)
|
||||
[](https://lgtm.com/projects/g/samuelhwilliams/Eel/context:javascript)
|
||||
[](https://lgtm.com/projects/g/samuelhwilliams/Eel/context:python)
|
||||
|
||||
|
||||
Eel is a little Python library for making simple Electron-like offline HTML/JS GUI apps, with full access to Python capabilities and libraries.
|
||||
Eel is a little Python library for making simple Electron-like offline HTML/JS GUI apps, with full access to Python capabilities and libraries.
|
||||
|
||||
> **Eel hosts a local webserver, then lets you annotate functions in Python so that they can be called from Javascript, and vice versa.**
|
||||
> **Eel hosts a local webserver, then lets you annotate functions in Python so that they can be called from Javascript, and vice versa.**
|
||||
|
||||
Eel is designed to take the hassle out of writing short and simple GUI applications. If you are familiar with Python and web development, probably just jump to [this example](https://github.com/ChrisKnott/Eel/tree/master/examples/04%20-%20file_access) which picks random file names out of the given folder (something that is impossible from a browser).
|
||||
Eel is designed to take the hassle out of writing short and simple GUI applications. If you are familiar with Python and web development, probably just jump to [this example](https://github.com/ChrisKnott/Eel/tree/master/examples/04%20-%20file_access) which picks random file names out of the given folder (something that is impossible from a browser).
|
||||
|
||||
<p align="center"><img src="https://raw.githubusercontent.com/samuelhwilliams/Eel/master/examples/04%20-%20file_access/Screenshot.png" ></p>
|
||||
<p align="center"><img src="https://raw.githubusercontent.com/samuelhwilliams/Eel/master/examples/04%20-%20file_access/Screenshot.png" ></p>
|
||||
|
||||
<!-- TOC -->
|
||||
<!-- TOC -->
|
||||
|
||||
- [Eel](#eel)
|
||||
- [Eel](#eel)
|
||||
- [Intro](#intro)
|
||||
- [Install](#install)
|
||||
- [Usage](#usage)
|
||||
@ -46,74 +63,74 @@ Description: # Eel
|
||||
- [Building distributable binary with PyInstaller](#building-distributable-binary-with-pyinstaller)
|
||||
- [Microsoft Edge](#microsoft-edge)
|
||||
|
||||
<!-- /TOC -->
|
||||
<!-- /TOC -->
|
||||
|
||||
## Intro
|
||||
## Intro
|
||||
|
||||
There are several options for making GUI apps in Python, but if you want to use HTML/JS (in order to use jQueryUI or Bootstrap, for example) then you generally have to write a lot of boilerplate code to communicate from the Client (Javascript) side to the Server (Python) side.
|
||||
There are several options for making GUI apps in Python, but if you want to use HTML/JS (in order to use jQueryUI or Bootstrap, for example) then you generally have to write a lot of boilerplate code to communicate from the Client (Javascript) side to the Server (Python) side.
|
||||
|
||||
The closest Python equivalent to Electron (to my knowledge) is [cefpython](https://github.com/cztomczak/cefpython). It is a bit heavy weight for what I wanted.
|
||||
The closest Python equivalent to Electron (to my knowledge) is [cefpython](https://github.com/cztomczak/cefpython). It is a bit heavy weight for what I wanted.
|
||||
|
||||
Eel is not as fully-fledged as Electron or cefpython - it is probably not suitable for making full blown applications like Atom - but it is very suitable for making the GUI equivalent of little utility scripts that you use internally in your team.
|
||||
Eel is not as fully-fledged as Electron or cefpython - it is probably not suitable for making full blown applications like Atom - but it is very suitable for making the GUI equivalent of little utility scripts that you use internally in your team.
|
||||
|
||||
For some reason many of the best-in-class number crunching and maths libraries are in Python (Tensorflow, Numpy, Scipy etc) but many of the best visualization libraries are in Javascript (D3, THREE.js etc). Hopefully Eel makes it easy to combine these into simple utility apps for assisting your development.
|
||||
For some reason many of the best-in-class number crunching and maths libraries are in Python (Tensorflow, Numpy, Scipy etc) but many of the best visualization libraries are in Javascript (D3, THREE.js etc). Hopefully Eel makes it easy to combine these into simple utility apps for assisting your development.
|
||||
|
||||
Join Eel's users and maintainers on [Discord](https://discord.com/invite/3nqXPFX), if you like.
|
||||
Join Eel's users and maintainers on [Discord](https://discord.com/invite/3nqXPFX), if you like.
|
||||
|
||||
## Install
|
||||
## Install
|
||||
|
||||
Install from pypi with `pip`:
|
||||
Install from pypi with `pip`:
|
||||
|
||||
```shell
|
||||
pip install eel
|
||||
```
|
||||
```shell
|
||||
pip install eel
|
||||
```
|
||||
|
||||
To include support for HTML templating, currently using [Jinja2](https://pypi.org/project/Jinja2/#description):
|
||||
To include support for HTML templating, currently using [Jinja2](https://pypi.org/project/Jinja2/#description):
|
||||
|
||||
```shell
|
||||
pip install eel[jinja2]
|
||||
```
|
||||
```shell
|
||||
pip install eel[jinja2]
|
||||
```
|
||||
|
||||
## Usage
|
||||
## Usage
|
||||
|
||||
### Directory Structure
|
||||
### Directory Structure
|
||||
|
||||
An Eel application will be split into a frontend consisting of various web-technology files (.html, .js, .css) and a backend consisting of various Python scripts.
|
||||
An Eel application will be split into a frontend consisting of various web-technology files (.html, .js, .css) and a backend consisting of various Python scripts.
|
||||
|
||||
All the frontend files should be put in a single directory (they can be further divided into folders inside this if necessary).
|
||||
All the frontend files should be put in a single directory (they can be further divided into folders inside this if necessary).
|
||||
|
||||
```
|
||||
my_python_script.py <-- Python scripts
|
||||
other_python_module.py
|
||||
static_web_folder/ <-- Web folder
|
||||
```
|
||||
my_python_script.py <-- Python scripts
|
||||
other_python_module.py
|
||||
static_web_folder/ <-- Web folder
|
||||
main_page.html
|
||||
css/
|
||||
style.css
|
||||
img/
|
||||
logo.png
|
||||
```
|
||||
```
|
||||
|
||||
### Starting the app
|
||||
### Starting the app
|
||||
|
||||
Suppose you put all the frontend files in a directory called `web`, including your start page `main.html`, then the app is started like this;
|
||||
Suppose you put all the frontend files in a directory called `web`, including your start page `main.html`, then the app is started like this;
|
||||
|
||||
```python
|
||||
import eel
|
||||
eel.init('web')
|
||||
eel.start('main.html')
|
||||
```
|
||||
```python
|
||||
import eel
|
||||
eel.init('web')
|
||||
eel.start('main.html')
|
||||
```
|
||||
|
||||
This will start a webserver on the default settings (http://localhost:8000) and open a browser to http://localhost:8000/main.html.
|
||||
This will start a webserver on the default settings (http://localhost:8000) and open a browser to http://localhost:8000/main.html.
|
||||
|
||||
If Chrome or Chromium is installed then by default it will open in that in App Mode (with the `--app` cmdline flag), regardless of what the OS's default browser is set to (it is possible to override this behaviour).
|
||||
If Chrome or Chromium is installed then by default it will open in that in App Mode (with the `--app` cmdline flag), regardless of what the OS's default browser is set to (it is possible to override this behaviour).
|
||||
|
||||
### App options
|
||||
### App options
|
||||
|
||||
Additional options can be passed to `eel.start()` as keyword arguments.
|
||||
Additional options can be passed to `eel.start()` as keyword arguments.
|
||||
|
||||
Some of the options include the mode the app is in (e.g. 'chrome'), the port the app runs on, the host name of the app, and adding additional command line flags.
|
||||
Some of the options include the mode the app is in (e.g. 'chrome'), the port the app runs on, the host name of the app, and adding additional command line flags.
|
||||
|
||||
As of Eel v0.12.0, the following options are available to `start()`:
|
||||
As of Eel v0.12.0, the following options are available to `start()`:
|
||||
- **mode**, a string specifying what browser to use (e.g. `'chrome'`, `'electron'`, `'edge'`, `'custom'`). Can also be `None` or `False` to not open a window. *Default: `'chrome'`*
|
||||
- **host**, a string specifying what hostname to use for the Bottle server. *Default: `'localhost'`)*
|
||||
- **port**, an int specifying what port to use for the Bottle server. Use `0` for port to be picked automatically. *Default: `8000`*.
|
||||
@ -129,66 +146,66 @@ Description: # Eel
|
||||
|
||||
|
||||
|
||||
### Exposing functions
|
||||
### Exposing functions
|
||||
|
||||
In addition to the files in the frontend folder, a Javascript library will be served at `/eel.js`. You should include this in any pages:
|
||||
In addition to the files in the frontend folder, a Javascript library will be served at `/eel.js`. You should include this in any pages:
|
||||
|
||||
```html
|
||||
<script type="text/javascript" src="/eel.js"></script>
|
||||
```
|
||||
```html
|
||||
<script type="text/javascript" src="/eel.js"></script>
|
||||
```
|
||||
|
||||
Including this library creates an `eel` object which can be used to communicate with the Python side.
|
||||
Including this library creates an `eel` object which can be used to communicate with the Python side.
|
||||
|
||||
Any functions in the Python code which are decorated with `@eel.expose` like this...
|
||||
Any functions in the Python code which are decorated with `@eel.expose` like this...
|
||||
|
||||
```python
|
||||
@eel.expose
|
||||
def my_python_function(a, b):
|
||||
```python
|
||||
@eel.expose
|
||||
def my_python_function(a, b):
|
||||
print(a, b, a + b)
|
||||
```
|
||||
```
|
||||
|
||||
...will appear as methods on the `eel` object on the Javascript side, like this...
|
||||
...will appear as methods on the `eel` object on the Javascript side, like this...
|
||||
|
||||
```javascript
|
||||
console.log("Calling Python...");
|
||||
eel.my_python_function(1, 2); // This calls the Python function that was decorated
|
||||
```
|
||||
```javascript
|
||||
console.log("Calling Python...");
|
||||
eel.my_python_function(1, 2); // This calls the Python function that was decorated
|
||||
```
|
||||
|
||||
Similarly, any Javascript functions which are exposed like this...
|
||||
Similarly, any Javascript functions which are exposed like this...
|
||||
|
||||
```javascript
|
||||
eel.expose(my_javascript_function);
|
||||
function my_javascript_function(a, b, c, d) {
|
||||
```javascript
|
||||
eel.expose(my_javascript_function);
|
||||
function my_javascript_function(a, b, c, d) {
|
||||
if (a < b) {
|
||||
console.log(c * d);
|
||||
}
|
||||
}
|
||||
```
|
||||
}
|
||||
```
|
||||
|
||||
can be called from the Python side like this...
|
||||
can be called from the Python side like this...
|
||||
|
||||
```python
|
||||
print('Calling Javascript...')
|
||||
eel.my_javascript_function(1, 2, 3, 4) # This calls the Javascript function
|
||||
```
|
||||
```python
|
||||
print('Calling Javascript...')
|
||||
eel.my_javascript_function(1, 2, 3, 4) # This calls the Javascript function
|
||||
```
|
||||
|
||||
The exposed name can also be overridden by passing in a second argument. If your app minifies JavaScript during builds, this may be necessary to ensure that functions can be resolved on the Python side:
|
||||
The exposed name can also be overridden by passing in a second argument. If your app minifies JavaScript during builds, this may be necessary to ensure that functions can be resolved on the Python side:
|
||||
|
||||
```javascript
|
||||
eel.expose(someFunction, "my_javascript_function");
|
||||
```
|
||||
```javascript
|
||||
eel.expose(someFunction, "my_javascript_function");
|
||||
```
|
||||
|
||||
When passing complex objects as arguments, bear in mind that internally they are converted to JSON and sent down a websocket (a process that potentially loses information).
|
||||
When passing complex objects as arguments, bear in mind that internally they are converted to JSON and sent down a websocket (a process that potentially loses information).
|
||||
|
||||
### Eello, World!
|
||||
### Eello, World!
|
||||
|
||||
> See full example in: [examples/01 - hello_world](https://github.com/ChrisKnott/Eel/tree/master/examples/01%20-%20hello_world)
|
||||
> See full example in: [examples/01 - hello_world](https://github.com/ChrisKnott/Eel/tree/master/examples/01%20-%20hello_world)
|
||||
|
||||
Putting this together into a **Hello, World!** example, we have a short HTML page, `web/hello.html`:
|
||||
Putting this together into a **Hello, World!** example, we have a short HTML page, `web/hello.html`:
|
||||
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<title>Hello, World!</title>
|
||||
|
||||
@ -208,174 +225,159 @@ Description: # Eel
|
||||
<body>
|
||||
Hello, World!
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
</html>
|
||||
```
|
||||
|
||||
and a short Python script `hello.py`:
|
||||
and a short Python script `hello.py`:
|
||||
|
||||
```python
|
||||
import eel
|
||||
```python
|
||||
import eel
|
||||
|
||||
# Set web files folder and optionally specify which file types to check for eel.expose()
|
||||
# *Default allowed_extensions are: ['.js', '.html', '.txt', '.htm', '.xhtml']
|
||||
eel.init('web', allowed_extensions=['.js', '.html'])
|
||||
# Set web files folder and optionally specify which file types to check for eel.expose()
|
||||
# *Default allowed_extensions are: ['.js', '.html', '.txt', '.htm', '.xhtml']
|
||||
eel.init('web', allowed_extensions=['.js', '.html'])
|
||||
|
||||
@eel.expose # Expose this function to Javascript
|
||||
def say_hello_py(x):
|
||||
@eel.expose # Expose this function to Javascript
|
||||
def say_hello_py(x):
|
||||
print('Hello from %s' % x)
|
||||
|
||||
say_hello_py('Python World!')
|
||||
eel.say_hello_js('Python World!') # Call a Javascript function
|
||||
say_hello_py('Python World!')
|
||||
eel.say_hello_js('Python World!') # Call a Javascript function
|
||||
|
||||
eel.start('hello.html') # Start (this blocks and enters loop)
|
||||
```
|
||||
eel.start('hello.html') # Start (this blocks and enters loop)
|
||||
```
|
||||
|
||||
If we run the Python script (`python hello.py`), then a browser window will open displaying `hello.html`, and we will see...
|
||||
If we run the Python script (`python hello.py`), then a browser window will open displaying `hello.html`, and we will see...
|
||||
|
||||
```
|
||||
Hello from Python World!
|
||||
Hello from Javascript World!
|
||||
```
|
||||
```
|
||||
Hello from Python World!
|
||||
Hello from Javascript World!
|
||||
```
|
||||
|
||||
...in the terminal, and...
|
||||
...in the terminal, and...
|
||||
|
||||
```
|
||||
Hello from Javascript World!
|
||||
Hello from Python World!
|
||||
```
|
||||
```
|
||||
Hello from Javascript World!
|
||||
Hello from Python World!
|
||||
```
|
||||
|
||||
...in the browser console (press F12 to open).
|
||||
...in the browser console (press F12 to open).
|
||||
|
||||
You will notice that in the Python code, the Javascript function is called before the browser window is even started - any early calls like this are queued up and then sent once the websocket has been established.
|
||||
You will notice that in the Python code, the Javascript function is called before the browser window is even started - any early calls like this are queued up and then sent once the websocket has been established.
|
||||
|
||||
### Return values
|
||||
### Return values
|
||||
|
||||
While we want to think of our code as comprising a single application, the Python interpreter and the browser window run in separate processes. This can make communicating back and forth between them a bit of a mess, especially if we always had to explicitly _send_ values from one side to the other.
|
||||
While we want to think of our code as comprising a single application, the Python interpreter and the browser window run in separate processes. This can make communicating back and forth between them a bit of a mess, especially if we always had to explicitly _send_ values from one side to the other.
|
||||
|
||||
Eel supports two ways of retrieving _return values_ from the other side of the app, which helps keep the code concise.
|
||||
Eel supports two ways of retrieving _return values_ from the other side of the app, which helps keep the code concise.
|
||||
|
||||
To prevent hanging forever on the Python side, a timeout has been put in place for trying to retrieve values from
|
||||
the JavaScript side, which defaults to 10000 milliseconds (10 seconds). This can be changed with the `_js_result_timeout` parameter to `eel.init`. There is no corresponding timeout on the JavaScript side.
|
||||
To prevent hanging forever on the Python side, a timeout has been put in place for trying to retrieve values from
|
||||
the JavaScript side, which defaults to 10000 milliseconds (10 seconds). This can be changed with the `_js_result_timeout` parameter to `eel.init`. There is no corresponding timeout on the JavaScript side.
|
||||
|
||||
#### Callbacks
|
||||
#### Callbacks
|
||||
|
||||
When you call an exposed function, you can immediately pass a callback function afterwards. This callback will automatically be called asynchrounously with the return value when the function has finished executing on the other side.
|
||||
When you call an exposed function, you can immediately pass a callback function afterwards. This callback will automatically be called asynchrounously with the return value when the function has finished executing on the other side.
|
||||
|
||||
For example, if we have the following function defined and exposed in Javascript:
|
||||
For example, if we have the following function defined and exposed in Javascript:
|
||||
|
||||
```javascript
|
||||
eel.expose(js_random);
|
||||
function js_random() {
|
||||
```javascript
|
||||
eel.expose(js_random);
|
||||
function js_random() {
|
||||
return Math.random();
|
||||
}
|
||||
```
|
||||
}
|
||||
```
|
||||
|
||||
Then in Python we can retrieve random values from the Javascript side like so:
|
||||
Then in Python we can retrieve random values from the Javascript side like so:
|
||||
|
||||
```python
|
||||
def print_num(n):
|
||||
```python
|
||||
def print_num(n):
|
||||
print('Got this from Javascript:', n)
|
||||
|
||||
# Call Javascript function, and pass explicit callback function
|
||||
eel.js_random()(print_num)
|
||||
# Call Javascript function, and pass explicit callback function
|
||||
eel.js_random()(print_num)
|
||||
|
||||
# Do the same with an inline lambda as callback
|
||||
eel.js_random()(lambda n: print('Got this from Javascript:', n))
|
||||
```
|
||||
# Do the same with an inline lambda as callback
|
||||
eel.js_random()(lambda n: print('Got this from Javascript:', n))
|
||||
```
|
||||
|
||||
(It works exactly the same the other way around).
|
||||
(It works exactly the same the other way around).
|
||||
|
||||
#### Synchronous returns
|
||||
#### Synchronous returns
|
||||
|
||||
In most situations, the calls to the other side are to quickly retrieve some piece of data, such as the state of a widget or contents of an input field. In these cases it is more convenient to just synchronously wait a few milliseconds then continue with your code, rather than breaking the whole thing up into callbacks.
|
||||
In most situations, the calls to the other side are to quickly retrieve some piece of data, such as the state of a widget or contents of an input field. In these cases it is more convenient to just synchronously wait a few milliseconds then continue with your code, rather than breaking the whole thing up into callbacks.
|
||||
|
||||
To synchronously retrieve the return value, simply pass nothing to the second set of brackets. So in Python we would write:
|
||||
To synchronously retrieve the return value, simply pass nothing to the second set of brackets. So in Python we would write:
|
||||
|
||||
```python
|
||||
n = eel.js_random()() # This immediately returns the value
|
||||
print('Got this from Javascript:', n)
|
||||
```
|
||||
```python
|
||||
n = eel.js_random()() # This immediately returns the value
|
||||
print('Got this from Javascript:', n)
|
||||
```
|
||||
|
||||
You can only perform synchronous returns after the browser window has started (after calling `eel.start()`), otherwise obviously the call with hang.
|
||||
You can only perform synchronous returns after the browser window has started (after calling `eel.start()`), otherwise obviously the call with hang.
|
||||
|
||||
In Javascript, the language doesn't allow us to block while we wait for a callback, except by using `await` from inside an `async` function. So the equivalent code from the Javascript side would be:
|
||||
In Javascript, the language doesn't allow us to block while we wait for a callback, except by using `await` from inside an `async` function. So the equivalent code from the Javascript side would be:
|
||||
|
||||
```javascript
|
||||
async function run() {
|
||||
```javascript
|
||||
async function run() {
|
||||
// Inside a function marked 'async' we can use the 'await' keyword.
|
||||
|
||||
let n = await eel.py_random()(); // Must prefix call with 'await', otherwise it's the same syntax
|
||||
console.log("Got this from Python: " + n);
|
||||
}
|
||||
}
|
||||
|
||||
run();
|
||||
```
|
||||
run();
|
||||
```
|
||||
|
||||
## Asynchronous Python
|
||||
## Asynchronous Python
|
||||
|
||||
Eel is built on Bottle and Gevent, which provide an asynchronous event loop similar to Javascript. A lot of Python's standard library implicitly assumes there is a single execution thread - to deal with this, Gevent can "[monkey patch](https://en.wikipedia.org/wiki/Monkey_patch)" many of the standard modules such as `time`. ~~This monkey patching is done automatically when you call `import eel`~~. If you need monkey patching you should `import gevent.monkey` and call `gevent.monkey.patch_all()` _before_ you `import eel`. Monkey patching can interfere with things like debuggers so should be avoided unless necessary.
|
||||
Eel is built on Bottle and Gevent, which provide an asynchronous event loop similar to Javascript. A lot of Python's standard library implicitly assumes there is a single execution thread - to deal with this, Gevent can "[monkey patch](https://en.wikipedia.org/wiki/Monkey_patch)" many of the standard modules such as `time`. ~~This monkey patching is done automatically when you call `import eel`~~. If you need monkey patching you should `import gevent.monkey` and call `gevent.monkey.patch_all()` _before_ you `import eel`. Monkey patching can interfere with things like debuggers so should be avoided unless necessary.
|
||||
|
||||
For most cases you should be fine by avoiding using `time.sleep()` and instead using the versions provided by `gevent`. For convenience, the two most commonly needed gevent methods, `sleep()` and `spawn()` are provided directly from Eel (to save importing `time` and/or `gevent` as well).
|
||||
For most cases you should be fine by avoiding using `time.sleep()` and instead using the versions provided by `gevent`. For convenience, the two most commonly needed gevent methods, `sleep()` and `spawn()` are provided directly from Eel (to save importing `time` and/or `gevent` as well).
|
||||
|
||||
In this example...
|
||||
In this example...
|
||||
|
||||
```python
|
||||
import eel
|
||||
eel.init('web')
|
||||
```python
|
||||
import eel
|
||||
eel.init('web')
|
||||
|
||||
def my_other_thread():
|
||||
def my_other_thread():
|
||||
while True:
|
||||
print("I'm a thread")
|
||||
eel.sleep(1.0) # Use eel.sleep(), not time.sleep()
|
||||
|
||||
eel.spawn(my_other_thread)
|
||||
eel.spawn(my_other_thread)
|
||||
|
||||
eel.start('main.html', block=False) # Don't block on this call
|
||||
eel.start('main.html', block=False) # Don't block on this call
|
||||
|
||||
while True:
|
||||
while True:
|
||||
print("I'm a main loop")
|
||||
eel.sleep(1.0) # Use eel.sleep(), not time.sleep()
|
||||
```
|
||||
```
|
||||
|
||||
...we would then have three "threads" (greenlets) running;
|
||||
...we would then have three "threads" (greenlets) running;
|
||||
|
||||
1. Eel's internal thread for serving the web folder
|
||||
2. The `my_other_thread` method, repeatedly printing **"I'm a thread"**
|
||||
3. The main Python thread, which would be stuck in the final `while` loop, repeatedly printing **"I'm a main loop"**
|
||||
1. Eel's internal thread for serving the web folder
|
||||
2. The `my_other_thread` method, repeatedly printing **"I'm a thread"**
|
||||
3. The main Python thread, which would be stuck in the final `while` loop, repeatedly printing **"I'm a main loop"**
|
||||
|
||||
## Building distributable binary with PyInstaller
|
||||
## Building distributable binary with PyInstaller
|
||||
|
||||
If you want to package your app into a program that can be run on a computer without a Python interpreter installed, you should use **PyInstaller**.
|
||||
If you want to package your app into a program that can be run on a computer without a Python interpreter installed, you should use **PyInstaller**.
|
||||
|
||||
1. Configure a virtualenv with desired Python version and minimum necessary Python packages
|
||||
2. Install PyInstaller `pip install PyInstaller`
|
||||
3. In your app's folder, run `python -m eel [your_main_script] [your_web_folder]` (for example, you might run `python -m eel hello.py web`)
|
||||
4. This will create a new folder `dist/`
|
||||
5. Valid PyInstaller flags can be passed through, such as excluding modules with the flag: `--exclude module_name`. For example, you might run `python -m eel file_access.py web --exclude win32com --exclude numpy --exclude cryptography`
|
||||
6. When happy that your app is working correctly, add `--onefile --noconsole` flags to build a single executable file
|
||||
1. Configure a virtualenv with desired Python version and minimum necessary Python packages
|
||||
2. Install PyInstaller `pip install PyInstaller`
|
||||
3. In your app's folder, run `python -m eel [your_main_script] [your_web_folder]` (for example, you might run `python -m eel hello.py web`)
|
||||
4. This will create a new folder `dist/`
|
||||
5. Valid PyInstaller flags can be passed through, such as excluding modules with the flag: `--exclude module_name`. For example, you might run `python -m eel file_access.py web --exclude win32com --exclude numpy --exclude cryptography`
|
||||
6. When happy that your app is working correctly, add `--onefile --noconsole` flags to build a single executable file
|
||||
|
||||
Consult the [documentation for PyInstaller](http://PyInstaller.readthedocs.io/en/stable/) for more options.
|
||||
Consult the [documentation for PyInstaller](http://PyInstaller.readthedocs.io/en/stable/) for more options.
|
||||
|
||||
## Microsoft Edge
|
||||
## Microsoft Edge
|
||||
|
||||
For Windows 10 users, Microsoft Edge (`eel.start(.., mode='edge')`) is installed by default and a useful fallback if a preferred browser is not installed. See the examples:
|
||||
For Windows 10 users, Microsoft Edge (`eel.start(.., mode='edge')`) is installed by default and a useful fallback if a preferred browser is not installed. See the examples:
|
||||
|
||||
- A Hello World example using Microsoft Edge: [examples/01 - hello_world-Edge/](https://github.com/ChrisKnott/Eel/tree/master/examples/01%20-%20hello_world-Edge)
|
||||
- Example implementing browser-fallbacks: [examples/07 - CreateReactApp/eel_CRA.py](https://github.com/ChrisKnott/Eel/tree/master/examples/07%20-%20CreateReactApp/eel_CRA.py)
|
||||
|
||||
- A Hello World example using Microsoft Edge: [examples/01 - hello_world-Edge/](https://github.com/ChrisKnott/Eel/tree/master/examples/01%20-%20hello_world-Edge)
|
||||
- Example implementing browser-fallbacks: [examples/07 - CreateReactApp/eel_CRA.py](https://github.com/ChrisKnott/Eel/tree/master/examples/07%20-%20CreateReactApp/eel_CRA.py)
|
||||
|
||||
Keywords: gui,html,javascript,electron
|
||||
Platform: UNKNOWN
|
||||
Classifier: Development Status :: 3 - Alpha
|
||||
Classifier: Natural Language :: English
|
||||
Classifier: Operating System :: MacOS
|
||||
Classifier: Operating System :: POSIX
|
||||
Classifier: Operating System :: Microsoft :: Windows :: Windows 10
|
||||
Classifier: Programming Language :: Python :: 3
|
||||
Classifier: Programming Language :: Python :: 3.6
|
||||
Classifier: Programming Language :: Python :: 3.7
|
||||
Classifier: Programming Language :: Python :: 3.8
|
||||
Classifier: Programming Language :: Python :: Implementation :: CPython
|
||||
Classifier: License :: OSI Approved :: MIT License
|
||||
Requires-Python: >=3.6
|
||||
Description-Content-Type: text/markdown
|
||||
Provides-Extra: jinja2
|
||||
|
||||
@ -0,0 +1,28 @@
|
||||
Copyright 2010 Pallets
|
||||
|
||||
Redistribution and use in source and binary forms, with or without
|
||||
modification, are permitted provided that the following conditions are
|
||||
met:
|
||||
|
||||
1. Redistributions of source code must retain the above copyright
|
||||
notice, this list of conditions and the following disclaimer.
|
||||
|
||||
2. Redistributions in binary form must reproduce the above copyright
|
||||
notice, this list of conditions and the following disclaimer in the
|
||||
documentation and/or other materials provided with the distribution.
|
||||
|
||||
3. Neither the name of the copyright holder nor the names of its
|
||||
contributors may be used to endorse or promote products derived from
|
||||
this software without specific prior written permission.
|
||||
|
||||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
||||
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
||||
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
|
||||
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
||||
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
||||
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
|
||||
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
|
||||
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
|
||||
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
|
||||
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
|
||||
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
@ -0,0 +1,100 @@
|
||||
Metadata-Version: 2.1
|
||||
Name: MarkupSafe
|
||||
Version: 2.0.1
|
||||
Summary: Safely add untrusted strings to HTML/XML markup.
|
||||
Home-page: https://palletsprojects.com/p/markupsafe/
|
||||
Author: Armin Ronacher
|
||||
Author-email: armin.ronacher@active-4.com
|
||||
Maintainer: Pallets
|
||||
Maintainer-email: contact@palletsprojects.com
|
||||
License: BSD-3-Clause
|
||||
Project-URL: Donate, https://palletsprojects.com/donate
|
||||
Project-URL: Documentation, https://markupsafe.palletsprojects.com/
|
||||
Project-URL: Changes, https://markupsafe.palletsprojects.com/changes/
|
||||
Project-URL: Source Code, https://github.com/pallets/markupsafe/
|
||||
Project-URL: Issue Tracker, https://github.com/pallets/markupsafe/issues/
|
||||
Project-URL: Twitter, https://twitter.com/PalletsTeam
|
||||
Project-URL: Chat, https://discord.gg/pallets
|
||||
Platform: UNKNOWN
|
||||
Classifier: Development Status :: 5 - Production/Stable
|
||||
Classifier: Environment :: Web Environment
|
||||
Classifier: Intended Audience :: Developers
|
||||
Classifier: License :: OSI Approved :: BSD License
|
||||
Classifier: Operating System :: OS Independent
|
||||
Classifier: Programming Language :: Python
|
||||
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
|
||||
Classifier: Topic :: Text Processing :: Markup :: HTML
|
||||
Requires-Python: >=3.6
|
||||
Description-Content-Type: text/x-rst
|
||||
|
||||
MarkupSafe
|
||||
==========
|
||||
|
||||
MarkupSafe implements a text object that escapes characters so it is
|
||||
safe to use in HTML and XML. Characters that have special meanings are
|
||||
replaced so that they display as the actual characters. This mitigates
|
||||
injection attacks, meaning untrusted user input can safely be displayed
|
||||
on a page.
|
||||
|
||||
|
||||
Installing
|
||||
----------
|
||||
|
||||
Install and update using `pip`_:
|
||||
|
||||
.. code-block:: text
|
||||
|
||||
pip install -U MarkupSafe
|
||||
|
||||
.. _pip: https://pip.pypa.io/en/stable/quickstart/
|
||||
|
||||
|
||||
Examples
|
||||
--------
|
||||
|
||||
.. code-block:: pycon
|
||||
|
||||
>>> from markupsafe import Markup, escape
|
||||
|
||||
>>> # escape replaces special characters and wraps in Markup
|
||||
>>> escape("<script>alert(document.cookie);</script>")
|
||||
Markup('<script>alert(document.cookie);</script>')
|
||||
|
||||
>>> # wrap in Markup to mark text "safe" and prevent escaping
|
||||
>>> Markup("<strong>Hello</strong>")
|
||||
Markup('<strong>hello</strong>')
|
||||
|
||||
>>> escape(Markup("<strong>Hello</strong>"))
|
||||
Markup('<strong>hello</strong>')
|
||||
|
||||
>>> # Markup is a str subclass
|
||||
>>> # methods and operators escape their arguments
|
||||
>>> template = Markup("Hello <em>{name}</em>")
|
||||
>>> template.format(name='"World"')
|
||||
Markup('Hello <em>"World"</em>')
|
||||
|
||||
|
||||
Donate
|
||||
------
|
||||
|
||||
The Pallets organization develops and supports MarkupSafe and other
|
||||
popular packages. In order to grow the community of contributors and
|
||||
users, and allow the maintainers to devote more time to the projects,
|
||||
`please donate today`_.
|
||||
|
||||
.. _please donate today: https://palletsprojects.com/donate
|
||||
|
||||
|
||||
Links
|
||||
-----
|
||||
|
||||
- Documentation: https://markupsafe.palletsprojects.com/
|
||||
- Changes: https://markupsafe.palletsprojects.com/changes/
|
||||
- PyPI Releases: https://pypi.org/project/MarkupSafe/
|
||||
- Source Code: https://github.com/pallets/markupsafe/
|
||||
- Issue Tracker: https://github.com/pallets/markupsafe/issues/
|
||||
- Website: https://palletsprojects.com/p/markupsafe/
|
||||
- Twitter: https://twitter.com/PalletsTeam
|
||||
- Chat: https://discord.gg/pallets
|
||||
|
||||
|
||||
@ -0,0 +1,13 @@
|
||||
MarkupSafe-2.0.1.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
|
||||
MarkupSafe-2.0.1.dist-info/LICENSE.rst,sha256=RjHsDbX9kKVH4zaBcmTGeYIUM4FG-KyUtKV_lu6MnsQ,1503
|
||||
MarkupSafe-2.0.1.dist-info/METADATA,sha256=FmPpxBdaqCCjF-XKqoxeEzqAzhetQnrkkSsd3V3X-Jc,3211
|
||||
MarkupSafe-2.0.1.dist-info/RECORD,,
|
||||
MarkupSafe-2.0.1.dist-info/WHEEL,sha256=jr7ubY0Lkz_yXH9FfFe9PTtLhGOsf62dZkNvTYrJINE,100
|
||||
MarkupSafe-2.0.1.dist-info/top_level.txt,sha256=qy0Plje5IJuvsCBjejJyhDCjEAdcDLK_2agVcex8Z6U,11
|
||||
markupsafe/__init__.py,sha256=s08KbuFRV3zh4Wh7xjsIphXgp1xf0EUB79wlPj-4scc,9211
|
||||
markupsafe/__pycache__/__init__.cpython-39.pyc,,
|
||||
markupsafe/__pycache__/_native.cpython-39.pyc,,
|
||||
markupsafe/_native.py,sha256=JMXegJtk1ZcnRKrgyCA-CEXmRnOpaIXLyDAM98GbshY,2061
|
||||
markupsafe/_speedups.cp39-win_amd64.pyd,sha256=hPTsANj9bt7hLYxWLuZcC7E3-EnJQ4GlvIf9Vx0p1p0,16384
|
||||
markupsafe/_speedups.pyi,sha256=f5QtwIOP0eLrxh2v5p6SmaYmlcHIGIfmz0DovaqL0OU,238
|
||||
markupsafe/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
|
||||
@ -0,0 +1,5 @@
|
||||
Wheel-Version: 1.0
|
||||
Generator: bdist_wheel (0.36.2)
|
||||
Root-Is-Purelib: false
|
||||
Tag: cp39-cp39-win_amd64
|
||||
|
||||
@ -0,0 +1 @@
|
||||
markupsafe
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -9,7 +9,7 @@ is_pypy = '__pypy__' in sys.builtin_module_names
|
||||
|
||||
|
||||
warnings.filterwarnings('ignore',
|
||||
'.+ distutils .+ deprecated',
|
||||
r'.+ distutils\b.+ deprecated',
|
||||
DeprecationWarning)
|
||||
|
||||
|
||||
|
||||
Binary file not shown.
Binary file not shown.
@ -1,4 +1,4 @@
|
||||
Metadata-Version: 1.1
|
||||
Metadata-Version: 2.1
|
||||
Name: bottle-websocket
|
||||
Version: 0.2.9
|
||||
Summary: WebSockets for bottle
|
||||
@ -6,7 +6,6 @@ Home-page: https://github.com/zeekay/bottle-websocket
|
||||
Author: Zach Kelling
|
||||
Author-email: zk@monoid.io
|
||||
License: MIT
|
||||
Description: Easy websockets for bottle.
|
||||
Keywords: bottle websockets
|
||||
Platform: UNKNOWN
|
||||
Classifier: Environment :: Web Environment
|
||||
@ -16,3 +15,6 @@ Classifier: Operating System :: OS Independent
|
||||
Classifier: Programming Language :: Python
|
||||
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
|
||||
Classifier: Topic :: Software Development :: Libraries :: Python Modules
|
||||
|
||||
Easy websockets for bottle.
|
||||
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -1,4 +1,4 @@
|
||||
Metadata-Version: 1.1
|
||||
Metadata-Version: 2.1
|
||||
Name: bs4
|
||||
Version: 0.0.1
|
||||
Summary: Screen-scraping library
|
||||
@ -7,7 +7,6 @@ Author: Leonard Richardson
|
||||
Author-email: leonardr@segfault.org
|
||||
License: MIT
|
||||
Download-URL: http://www.crummy.com/software/BeautifulSoup/bs4/download/
|
||||
Description: Use `beautifulsoup4 <https://pypi.python.org/pypi/beautifulsoup4>`_ instead.
|
||||
Platform: UNKNOWN
|
||||
Classifier: Development Status :: 5 - Production/Stable
|
||||
Classifier: Intended Audience :: Developers
|
||||
@ -19,3 +18,6 @@ Classifier: Topic :: Text Processing :: Markup :: HTML
|
||||
Classifier: Topic :: Text Processing :: Markup :: XML
|
||||
Classifier: Topic :: Text Processing :: Markup :: SGML
|
||||
Classifier: Topic :: Software Development :: Libraries :: Python Modules
|
||||
|
||||
Use `beautifulsoup4 <https://pypi.python.org/pypi/beautifulsoup4>`_ instead.
|
||||
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -1,4 +1,4 @@
|
||||
../../Scripts/normalizer.exe,sha256=63XTo-ZCPFkdVNSh7OgEV_EiUDlwQbEO4iTjK_czj_0,106391
|
||||
../../Scripts/normalizer.exe,sha256=Tb318KAuAZX3JDK2YH_V8XoRI9mah1OfwjHG0lkxy0k,106395
|
||||
charset_normalizer-2.0.4.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
|
||||
charset_normalizer-2.0.4.dist-info/LICENSE,sha256=6zGgxaT7Cbik4yBV0lweX5w1iidS_vPNcgIT0cz-4kE,1070
|
||||
charset_normalizer-2.0.4.dist-info/METADATA,sha256=iGaSYKAbW7dltLfO_sIm347XsC5kqKiFrvR3IHolDio,11710
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -1,4 +1,4 @@
|
||||
Metadata-Version: 1.2
|
||||
Metadata-Version: 2.1
|
||||
Name: future
|
||||
Version: 0.18.2
|
||||
Summary: Clean single-source support for Python 3 and 2
|
||||
@ -6,15 +6,34 @@ Home-page: https://python-future.org
|
||||
Author: Ed Schofield
|
||||
Author-email: ed@pythoncharmers.com
|
||||
License: MIT
|
||||
Description:
|
||||
future: Easy, safe support for Python 2/3 compatibility
|
||||
=======================================================
|
||||
Keywords: future past python3 migration futurize backport six 2to3 modernize pasteurize 3to2
|
||||
Platform: UNKNOWN
|
||||
Classifier: Programming Language :: Python
|
||||
Classifier: Programming Language :: Python :: 2
|
||||
Classifier: Programming Language :: Python :: 2.6
|
||||
Classifier: Programming Language :: Python :: 2.7
|
||||
Classifier: Programming Language :: Python :: 3
|
||||
Classifier: Programming Language :: Python :: 3.3
|
||||
Classifier: Programming Language :: Python :: 3.4
|
||||
Classifier: Programming Language :: Python :: 3.5
|
||||
Classifier: Programming Language :: Python :: 3.6
|
||||
Classifier: Programming Language :: Python :: 3.7
|
||||
Classifier: License :: OSI Approved
|
||||
Classifier: License :: OSI Approved :: MIT License
|
||||
Classifier: Development Status :: 4 - Beta
|
||||
Classifier: Intended Audience :: Developers
|
||||
Requires-Python: >=2.6, !=3.0.*, !=3.1.*, !=3.2.*
|
||||
License-File: LICENSE.txt
|
||||
|
||||
``future`` is the missing compatibility layer between Python 2 and Python
|
||||
3. It allows you to use a single, clean Python 3.x-compatible codebase to
|
||||
support both Python 2 and Python 3 with minimal overhead.
|
||||
|
||||
It is designed to be used as follows::
|
||||
future: Easy, safe support for Python 2/3 compatibility
|
||||
=======================================================
|
||||
|
||||
``future`` is the missing compatibility layer between Python 2 and Python
|
||||
3. It allows you to use a single, clean Python 3.x-compatible codebase to
|
||||
support both Python 2 and Python 3 with minimal overhead.
|
||||
|
||||
It is designed to be used as follows::
|
||||
|
||||
from __future__ import (absolute_import, division,
|
||||
print_function, unicode_literals)
|
||||
@ -24,19 +43,19 @@ Description:
|
||||
pow, round, super,
|
||||
filter, map, zip)
|
||||
|
||||
followed by predominantly standard, idiomatic Python 3 code that then runs
|
||||
similarly on Python 2.6/2.7 and Python 3.3+.
|
||||
followed by predominantly standard, idiomatic Python 3 code that then runs
|
||||
similarly on Python 2.6/2.7 and Python 3.3+.
|
||||
|
||||
The imports have no effect on Python 3. On Python 2, they shadow the
|
||||
corresponding builtins, which normally have different semantics on Python 3
|
||||
versus 2, to provide their Python 3 semantics.
|
||||
The imports have no effect on Python 3. On Python 2, they shadow the
|
||||
corresponding builtins, which normally have different semantics on Python 3
|
||||
versus 2, to provide their Python 3 semantics.
|
||||
|
||||
|
||||
Standard library reorganization
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
Standard library reorganization
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
``future`` supports the standard library reorganization (PEP 3108) through the
|
||||
following Py3 interfaces:
|
||||
``future`` supports the standard library reorganization (PEP 3108) through the
|
||||
following Py3 interfaces:
|
||||
|
||||
>>> # Top-level packages with Py3 names provided on Py2:
|
||||
>>> import html.parser
|
||||
@ -56,52 +75,36 @@ Description:
|
||||
>>> from subprocess import getoutput, getstatusoutput
|
||||
|
||||
|
||||
Automatic conversion
|
||||
--------------------
|
||||
Automatic conversion
|
||||
--------------------
|
||||
|
||||
An included script called `futurize
|
||||
<http://python-future.org/automatic_conversion.html>`_ aids in converting
|
||||
code (from either Python 2 or Python 3) to code compatible with both
|
||||
platforms. It is similar to ``python-modernize`` but goes further in
|
||||
providing Python 3 compatibility through the use of the backported types
|
||||
and builtin functions in ``future``.
|
||||
An included script called `futurize
|
||||
<http://python-future.org/automatic_conversion.html>`_ aids in converting
|
||||
code (from either Python 2 or Python 3) to code compatible with both
|
||||
platforms. It is similar to ``python-modernize`` but goes further in
|
||||
providing Python 3 compatibility through the use of the backported types
|
||||
and builtin functions in ``future``.
|
||||
|
||||
|
||||
Documentation
|
||||
-------------
|
||||
Documentation
|
||||
-------------
|
||||
|
||||
See: http://python-future.org
|
||||
See: http://python-future.org
|
||||
|
||||
|
||||
Credits
|
||||
-------
|
||||
Credits
|
||||
-------
|
||||
|
||||
:Author: Ed Schofield, Jordan M. Adler, et al
|
||||
:Sponsor: Python Charmers Pty Ltd, Australia, and Python Charmers Pte
|
||||
:Author: Ed Schofield, Jordan M. Adler, et al
|
||||
:Sponsor: Python Charmers Pty Ltd, Australia, and Python Charmers Pte
|
||||
Ltd, Singapore. http://pythoncharmers.com
|
||||
:Others: See docs/credits.rst or http://python-future.org/credits.html
|
||||
:Others: See docs/credits.rst or http://python-future.org/credits.html
|
||||
|
||||
|
||||
Licensing
|
||||
---------
|
||||
Copyright 2013-2019 Python Charmers Pty Ltd, Australia.
|
||||
The software is distributed under an MIT licence. See LICENSE.txt.
|
||||
Licensing
|
||||
---------
|
||||
Copyright 2013-2019 Python Charmers Pty Ltd, Australia.
|
||||
The software is distributed under an MIT licence. See LICENSE.txt.
|
||||
|
||||
|
||||
|
||||
Keywords: future past python3 migration futurize backport six 2to3 modernize pasteurize 3to2
|
||||
Platform: UNKNOWN
|
||||
Classifier: Programming Language :: Python
|
||||
Classifier: Programming Language :: Python :: 2
|
||||
Classifier: Programming Language :: Python :: 2.6
|
||||
Classifier: Programming Language :: Python :: 2.7
|
||||
Classifier: Programming Language :: Python :: 3
|
||||
Classifier: Programming Language :: Python :: 3.3
|
||||
Classifier: Programming Language :: Python :: 3.4
|
||||
Classifier: Programming Language :: Python :: 3.5
|
||||
Classifier: Programming Language :: Python :: 3.6
|
||||
Classifier: Programming Language :: Python :: 3.7
|
||||
Classifier: License :: OSI Approved
|
||||
Classifier: License :: OSI Approved :: MIT License
|
||||
Classifier: Development Status :: 4 - Beta
|
||||
Classifier: Intended Audience :: Developers
|
||||
Requires-Python: >=2.6, !=3.0.*, !=3.1.*, !=3.2.*
|
||||
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user