Merge remote-tracking branch 'origin/master' into 1.0.0-release

# Conflicts:
#	CHANGELOG.md
#	dash/version.py

Author: Marc-André Rivet

.circleci/requirements/dev-requirements-py37.txt

@@ -1,4 +1,4 @@
-dash_core_components==0.35.1
+dash_core_components>=0.40.2
 dash_html_components==0.12.0rc3
 dash-flow-example==0.0.3
 dash-dangerously-set-inner-html

.circleci/requirements/dev-requirements.txt

@@ -1,4 +1,4 @@
-dash_core_components==0.35.1
+dash_core_components>=0.40.2
 dash_html_components>=0.12.0rc3
 dash_flow_example==0.0.3
 dash-dangerously-set-inner-html

.pylintrc

@@ -58,7 +58,9 @@ disable=fixme,
         missing-docstring,
         invalid-name,
         too-many-lines,
-        old-style-class
+        old-style-class,
+        superfluous-parens
+
 # Enable the message, report, category or checker with the given id(s). You can
 # either give multiple identifier separated by comma (,) or put this option
 # multiple time (only on the command line, not in the configuration file where

.pylintrc37

@@ -146,7 +146,8 @@ disable=invalid-name,
         no-else-return,
         useless-object-inheritance,
         possibly-unused-variable,
-        too-many-lines
+        too-many-lines,
+        too-many-statements
 
 # Enable the message, report, category or checker with the given id(s). You can
 # either give multiple identifier separated by comma (,) or put this option

CHANGELOG.md

@@ -1,6 +1,35 @@
-## [1.0.0-rc1] - 2018-11-12
+## [1.0.0a1] - 2018-12-17
 ### Changed
