pyiron / snippets / 9272810986
95%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 11
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 91.741% (+2.2%) from 89.504%
9272810986

push

github

web-flow 
Base stuff (#6)

* move tests_base to tests

* Replace pyiron.base with pyiron_base

* Add decorator for deprecation warnings

* Add support for pending deprecation

* Fix codacy nags

* Fix docstring markup

* Add ability to deprecate single arguments

* Allow passing deprecated arguments via kwargs

* Add a util class for import warnings (#116)

* Add a util class for import warnings

* Add docstring

* Add test

* Add context manager

Co-authored-by: Marvin Poul <ponder@creshal.de>

* Copy deprecator instance on decorating

Decorating a function with the Deprecator can change its instance
attributes (if you pass arguments when decorating).  That means that
when decorating different functions the warning shown used only the
arguments from the last call to the deprecator instance.

This is fixed now by copying the deprecator instance before wrapping the
given function.

* Using the new TestCase module

* Fixing imports

* Refactoring

* Corrections as discussed in the pyiron meeting

* black formatting

* Add function to retry until error goes away

We had a pattern for this in multiple places (talking to the database or
hdf5 file).

* Add tests

* Small nits

* Fix typo

* Format black

* Small nits

* Rename atmost -> at_most

* Rename atmost -> at_most

* Call all the single supers!

* add ruff linter

* add ruff linter

* Move files into snippets hierarchy

* Sanitize deprecator

* Remove tests for stuff that wasn't transferred

* Split retry and import_alarm

* Move the missed test file into the snippets hierarchy

* Refactor: rename test file

* Break apart deprecate and import_alarm tests

* Fix deprecator tests

* Fix retry tests

* Update import_alarm tests

* Fix tests to catch failures instead of warnings

Catching warnings can be janky, e.g. if some upstream dependency starts getting a deprecation warning (possible even depending only on the sta... (continued)

411 of 448 relevant lines covered (91.74%)

0.92 hits per line

Jobs
ID Job ID Ran Files Coverage
1 9272810986.1 11
91.74
 GitHub Action Run
Source Files on build 9272810986