semvec/pypi-packages huggingface dataset:
obsidiana 2025.12.1
Tools for working with Obsidian vault(s)
Requires Python: >=3.12
Keywords: notes, notetaking, obsidian

=============
``Obsidiana``
=============

|PyPI| |CI|

.. |PyPI| image:: https://img.shields.io/pypi/v/obsidiana.svg
  :alt: PyPI version
  :target: https://pypi.org/project/obsidiana/

.. |CI| image:: https://github.com/Julian/obsidiana/workflows/CI/badge.svg
  :alt: Build status
  :target: https://github.com/Julian/obsidiana/actions?query=workflow%3ACI

A set of tools for working with (my? your?) Obsidian vault.


Should I Use This?
------------------

If you're not @Julian, possibly not as-is, but I like making my tools public in case they do turn out useful to you, or even so you can tell me if you do similar things yourself, so feel free to peruse or use.


What's in a Name
----------------

"Obsidiana" is spanish for Obsidian.
Unlike ``obsidian`` it also wasn't yet taken on PyPI.
problematic-source 0.1.0
Add your description here
Requires Python: >=3.13

# problematic-source

This program provides a number of heuristics to find pre-generated files within
a codebase, and to report on those problems.

The program is quite straightforward to use. Simply point it to a tarball, git
repository, or something else, wait a few seconds to minutes, and then create a
report on the pre-generated files within the codebase. Eg:

```
python3 main.py -o report.txt coreutils.tar.gz
```

## Known Issues

- This program is still fairly rough around the edges. Problems are to be expected.
- Sometimes, you may come up with a new heuristic that you think makes sense in
  general. Create a PR or issue.

## Reporting

The report's primary purpose is for live-bootstrap, so the categories are
created with that in mind. The report exists to help you document your findings.