Staticjinja

Latest version: v5.0.0

Safety actively analyzes 629811 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

3.0.1

----------------------------------------------------------------------------------------

Fixed
^^^^^

* Formatting error in this changelog.

3.0.0

----------------------------------------------------------------------------------------

Changed
^^^^^^^

* Calling ``python3 -m staticjinja`` now works exactly the same as calling
``staticjinja`` directly. If you were using ``python3 -m staticjinja``, this
probably broke you, you now need to explicitly give the ``watch`` subcommand
with ``python3 -m staticjinja watch``. For more info see
https://github.com/staticjinja/staticjinja/issues/152.

2.1.0

----------------------------------------------------------------------------------------

Deprecated
^^^^^^^^^^

* Deprecate inferring project root directory from build script directory.
In the future, if staticjinja ever receives a relative path, it will use
the CWD as the root. If you rely upon the location of your build script
that uses the staticjinja API, then you may need to change. If you're just
using the CLI, then you don't need to change anything.
See https://github.com/staticjinja/staticjinja/issues/149 for more info.

2.0.1

----------------------------------------------------------------------------------------

Added
^^^^^

* A failed attempt at auto release when the version number is bumped. Nothing
actually changed here.

2.0.0

----------------------------------------------------------------------------------------

Deprecated
^^^^^^^^^^

* Renamed ``Site.get_dependencies()`` to ``Site.get_dependents()``.
See https://github.com/staticjinja/staticjinja/commit/170b027a4fff86790bc69a1222d7b0a36c1080bc

Changed
^^^^^^^

* Improved CLI help message formatting

* Revert the change made in 71_. Ensuring output locations exist should be the
responsibility of the custom render function, since there's no guarantee
what output locations the custom render function might use. This might only
affect those using custom render functions.

* Slightly changed the return type of ``Site.get_dependencies()``.
See https://github.com/staticjinja/staticjinja/commit/170b027a4fff86790bc69a1222d7b0a36c1080bc

* Make Reloader piggyback off of Site's logger, so we don't have any bare print statements
dangling about.

.. _71: https://github.com/staticjinja/staticjinja/pull/71


Added
^^^^^

* Many ``Site`` functions now accept PathLike args, not just str's or template names.
See https://github.com/staticjinja/staticjinja/commit/a662a37994ccd1e6b5d37c1bd4666ac30c74899d

Fixed
^^^^^

* Fix and improve the ``markdown`` example.

* Change from inspect.isfunction() -> callable(), per 143_.
Now you should be able to use methods which are instance members of classes.

* Docs: Fix docstring for ``Site.render_template``.

* Make Renderer call super() correctly. It's deprecated, so probably no point, but
might as well fix it.

* Internal: Made flake8 check actually runs against files, other small fixups

.. _143: https://github.com/staticjinja/staticjinja/issues/145

1.0.4

----------------------------------------------------------------------------------------

Changed
^^^^^^^

* Contributing info is updated/improved.

* CLI help message is better formatted and more useful. How it works shouldn't
have changed.

* Internal: Use ``poetry`` as our package manager. This should change the
development workflow but not the user experience.

* Internal: Moved many tests/checks out of tox and into Makefile.

* Internal: Use black as our formatter.

* Improve some tests and add some more CLI tests.

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.