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/24582623",
"attributedTo": "https://programming.dev/u/logging_strict",
"to": [
"https://programming.dev/c/python",
"https://www.w3.org/ns/activitystreams#Public"
],
"name": "Whats in a Python tarball",
"cc": [],
"content": "<p>From helping other projects have run across a fundamental issue which web searches have not given appropriate answers.</p>\n<p>What should go in a tarball and what should not?</p>\n<p>Is it only the build files, python code, and package data and nothing else?</p>\n<p>Should it include tests/ folder?</p>\n<p>Should it include development and configuration files?</p>\n<p>Have seven published packages which include almost all the files and folders. Including:</p>\n<p>.gitignore,</p>\n<p>.gitattributes,</p>\n<p>.github folder tree,</p>\n<p>docs/,</p>\n<p>tests/,</p>\n<p>Makefile,</p>\n<p>all config files,</p>\n<p>all tox files,</p>\n<p>pre-commit config file</p>\n<p>My thinking is that the tarball should have everything needed to maintain the package, but this belief has been challenged. That the tarball is not appropriate for that.</p>\n<p>Thoughts?</p>\n",
"mediaType": "text/html",
"source": {
"content": "From helping other projects have run across a fundamental issue which web searches have not given appropriate answers.\n\nWhat should go in a tarball and what should not?\n\nIs it only the build files, python code, and package data and nothing else?\n\nShould it include tests/ folder?\n\nShould it include development and configuration files?\n\nHave seven published packages which include almost all the files and folders. Including:\n\n.gitignore, \n\n.gitattributes, \n\n.github folder tree, \n\ndocs/, \n\ntests/, \n\nMakefile, \n\nall config files, \n\nall tox files, \n\npre-commit config file\n\nMy thinking is that the tarball should have everything needed to maintain the package, but this belief has been challenged. That the tarball is not appropriate for that.\n\nThoughts?",
"mediaType": "text/markdown"
},
"attachment": [],
"sensitive": false,
"published": "2025-01-27T05:51:45.303180Z",
"updated": "2025-01-27T12:34:11.043333Z",
"audience": "https://programming.dev/c/python",
"tag": [
{
"href": "https://programming.dev/post/24582623",
"name": "#python",
"type": "Hashtag"
}
]
}