![]() * Added Markdown v3.3.4 explicitly to requirements.txt, to fix breaking change caused by 3.3. * added logic to prevent duplicating fstab entries * Ubuntu quiet script fix for 1337-server/automatic-ripping-machine issue #111 * Ubuntu loud script fix for 1337-server/automatic-ripping-machine issue #111 * updated the clone command for testing updated requirements * Putting alsa install first to hopefully fix continuing error calling aplay in scripts * Added Markdown v3.3.4 explicitly to requirements.txt, to fix breaking change caused by 3.3.5 (see Python-Markdown/markdown#1203) * Added installs for lsscsi and net-tools * Added handling for arm group/user already existing ![]() * added ALSA install to script to avoid breakage on Ubuntu Server instances * pycharm runs as "other", so the 777 is needed * grab the ip of the site that's now running * moved dev environment installation location * fix command to properly run without hanging script * hard-coding path since the user folder is already created * added logic to run proper installation function * added handling harness for script options I discovered that pip6 support python version constraint so it could be something like that (didn't test it): With the lighter constraint, i'll be able to have markdown installed in every python3.6 -> 3.10 ecosystem but that is expected as flake8 does not support python3.10 yet (nor 3.9). On python3.10 flake8 will be the bad guy. On a python3.6->3.9 I won't be able to install the latest markdown -> conflict I'm a user of both flake8 and markdown (requirements.txt only contains flake8 and markdown). I'm downgrading markdown to 3.3.4 due to that but it makes me sad. So I would suggest restricting importlib-metadata to >=3.0.0 to keep backward dependencies compatible code with the ecosystem (who is not up to date with python 3.10 which requires 4.4 ) ). Regarding this closed issue, I also ran into a dependency problem regarding the latest markdown pushing importlib-metadata>=4.4 and latest flake8 constraining it to importlib-metadata3.10.Īccording to importlib-metadata Changelog the needs only 3.0.0 to support python 3.6. Hope this makes sense, please let me know if I can provide more examples. loosen the importlib-metadata version requirement, wrap the INSTALLED_EXTENSIONS statements in a try/except block and handle the case where an earlier version of importlib-metadata is installed.TypeError: entry_points() got an unexpected keyword argument 'group'įrom the user's perspective, the expectation with projects using semver is that any potentially breaking change will cause a major version bump. INSTALLED_EXTENSIONS = metadata.entry_points(group='markdown.extensions') Venv/lib/python3.7/site-packages/markdown/util.py:88: in Venv/lib/python3.7/site-packages/markdown/core.py:26: in ![]() core import Markdown, markdown, markdownFromFile # noqa: E402 Venv/lib/python3.7/site-packages/markdown/_init_.py:29: in įrom. ![]() ![]()
0 Comments
Leave a Reply. |