-- Updated `react` and `react-dom` in other Dash repo's to version `16.6.1`. Upgrading to React 16 includes some small breaking changes, discussed [here](https://reactjs.org/blog/2017/09/26/react-v16.0.html#breaking-changes)
+- Initial Dash 1.0 alpha release [#3](https://github.com/plotly/dash-core/issues/3)
+
+## 0.33.0 - 2018-12-10
+## Added
+- Added specific Dash exception types to replace generic exceptions (InvalidIndexException, DependencyException, ResourceException) [#487](https://github.com/plotly/dash/pull/487)
+
+## 0.32.2 - 2018-12-09
+## Fixed
+- Fix typo in missing events/inputs error message [#485](https://github.com/plotly/dash/pull/485)
+
+## 0.32.1 - 2018-12-07
+## Changed
+- Muted dash related missing props docstring from extract-meta warnings [#484](https://github.com/plotly/dash/pull/484)
+
+## 0.32.0 - 2018-12-07
+## Added
+- Support for .map file extension and dynamic (on demand) loading [#478](https://github.com/plotly/dash/pull/478)
+
+## 0.31.1 - 2018-11-29
+## Fixed
+- Fix `_imports_.py` indentation generation. [#473](https://github.com/plotly/dash/pull/473/files)
+
+## 0.31.0 - 2018-11-29
+## Added
+- Combined `extract-meta` and python component files generation in a cli [#451](https://github.com/plotly/dash/pull/451)
+
+## 0.30.0 - 2018-11-14
+## Added
+- Hot reload from the browser [#362](https://github.com/plotly/dash/pull/362)
+- Silence routes logging with `dev_tools_silence_routes_logging`.
 
 ## 0.29.0 - 2018-11-06
 ## Added
@@ -92,7 +121,7 @@
 - Take configs values from init or environ variables (Prefixed with `DASH_`). [#322](https://github.com/plotly/dash/pull/322)
 
 ## Fixed
-- Take `requests_pathname_prefix` config when creating scripts tags. 
+- Take `requests_pathname_prefix` config when creating scripts tags.
 - `requests/routes_pathname_prefix` must starts and end with `/`.
 - `requests_pathname_prefix` must ends with `routes_pathname_prefix`. If you supplied both `requests` and `routes` pathname before this update, make sure `requests_pathname_prefix` ends with the same value as `routes_pathname_prefix`.
 - `url_base_pathname` set both `requests/routes` pathname, cannot supply it with either `requests` or `routes` pathname prefixes.

CONTRIBUTING.md

@@ -86,7 +86,7 @@ _For larger features, your contribution will have a higher likelihood of getting
 - [ ] If significant enough, you have created an issue about documenting the new feature or change and you have added it to the [Documentation] project.
 - [ ] You have created a pull request in [Dash Docs] with the new release of your feature by editing that project's [`requirements.txt` file](https://github.com/plotly/dash-docs/blob/master/requirements.txt) and you have assigned `@chriddyp` to review.
 
-### Versioning Policy
+## Versioning Policy
 This repository adheres to [semver](https://semver.org/). The following policy is in effect for `dash`, `dash-core-components`, `dash-html-components` and `dash-renderer`:
 1. Matching major version numbers are guarenteed to work together.
 2. Any change to the public API (breaking change) will increase a major version.
@@ -95,17 +95,17 @@ This repository adheres to [semver](https://semver.org/). The following policy i
 
 ### Major Release Candidate Window
 1. The major release candidate window will be announced internally at Plotly and through our popular community channels.
-2. Within one day `dash`, `dash-core-components`, `dash-html-components` and `dash-renderer` master branches will be reversioned as `N.0.0-rc1` and published.
+2. `dash`, `dash-core-components`, `dash-html-components` and `dash-renderer` master branches will be reversioned as `N.0.0-rc1` on the same day and published for testing.
 3. Pull requests especially those containing breaking changes will be merged.
 4. Per repo tests will be updated to target the latest `rc` versions.
 5. [dash-docs](https://github.com/plotly/dash-docs), some apps in the [dash gallery](https://dash.plot.ly/gallery) and Plotly internal projects will be updated to target the latest `rc` versions.
 6. steps 3-5 will continue until all breaking changes have been merged.
 7. A major release candidate freeze will go into effect. During this time steps 3-5 will continue but only bug fixes will be merged.
-8. Within one day `dash`, `dash-core-components`, `dash-html-components` and `dash-renderer` master branches will be reversioned as `N.0.0` and published ending the major release cnadidate window.
+8. Once testing and Q/A is complete `dash`, `dash-core-components`, `dash-html-components` and `dash-renderer` master branches will be reversioned as `N.0.0` and published ending the major release candidate window.
 
 ### Backporting fixes
 During and after the major release candidate window bug fixes that can apply to pre-major release candidate releases should be backported. This is accomplished by:
-1. If a pre-major release branch does not exist then check out a branch at the tag defining the last published release before the previous major release candidate window began. For example if we are in the `1.x` series and the last pre-`1.x` series release is `v0.18.1` checkout a branch at `0.18.1` called `0.18-release`. If the branch does exist check it out.
+1. If a pre-major release branch does not exist then check out a branch at the tag defining the last published release before the previous major release candidate window began. For example if we are in the `1.x` series and the last pre-`1.x` series release is `v0.18.1` checkout a branch at `v0.18.1` called `0.18-release`. If the branch does exist check it out.
 2. Cherry-pick or otherwise reapply the fix to the pre-major release branch and update the patch version. In the example above the new version and tag will be `v0.18.2` on the `0.18-release` branch.
 3. Publish.
 

MANIFEST.in

@@ -1,3 +1,4 @@
 include README.md
 include LICENSE
 include dash/favicon.ico
+include dash/extract-meta.js

dash/_configs.py

@@ -22,7 +22,12 @@ def env_configs():
         'DASH_COMPONENTS_CACHE_MAX_AGE',
         'DASH_INCLUDE_ASSETS_FILES',
         'DASH_SERVE_DEV_BUNDLES',
-        'DASH_DEBUG'
+        'DASH_DEBUG',
+        'DASH_HOT_RELOAD',
+        'DASH_HOT_RELOAD_INTERVAL',
+        'DASH_HOT_RELOAD_WATCH_INTERVAL',
+        'DASH_HOT_RELOAD_MAX_RETRY',
+        'DASH_SILENCE_ROUTES_LOGGING'
     )})
 
 

dash/_utils.py

@@ -1,3 +1,6 @@
+import uuid
+
+
 def interpolate_str(template, **data):
     s = template
     for k, v in data.items():
@@ -20,12 +23,15 @@ def format_tag(tag_name, attributes, inner='', closed=False, opened=False):
             '{}="{}"'.format(k, v) for k, v in attributes.items()]))
 
 
+def generate_hash():
+    return str(uuid.uuid4().hex).strip('-')
+
+
 def get_asset_path(
         requests_pathname,
         routes_pathname,
         asset_path,
         asset_url_path):
-
     i = requests_pathname.rfind(routes_pathname)
     req = requests_pathname[:i]
 

dash/_watch.py

@@ -0,0 +1,36 @@
+import collections
+import os
+import re
+import time
+
+
+def watch(folders, on_change, pattern=None, sleep_time=0.1):
+    pattern = re.compile(pattern) if pattern else None
+    watched = collections.defaultdict(lambda: -1)
+
+    def walk():
+        walked = []
+        for folder in folders:
+            for current, _, files, in os.walk(folder):
+                for f in files:
+                    if pattern and not pattern.search(f):
+                        continue
+                    path = os.path.join(current, f)
+
+                    info = os.stat(path)
+                    new_time = info.st_mtime
+
+                    if new_time > watched[path] > 0:
+                        on_change(path, new_time, False)
+
+                    watched[path] = new_time
+                    walked.append(path)
+
+        # Look for deleted files
+        for w in [x for x in watched.keys() if x not in walked]:
+            del watched[w]
+            on_change(w, -1, True)
+
+    while True:
+        walk()
+        time.sleep(sleep_time)