django-json-widget 2.0.2__tar.gz → 2.0.3__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/AUTHORS.rst +29 -29
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/CHANGELOG.rst +60 -57
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/CONTRIBUTING.rst +113 -113
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/LICENSE +14 -14
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/MANIFEST.in +6 -6
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/PKG-INFO +204 -201
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/README.rst +105 -105
- django_json_widget-2.0.3/django_json_widget/__init__.py +1 -0
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/apps.py +6 -6
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/models.py +1 -1
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/static/dist/img/jsoneditor-icons.svg +749 -749
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/static/dist/jsoneditor.min.css +9 -9
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/static/dist/jsoneditor.min.js +85 -85
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/templates/django_json_widget.html +25 -25
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/urls.py +1 -1
- django_json_widget-2.0.3/django_json_widget/widgets.py +45 -0
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget.egg-info/PKG-INFO +204 -201
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget.egg-info/not-zip-safe +1 -1
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/setup.cfg +27 -27
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/setup.py +80 -80
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/tests/test_models.py +23 -23
- django_json_widget-2.0.2/django_json_widget/__init__.py +0 -1
- django_json_widget-2.0.2/django_json_widget/widgets.py +0 -88
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/static/css/django_json_widget.css +0 -0
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget/views.py +0 -0
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget.egg-info/SOURCES.txt +0 -0
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget.egg-info/dependency_links.txt +0 -0
- {django_json_widget-2.0.2 → django_json_widget-2.0.3}/django_json_widget.egg-info/top_level.txt +0 -0
|
@@ -1,29 +1,29 @@
|
|
|
1
|
-
=======
|
|
2
|
-
Credits
|
|
3
|
-
=======
|
|
4
|
-
|
|
5
|
-
Development Lead
|
|
6
|
-
----------------
|
|
7
|
-
|
|
8
|
-
* José Manuel Rivas (jmrivas86) <jmrivas86@gmail.com>
|
|
9
|
-
|
|
10
|
-
Contributors
|
|
11
|
-
------------
|
|
12
|
-
|
|
13
|
-
* Knut Hühne (k-nut)
|
|
14
|
-
* Qiying Wang (WqyJh)
|
|
15
|
-
* Erkin Çakar (travijuu)
|
|
16
|
-
* Vinay Pai (vinaypai)
|
|
17
|
-
* Pedro Miguel Correia (pedroma)
|
|
18
|
-
* Artur BarseghyanArtur Barseghyan (barseghyanartur)
|
|
19
|
-
* Alexandre Voiney (avoiney)
|
|
20
|
-
* Michał Bielawski (D3X)
|
|
21
|
-
* Arcuri Davide (dadokkio)
|
|
22
|
-
* Ling Li (lingster)
|
|
23
|
-
* Steven Mapes (StevenMapes)
|
|
24
|
-
* Stefan Wehrmeyer (stefanw)
|
|
25
|
-
* Michał Bielawski (D3X)
|
|
26
|
-
* Ashok Argent-Katwala (ashokdelphia)
|
|
27
|
-
* Chris Culhane (cfculhane)
|
|
28
|
-
* Amar Sahinovic (amarsahinovic)
|
|
29
|
-
* Erfan Arefmehr (erfan-rfmhr)
|
|
1
|
+
=======
|
|
2
|
+
Credits
|
|
3
|
+
=======
|
|
4
|
+
|
|
5
|
+
Development Lead
|
|
6
|
+
----------------
|
|
7
|
+
|
|
8
|
+
* José Manuel Rivas (jmrivas86) <jmrivas86@gmail.com>
|
|
9
|
+
|
|
10
|
+
Contributors
|
|
11
|
+
------------
|
|
12
|
+
|
|
13
|
+
* Knut Hühne (k-nut)
|
|
14
|
+
* Qiying Wang (WqyJh)
|
|
15
|
+
* Erkin Çakar (travijuu)
|
|
16
|
+
* Vinay Pai (vinaypai)
|
|
17
|
+
* Pedro Miguel Correia (pedroma)
|
|
18
|
+
* Artur BarseghyanArtur Barseghyan (barseghyanartur)
|
|
19
|
+
* Alexandre Voiney (avoiney)
|
|
20
|
+
* Michał Bielawski (D3X)
|
|
21
|
+
* Arcuri Davide (dadokkio)
|
|
22
|
+
* Ling Li (lingster)
|
|
23
|
+
* Steven Mapes (StevenMapes)
|
|
24
|
+
* Stefan Wehrmeyer (stefanw)
|
|
25
|
+
* Michał Bielawski (D3X)
|
|
26
|
+
* Ashok Argent-Katwala (ashokdelphia)
|
|
27
|
+
* Chris Culhane (cfculhane)
|
|
28
|
+
* Amar Sahinovic (amarsahinovic)
|
|
29
|
+
* Erfan Arefmehr (erfan-rfmhr)
|
|
@@ -1,57 +1,60 @@
|
|
|
1
|
-
=========
|
|
2
|
-
Changelog
|
|
3
|
-
=========
|
|
4
|
-
|
|
5
|
-
2.0.
|
|
6
|
-
------------------
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
*
|
|
22
|
-
*
|
|
23
|
-
*
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
*
|
|
55
|
-
*
|
|
56
|
-
|
|
57
|
-
|
|
1
|
+
=========
|
|
2
|
+
Changelog
|
|
3
|
+
=========
|
|
4
|
+
|
|
5
|
+
2.0.3 (2025-07-29)
|
|
6
|
+
------------------
|
|
7
|
+
|
|
8
|
+
2.0.2 (2025-07-28)
|
|
9
|
+
------------------
|
|
10
|
+
|
|
11
|
+
* Fix Version 2.0.1 causes rendering HTML scripts issue #80
|
|
12
|
+
|
|
13
|
+
2.0.1 (2024-03-02)
|
|
14
|
+
------------------=
|
|
15
|
+
|
|
16
|
+
* Fixed Version 2.0.0 causes issues with Django 4.x due to missing sourcemaps issue #83
|
|
17
|
+
|
|
18
|
+
2.0.0 (2024-03-24)
|
|
19
|
+
------------------
|
|
20
|
+
|
|
21
|
+
* Fix default paths for static files #53
|
|
22
|
+
* Stop declaring support for Django versions before 3.2 #65
|
|
23
|
+
* Avoid HTML injection via unsafe JSON injection #64
|
|
24
|
+
* Remove source map reference from JS bundle #70
|
|
25
|
+
* Add dark mode CSS support #82
|
|
26
|
+
* Updated documentation
|
|
27
|
+
|
|
28
|
+
1.1.1 (2021-02-17)
|
|
29
|
+
------------------
|
|
30
|
+
|
|
31
|
+
* Fix for issue #51, updates the bundled libs to 9.1.9 and additional notes for Django 3.1 changes
|
|
32
|
+
|
|
33
|
+
1.1.0 (2021-02-05)
|
|
34
|
+
------------------
|
|
35
|
+
|
|
36
|
+
* Added functionality to override version of JSONEditor to use
|
|
37
|
+
* update readme for django 3.1
|
|
38
|
+
|
|
39
|
+
1.0.1 (2020-04-17)
|
|
40
|
+
------------------
|
|
41
|
+
|
|
42
|
+
* Stop resolving paths to the static files
|
|
43
|
+
|
|
44
|
+
1.0.0 (2020-01-16)
|
|
45
|
+
------------------
|
|
46
|
+
|
|
47
|
+
* Update Makefile
|
|
48
|
+
* Make Stable the project
|
|
49
|
+
|
|
50
|
+
|
|
51
|
+
0.3.0 (2020-01-16)
|
|
52
|
+
------------------
|
|
53
|
+
|
|
54
|
+
* Update requirements.txt
|
|
55
|
+
* Fixed static to work with CDN tools like django-storages
|
|
56
|
+
* Make widget more configurable
|
|
57
|
+
* Fixed an incompatibility with Python 2.7
|
|
58
|
+
* update jsoneditor to latest version
|
|
59
|
+
|
|
60
|
+
|
|
@@ -1,113 +1,113 @@
|
|
|
1
|
-
============
|
|
2
|
-
Contributing
|
|
3
|
-
============
|
|
4
|
-
|
|
5
|
-
Contributions are welcome, and they are greatly appreciated! Every
|
|
6
|
-
little bit helps, and credit will always be given.
|
|
7
|
-
|
|
8
|
-
You can contribute in many ways:
|
|
9
|
-
|
|
10
|
-
Types of Contributions
|
|
11
|
-
----------------------
|
|
12
|
-
|
|
13
|
-
Report Bugs
|
|
14
|
-
~~~~~~~~~~~
|
|
15
|
-
|
|
16
|
-
Report bugs at https://github.com/jmrivas86/django-json-widget/issues.
|
|
17
|
-
|
|
18
|
-
If you are reporting a bug, please include:
|
|
19
|
-
|
|
20
|
-
* Your operating system name and version.
|
|
21
|
-
* Any details about your local setup that might be helpful in troubleshooting.
|
|
22
|
-
* Detailed steps to reproduce the bug.
|
|
23
|
-
|
|
24
|
-
Fix Bugs
|
|
25
|
-
~~~~~~~~
|
|
26
|
-
|
|
27
|
-
Look through the GitHub issues for bugs. Anything tagged with "bug"
|
|
28
|
-
is open to whoever wants to implement it.
|
|
29
|
-
|
|
30
|
-
Implement Features
|
|
31
|
-
~~~~~~~~~~~~~~~~~~
|
|
32
|
-
|
|
33
|
-
Look through the GitHub issues for features. Anything tagged with "feature"
|
|
34
|
-
is open to whoever wants to implement it.
|
|
35
|
-
|
|
36
|
-
Write Documentation
|
|
37
|
-
~~~~~~~~~~~~~~~~~~~
|
|
38
|
-
|
|
39
|
-
django-json-widget could always use more documentation, whether as part of the
|
|
40
|
-
official django-json-widget docs, in docstrings, or even on the web in blog posts,
|
|
41
|
-
articles, and such.
|
|
42
|
-
|
|
43
|
-
Submit Feedback
|
|
44
|
-
~~~~~~~~~~~~~~~
|
|
45
|
-
|
|
46
|
-
The best way to send feedback is to file an issue at https://github.com/jmrivas86/django-json-widget/issues.
|
|
47
|
-
|
|
48
|
-
If you are proposing a feature:
|
|
49
|
-
|
|
50
|
-
* Explain in detail how it would work.
|
|
51
|
-
* Keep the scope as narrow as possible, to make it easier to implement.
|
|
52
|
-
* Remember that this is a volunteer-driven project, and that contributions
|
|
53
|
-
are welcome :)
|
|
54
|
-
|
|
55
|
-
Get Started!
|
|
56
|
-
------------
|
|
57
|
-
|
|
58
|
-
Ready to contribute? Here's how to set up `django-json-widget` for local development.
|
|
59
|
-
|
|
60
|
-
1. Fork the `django-json-widget` repo on GitHub.
|
|
61
|
-
2. Clone your fork locally::
|
|
62
|
-
|
|
63
|
-
$ git clone git@github.com:your_name_here/django-json-widget.git
|
|
64
|
-
|
|
65
|
-
3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
|
|
66
|
-
|
|
67
|
-
$ mkvirtualenv django-json-widget
|
|
68
|
-
$ cd django-json-widget/
|
|
69
|
-
$ python setup.py develop
|
|
70
|
-
|
|
71
|
-
4. Create a branch for local development::
|
|
72
|
-
|
|
73
|
-
$ git checkout -b name-of-your-bugfix-or-feature
|
|
74
|
-
|
|
75
|
-
Now you can make your changes locally.
|
|
76
|
-
|
|
77
|
-
5. When you're done making changes, check that your changes pass flake8 and the
|
|
78
|
-
tests, including testing other Python versions with tox::
|
|
79
|
-
|
|
80
|
-
$ flake8 django_json_widget tests
|
|
81
|
-
$ python setup.py test
|
|
82
|
-
$ tox
|
|
83
|
-
|
|
84
|
-
To get flake8 and tox, just pip install them into your virtualenv.
|
|
85
|
-
|
|
86
|
-
6. Commit your changes and push your branch to GitHub::
|
|
87
|
-
|
|
88
|
-
$ git add .
|
|
89
|
-
$ git commit -m "Your detailed description of your changes."
|
|
90
|
-
$ git push origin name-of-your-bugfix-or-feature
|
|
91
|
-
|
|
92
|
-
7. Submit a pull request through the GitHub website.
|
|
93
|
-
|
|
94
|
-
Pull Request Guidelines
|
|
95
|
-
-----------------------
|
|
96
|
-
|
|
97
|
-
Before you submit a pull request, check that it meets these guidelines:
|
|
98
|
-
|
|
99
|
-
1. The pull request should include tests.
|
|
100
|
-
2. If the pull request adds functionality, the docs should be updated. Put
|
|
101
|
-
your new functionality into a function with a docstring, and add the
|
|
102
|
-
feature to the list in README.rst.
|
|
103
|
-
3. The pull request should work for Python 2.6, 2.7, and 3.3, and for PyPy. Check
|
|
104
|
-
https://travis-ci.org/jmrivas86/django-json-widget/pull_requests
|
|
105
|
-
and make sure that the tests pass for all supported Python versions.
|
|
106
|
-
|
|
107
|
-
Tips
|
|
108
|
-
----
|
|
109
|
-
|
|
110
|
-
To run a subset of tests::
|
|
111
|
-
|
|
112
|
-
$ python -m unittest tests.test_django_json_widget
|
|
113
|
-
|
|
1
|
+
============
|
|
2
|
+
Contributing
|
|
3
|
+
============
|
|
4
|
+
|
|
5
|
+
Contributions are welcome, and they are greatly appreciated! Every
|
|
6
|
+
little bit helps, and credit will always be given.
|
|
7
|
+
|
|
8
|
+
You can contribute in many ways:
|
|
9
|
+
|
|
10
|
+
Types of Contributions
|
|
11
|
+
----------------------
|
|
12
|
+
|
|
13
|
+
Report Bugs
|
|
14
|
+
~~~~~~~~~~~
|
|
15
|
+
|
|
16
|
+
Report bugs at https://github.com/jmrivas86/django-json-widget/issues.
|
|
17
|
+
|
|
18
|
+
If you are reporting a bug, please include:
|
|
19
|
+
|
|
20
|
+
* Your operating system name and version.
|
|
21
|
+
* Any details about your local setup that might be helpful in troubleshooting.
|
|
22
|
+
* Detailed steps to reproduce the bug.
|
|
23
|
+
|
|
24
|
+
Fix Bugs
|
|
25
|
+
~~~~~~~~
|
|
26
|
+
|
|
27
|
+
Look through the GitHub issues for bugs. Anything tagged with "bug"
|
|
28
|
+
is open to whoever wants to implement it.
|
|
29
|
+
|
|
30
|
+
Implement Features
|
|
31
|
+
~~~~~~~~~~~~~~~~~~
|
|
32
|
+
|
|
33
|
+
Look through the GitHub issues for features. Anything tagged with "feature"
|
|
34
|
+
is open to whoever wants to implement it.
|
|
35
|
+
|
|
36
|
+
Write Documentation
|
|
37
|
+
~~~~~~~~~~~~~~~~~~~
|
|
38
|
+
|
|
39
|
+
django-json-widget could always use more documentation, whether as part of the
|
|
40
|
+
official django-json-widget docs, in docstrings, or even on the web in blog posts,
|
|
41
|
+
articles, and such.
|
|
42
|
+
|
|
43
|
+
Submit Feedback
|
|
44
|
+
~~~~~~~~~~~~~~~
|
|
45
|
+
|
|
46
|
+
The best way to send feedback is to file an issue at https://github.com/jmrivas86/django-json-widget/issues.
|
|
47
|
+
|
|
48
|
+
If you are proposing a feature:
|
|
49
|
+
|
|
50
|
+
* Explain in detail how it would work.
|
|
51
|
+
* Keep the scope as narrow as possible, to make it easier to implement.
|
|
52
|
+
* Remember that this is a volunteer-driven project, and that contributions
|
|
53
|
+
are welcome :)
|
|
54
|
+
|
|
55
|
+
Get Started!
|
|
56
|
+
------------
|
|
57
|
+
|
|
58
|
+
Ready to contribute? Here's how to set up `django-json-widget` for local development.
|
|
59
|
+
|
|
60
|
+
1. Fork the `django-json-widget` repo on GitHub.
|
|
61
|
+
2. Clone your fork locally::
|
|
62
|
+
|
|
63
|
+
$ git clone git@github.com:your_name_here/django-json-widget.git
|
|
64
|
+
|
|
65
|
+
3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
|
|
66
|
+
|
|
67
|
+
$ mkvirtualenv django-json-widget
|
|
68
|
+
$ cd django-json-widget/
|
|
69
|
+
$ python setup.py develop
|
|
70
|
+
|
|
71
|
+
4. Create a branch for local development::
|
|
72
|
+
|
|
73
|
+
$ git checkout -b name-of-your-bugfix-or-feature
|
|
74
|
+
|
|
75
|
+
Now you can make your changes locally.
|
|
76
|
+
|
|
77
|
+
5. When you're done making changes, check that your changes pass flake8 and the
|
|
78
|
+
tests, including testing other Python versions with tox::
|
|
79
|
+
|
|
80
|
+
$ flake8 django_json_widget tests
|
|
81
|
+
$ python setup.py test
|
|
82
|
+
$ tox
|
|
83
|
+
|
|
84
|
+
To get flake8 and tox, just pip install them into your virtualenv.
|
|
85
|
+
|
|
86
|
+
6. Commit your changes and push your branch to GitHub::
|
|
87
|
+
|
|
88
|
+
$ git add .
|
|
89
|
+
$ git commit -m "Your detailed description of your changes."
|
|
90
|
+
$ git push origin name-of-your-bugfix-or-feature
|
|
91
|
+
|
|
92
|
+
7. Submit a pull request through the GitHub website.
|
|
93
|
+
|
|
94
|
+
Pull Request Guidelines
|
|
95
|
+
-----------------------
|
|
96
|
+
|
|
97
|
+
Before you submit a pull request, check that it meets these guidelines:
|
|
98
|
+
|
|
99
|
+
1. The pull request should include tests.
|
|
100
|
+
2. If the pull request adds functionality, the docs should be updated. Put
|
|
101
|
+
your new functionality into a function with a docstring, and add the
|
|
102
|
+
feature to the list in README.rst.
|
|
103
|
+
3. The pull request should work for Python 2.6, 2.7, and 3.3, and for PyPy. Check
|
|
104
|
+
https://travis-ci.org/jmrivas86/django-json-widget/pull_requests
|
|
105
|
+
and make sure that the tests pass for all supported Python versions.
|
|
106
|
+
|
|
107
|
+
Tips
|
|
108
|
+
----
|
|
109
|
+
|
|
110
|
+
To run a subset of tests::
|
|
111
|
+
|
|
112
|
+
$ python -m unittest tests.test_django_json_widget
|
|
113
|
+
|
|
@@ -1,14 +1,14 @@
|
|
|
1
|
-
|
|
2
|
-
MIT License
|
|
3
|
-
|
|
4
|
-
Copyright (c) 2017, José Manuel Rivas
|
|
5
|
-
|
|
6
|
-
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
|
|
7
|
-
|
|
8
|
-
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
|
|
9
|
-
|
|
10
|
-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
1
|
+
|
|
2
|
+
MIT License
|
|
3
|
+
|
|
4
|
+
Copyright (c) 2017, José Manuel Rivas
|
|
5
|
+
|
|
6
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
|
|
7
|
+
|
|
8
|
+
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
|
|
9
|
+
|
|
10
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
|
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
include AUTHORS.rst
|
|
2
|
-
include CONTRIBUTING.rst
|
|
3
|
-
include CHANGELOG.rst
|
|
4
|
-
include LICENSE
|
|
5
|
-
include README.rst
|
|
6
|
-
recursive-include django_json_widget *.html *.png *.gif *js *.css *jpg *jpeg *svg *py
|
|
1
|
+
include AUTHORS.rst
|
|
2
|
+
include CONTRIBUTING.rst
|
|
3
|
+
include CHANGELOG.rst
|
|
4
|
+
include LICENSE
|
|
5
|
+
include README.rst
|
|
6
|
+
recursive-include django_json_widget *.html *.png *.gif *js *.css *jpg *jpeg *svg *py
|