A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": [
"https://join-lemmy.org/context.json",
"https://www.w3.org/ns/activitystreams"
],
"type": "Page",
"id": "https://programming.dev/post/24160206",
"attributedTo": "https://programming.dev/u/logging_strict",
"to": [
"https://programming.dev/c/python",
"https://www.w3.org/ns/activitystreams#Public"
],
"name": "PEP 735 does dependency group solve anything?",
"cc": [],
"content": "<p>PEP 735 what is it’s goal? Does it solve our dependency hell issue?</p>\n<p>A deep dive and out comes this limitation</p>\n<p><strong>The mutual compatibility of Dependency Groups is not guaranteed.</strong></p>\n<p>– <a href=\"https://peps.python.org/pep-0735/#lockfile-generation\">peps.python.org/pep-0735/#lockfile-generation</a></p>\n<p>Huh?! Why not?</p>\n<p><strong>mutual compatibility or go pound sand!</strong></p>\n<pre style=\"background-color:#ffffff;\">\n<span style=\"color:#323232;\">pip install -r requirements/dev.lock\n</span><span style=\"color:#323232;\">pip install -r requirements/kit.lock -r requirements/manage.lock\n</span></pre>\n<p>The above code, purposefully, does not afford pip a fighting chance.\nIf there are incompatibilities, it’ll come out when trying randomized\ncombinations.</p>\n<p>Without a means to test for and guarantee mutual compatibility, end users\nwill <strong>always</strong> find themselves in dependency hell.</p>\n<p>Any combination of requirement files (or dependency groups),\n<strong>intended for the same venv</strong>, MUST always work!</p>\n<p>What if this is scaled further, instead of one package, a chain of packages?!</p>\n",
"mediaType": "text/html",
"source": {
"content": "PEP 735 what is it's goal? Does it solve our dependency hell issue?\n\nA deep dive and out comes this limitation\n\n**The mutual compatibility of Dependency Groups is not guaranteed.**\n\n-- https://peps.python.org/pep-0735/#lockfile-generation\n\nHuh?! Why not?\n\n**mutual compatibility or go pound sand!**\n\n```\npip install -r requirements/dev.lock\npip install -r requirements/kit.lock -r requirements/manage.lock\n```\n\nThe above code, purposefully, does not afford pip a fighting chance.\nIf there are incompatibilities, it'll come out when trying randomized\ncombinations.\n\nWithout a means to test for and guarantee mutual compatibility, end users\nwill **always** find themselves in dependency hell.\n\nAny combination of requirement files (or dependency groups),\n**intended for the same venv**, MUST always work!\n\nWhat if this is scaled further, instead of one package, a chain of packages?!",
"mediaType": "text/markdown"
},
"attachment": [
{
"href": "https://peps.python.org/pep-0735/",
"mediaType": "text/html; charset=utf-8",
"type": "Link"
}
],
"sensitive": false,
"published": "2025-01-17T02:13:13.921200Z",
"audience": "https://programming.dev/c/python",
"tag": [
{
"href": "https://programming.dev/post/24160206",
"name": "#python",
"type": "Hashtag"
}
]
}