@@ -55,9 +55,25 @@ Now you should be able to restart the webpack process (in `dash2/renderer`:
55
55
` ctrl-c ` , ` npm start ` ), after which webpack will automatically pick up new
56
56
changes to the component suite.
57
57
58
+ ## Installing python package locally
59
+
60
+ You don't need publishing access to test the module locally.
61
+
62
+ ``` sh
63
+ # Install in `site-packages` on your machine
64
+ $ python setup.py install
65
+ ```
66
+
58
67
## Publishing
59
68
60
- Ask @coopy or @chriddyp to be added to the [ NPM package authors] [ ] .
69
+ For now, two different workflows are necessary for publishing to NPM and PyPi,
70
+ respectively. TODO:
71
+ [ #5 ] ( https://github.com/plotly/dash-components-archetype/issues/5 ) will roll up
72
+ publishing steps into one workflow.
73
+
74
+ Ask @chriddyp to be added to the [ NPM package authors] [ ] or to [ PyPi] [ ] .
75
+
76
+ ### Publishing to NPM
61
77
62
78
``` sh
63
79
# Bump the package version
@@ -70,6 +86,20 @@ $ git push --follow-tags
70
86
$ npm publish
71
87
```
72
88
89
+ ### Publishing to PyPi
90
+
91
+ ``` sh
92
+ # Bump the package version
93
+ $ vi setup.py
94
+
95
+ # Commit to github
96
+ $ git add setup.py
97
+ $ git commit -m " Bump pypi package version to vx.x.x"
98
+
99
+ # Publish to PyPi
100
+ $ npm run publish-pypi
101
+ ```
102
+
73
103
## Builder / Archetype
74
104
75
105
We use [ Builder] [ ] to centrally manage build configuration, dependencies, and
@@ -81,4 +111,5 @@ scripts. See the [dash-components-archetype][] repo for more information.
81
111
[ dash-components-archetype ] : https://github.com/plotly/dash-components-archetype
82
112
[ MDN HTML attribute reference ] : https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes
83
113
[ NPM package authors ] : https://www.npmjs.com/package/dash-html-components/access
114
+ [ PyPi ] : https://pypi.python.org/pypi
84
115
0 commit comments