Update pinned dependencies in order to use Dash on Py39

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.

[anders-kiaer]

Updated pinned dependency lxml in order to use Dash on Python 3.9 (lxml>=4.5.2 has pre-compiled wheels built for Python 3.9).

---

Has it been considered earlier to remove pinning of test dependencies? I guess the reason originally was to try to achieve reproducible runs, but since the ordinary non-testing dependencies (as well as indirect dependencies) are not pinned this is not the case even with pinned direct test dependencies. And pip install dash[testing] is also a "public API" similarly to pip install dash.

Projects using dash[testing] together with their own test dependencies might face increased version conflicts with pip>=20.3 scheduled to be released this month.

One way of quickly picking up new releases of ordinary + test dependencies breaking the project is to e.g. do scheduled CI runs. This could also be done in combination with e.g. testdependency~=x.y if you want to only allow minor+patch version to update and not major versions (as a step towards loosening up test dependency pinning).

[alexcjohnson]

@anders-kiaer thanks for the PR. Looks like we had overly tight restrictions on CI runs when you submitted this but we've since fixed that - I'll merge once the new test runs pass. 💃

Your point about loosening dash[testing] requirements is well taken, but let's continue that discussion in #1466.