# Rattr rats on your attrs.
Rattr (pronounced 'ratter') is a tool to determine attribute usage in python functions. It can parse python files, follow imports and then report to you about the attributes accessed by function calls in that file.
# Status
Currently this project is under active development and likely to change significantly in the future. However we hope it might be useful and interesting to the wider python community.
# But why?
We developed rattr to help with some analytics work in python where type checkers like mypy and pyre are cumbersome.
In analytics work, we often have functions that look like this:
```python
def compute_cost_effectiveness(person):
return person.sales / person.salary
```
because we're pythonistas, the exact type of `person` is unimportant to us in this example - what's important is that it has a sales and salary attribute and that those are numbers. Annotating this function with that information for mypy would be cumbersome - and with thousands of functions it would be hard to do.
Rattr is a tool that solves the first part of this - it can detect that `compute_cost_effectiveness` needs to access "sales" and "salary" attributes and so it could tell us that the following would fail:
```python
def create_report():
people = some_database.query(Person.name, Person.sales).all()
return {person.name: compute_cost_effectiveness(person) for person in people}
```
It can also effectively compute the provenance of attributes. Suppose that you have a wide array of functions for computing information about financial products - like
```python
def compute_some_complex_risk_metric_for(security, other_data):
# proprietary and complicated logic here
security.riskiness = bla
return security
```
and you have other functions that consume that information:
```python
def should_i_buy(security):
if security.riskiness > 5:
return False
# More logic here ...
```
rattr can help you determine which functions are required for a calculation. Effectively allowing you to build powerful directed graph structures for your function libraries.
# Configuration
Rattr is configurable both via pyproject.toml and the command line.
## Command Line Args:
```
-h, --help show this help message and exit
-v, --version show program's version number and exit
-f {0,1,2,3}, --follow-imports {0,1,2,3}
follow imports level meanings:
0 - do not follow imports
1 - follow imports to local modules (default)
2 - follow imports to local and pip installed modules
3 - follow imports to local, pip installed, and stdlib modules
NB: following stdlib imports when using CPython will cause issues
-F PATTERN, --exclude-import PATTERN
do not follow imports to modules matching the given pattern, regardless of the
level of -f
-x PATTERN, --exclude PATTERN
exclude functions and classes matching the given regular expression from being
analysed
-w {none,file,all,ALL}, --show-warnings {none,file,all,ALL}
show warnings level meaning:
none - do not show warnings
file - show warnings for <file>
all - show warnings for all files (default)
All - show warnings for all files, including low-priority
NB: errors and fatal errors are always shown
-p {none,short,full}, --show-path {none,short,full}
show path level meaning:
none - do not show the file path in errors/warnings
short - show an abbreviated path (default)
full - show the full path
E.g.: "/home/user/very/deep/dir/path/file" becomes "~/.../dir/path/file"
--strict run rattr in strict mode, i.e. fail on any error
--permissive THRESHOLD
run rattr in permissive mode, with the given badness threshold (when threshold
is zero or omitted, it is taken as infinite) (default: --permissive 0 when
group omitted)
typical badness values:
+0 - info
+1 - warning
+5 - error
+∞ - fatal
NB: badness is only contributed to by the target <file> and by the
simplification stage (e.g. resolving function calls, etc).
-i, --show-ir show the IR for the file and imports
-r, --show-results show the results of analysis
-s, --show-stats show stats Rattr statisitics
-S, --silent show only errors and warnings
--cache CACHE the file to cache the results to, if successful
<filter-string> filter the output to functions matching the given regular expression
<file> the Python source file to analyse
```
## pyproject.toml
Example toml config:
```toml
[tool.rattr]
follow-imports = 0 # options are: (0, 1, 2, 3)
strict = true
# permissive = 1 # (can be any positive int & mutex with 'strict = true')
silent = true
# show-ir = true # (mutex with 'silent = true')
# show-results = true # (mutex with 'silent = true')
# show-stats = true # (mutex with 'silent = true')
show-path = 'none' # options are: ('none', 'short', 'full')
show-warnings = 'none' # options are: ('none', 'file', 'all', 'ALL')
exclude-import = [
'a\.b\.c.*',
'd\..*',
'^e$'
]
exclude = [
'a_.*',
'b_.*',
'_c.*',
]
cache = 'cache.json'
```
Without setting any command line or toml arguments specifically, the default configuration for rattr is the following:
```toml
[tool.rattr]
follow-imports = 1
permissive = 0
show-ir = false
show-results = true
show-stats = false
show-path = 'short'
show-warnings = 'all'
exclude-import = []
exclude = []
cache = ''
```
# Developer Notes
## Use of Undocumented Behaviour
In `rattr/analyser/types.py` several `Union` types are defined for
convenience. In Python 3.8 to check if the variable `a` is an instance of any
of the types within the `Union` the `typing` module provides `get_args` i.e.
one would use `isinstance(a, get_args(UnionTypeName))`. However, this function
is not provided in Python 3.7 and so the undocumented attribute `__args__` of
the `UnionTypeName` must be used i.e. `isinstance(a, UnionTypeName.__args__)`.
As this is undocumented it should be changed when we upgrade to Python 3.8+
(and `$EDITOR` will not syntax highlight or tab-complete it).
## Annotations
Rattr provides the ability to annotate functions in the target file such that
they may be ignored completely, ignored with their results determined manually,
etc. Additionally, each assertor may provide it's own annotations to ignore
and/or define behaviour.
General Rattr annotations are located in `rattr/analyser/annotations.py` and
assertor specific annotations are to be added by the assertion developer --
however they should be placed in the file containing the `Assertor` class.
### Annotation Format
Annotations should take the form `rattr_<annotation_name>` to avoid namespace
conflicts in importing code.
### Detecting and Parsing Annotations
The `rattr/analyser/utils.py` file provides the following annotation utility
functions:
* `has_annotation(name: str, fn: ast.FunctionDef) -> bool`
* `get_annotation(name: str, fn: ast.FunctionDef) -> Optional[ast.AST]`
* `parse_annotation(name: str, fn: ast.FunctionDef) -> Dict[str, Any]`
* `parse_rattr_results_from_annotation(fn: ast.FunctionDef) -> Dict[str, Literal[...]]:`
* `safe_eval(expr: ast.expr, culprit: Optional[ast.AST]) -> Union[Literal, Iterable[Iterable[...[Literal]]]]`
* `is_name(name: Any) -> bool`
* `is_set_of_names(set_of_names: Any) -> bool`
* `is_args(args: Any) -> bool`
### Provided Annotations
Annotation Name | Location
:-------------------------------------------|:--------------------------------
`rattr_ignore` | `rattr/analyser/annotations.py`
`rattr_results(<results>)` | `rattr/analyser/annotations.py`
### Results Annotation Grammar
```python
@rattr_results(
sets={"a", "b.attr"},
calls=[
("callee_function", (["arg", "another"], {"kwarg": "some_var"}))
]
)
def decorated_function(...):
# ...
```
Any argument to the decorator can be omitted and a default value will be used.
## Known Issues
Nested functions are not currently analysed properly, functions containing
nested functions must be annotated manually.
Comprehensions are not fully analysed, should be solvable by the same approach
as nested functions -- "un-nest" them.
--------------------------------------------------------------------------------
# Usage Notes
See `python rattr -h`.
## Errors and Warnings
Rattr can give five types of error/warnings: raised Python errors, output
beginning with "info:" or "warning:", output beginning with "error:", and
output beginning with "fatal:". The former can be seen as a developer caused
error, and the latter four are user errors.
### User Error: "info" and "warning"
Warns the user of potential issues or bad practise that should not affect the
results of analysis. Low-priority (often class based) warnings begin with
"info".
### User Error: "error"
Warns the user of potential issues or bad practise that will likely affect the
results of analysis (though there are times when the results will still be
correct).
### User Error: "fatal"
Warns the user of potential issues or bad practise so severe that the results
can not be produced for the given file.
## Results Structure
A dictionary from functions to results, which is in turn a dictionary of the
variables, attributes, etc (collectively nameables) that are get, set, called,
or deleted.
## Nameables Format
Pythonic Name | Python Example | Rattr Result Format
:---------------|:------------------------------|:---------------------
Name | `name` | `name`
Starred | `*name` | `*name`
Attribute | `name.attr` | `name.attr`
Call | `name(a, b, ...)` | `name()`
Subscript | `name[0]` or `name['key']` | `name[]`
The above can be nested in Rattr as in Python, for example the Python snippet
`name.method(arg_one, arg_two, ...).result_attr['some key']` will become
`name.method().result_attr[]`.
However, some expression do not have resolvable names. For example, given the
class `A` and instances `a_one`, `a_two`; assuming that `A` implements
`__add__`, which over two names of type `A` returns an `A`; and, `A` provides
the attribute `some_attr`; the following is legal Python code
`(a_one + a_two).some_attr`. Another example of code whose name is unresolvable
is `(3).to_bytes(length=1, byteorder='big')`.
Rattr will handle the above cases by returning a produced local name -- the
result of prepending the AST node type with an '@'. The former example
will become `@BinOp.some_attr`, and the latter `@Int.to_bytes`.
## Example Results
```
{
...
"my_function": {
"gets": [
"variable_a",
"variable_b",
"object_a.some_attr",
],
"sets": [
"object_a.set_me",
],
"dels": [],
"calls": [
"min()",
"max()"
]
},
}
```
## Support for Python 3.8
Between Python 3.7 and Python 3.8 there were several significant changes that
effect Rattr and how it works, namely:
1. the introduction of the walrus operator;
2. the addition of `posonlyargs` to `ast.arguments`;
3. complete rework of the representation of constants in `ast`.
As it stands Rattr will run on-and-under Python 3.8, however, with varying
support for the above. Specifically: 1. is not supported, and usage will cause
an error; 2. is not supported, and usage results in undefined behaviour; and 3.
is fully supported.
An additional issue with Python 3.7/3.8 cross-compatibility is the introduction
of `typing.get_origin` and `typing.get_args`, removing the need to rely on the
undefined behaviour of `Union().__args__`. Though, as the latter works in both,
this does not affect the execution of Rattr -- it just results in some
complaints by `mypy` which could be avoided it only Python 3.8 were supported.
Links regarding the above:
[1] https://stackoverflow.com/questions/45957615/check-a-variable-against-union-type-at-runtime-in-python-3-6
-- answers 1 and 2 specifically touch on the `typing.get_args` /
`Union().__args__` issue.
[2] https://greentreesnakes.readthedocs.io/en/latest/nodes.html#literals
-- literals are very different.
[3] https://greentreesnakes.readthedocs.io/en/latest/nodes.html#NamedExpr
-- walrus operator.
[4] https://greentreesnakes.readthedocs.io/en/latest/nodes.html#arguments
-- `posonlyargs`.
--------------------------------------------------------------------------------
# Known Issues
For now these will throw a fatal error -- in the future Rattr should be more
"feature complete" and should handle these cases properly.
## Globals
```python
>>> y = 8
>>> def fn(a):
... global y
... y = a
...
>>> fn(3)
>>> y
3
>>>
```
## Redefinitions
```python
def fn(m):
print(m.attr_one)
m = MyCoolClass()
print(m.attr_two)
```
Rattr will produce `{ "sets": {"m.attr_one", "m.attr_two"} }`\
But should produce `{ "sets": {"m.attr_one", "@local:m.atter_two"} }`?
Raw data
{
"_id": null,
"home_page": "https://github.com/SuadeLabs/rattr",
"name": "rattr",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "automation linting type-checking attributes rats",
"author": "Suade Labs",
"author_email": "",
"download_url": "https://files.pythonhosted.org/packages/c5/bb/4894c9eff498bfbeca7fe042f179033225dcccc196a048eb9ee3de07f2fd/rattr-0.1.8.tar.gz",
"platform": null,
"description": "# Rattr rats on your attrs.\n\nRattr (pronounced 'ratter') is a tool to determine attribute usage in python functions. It can parse python files, follow imports and then report to you about the attributes accessed by function calls in that file.\n\n# Status\n\nCurrently this project is under active development and likely to change significantly in the future. However we hope it might be useful and interesting to the wider python community.\n\n# But why?\n\nWe developed rattr to help with some analytics work in python where type checkers like mypy and pyre are cumbersome.\nIn analytics work, we often have functions that look like this:\n```python\ndef compute_cost_effectiveness(person):\n return person.sales / person.salary\n```\n\nbecause we're pythonistas, the exact type of `person` is unimportant to us in this example - what's important is that it has a sales and salary attribute and that those are numbers. Annotating this function with that information for mypy would be cumbersome - and with thousands of functions it would be hard to do.\n\nRattr is a tool that solves the first part of this - it can detect that `compute_cost_effectiveness` needs to access \"sales\" and \"salary\" attributes and so it could tell us that the following would fail:\n\n```python\ndef create_report():\n people = some_database.query(Person.name, Person.sales).all()\n return {person.name: compute_cost_effectiveness(person) for person in people}\n```\n\nIt can also effectively compute the provenance of attributes. Suppose that you have a wide array of functions for computing information about financial products - like\n```python\ndef compute_some_complex_risk_metric_for(security, other_data):\n # proprietary and complicated logic here\n security.riskiness = bla\n return security\n```\n\nand you have other functions that consume that information:\n```python\ndef should_i_buy(security):\n if security.riskiness > 5:\n return False\n # More logic here ...\n```\n\nrattr can help you determine which functions are required for a calculation. Effectively allowing you to build powerful directed graph structures for your function libraries.\n\n# Configuration\n\nRattr is configurable both via pyproject.toml and the command line.\n\n## Command Line Args:\n\n```\n -h, --help show this help message and exit\n\n -v, --version show program's version number and exit\n\n -f {0,1,2,3}, --follow-imports {0,1,2,3}\n follow imports level meanings:\n 0 - do not follow imports\n 1 - follow imports to local modules (default)\n 2 - follow imports to local and pip installed modules\n 3 - follow imports to local, pip installed, and stdlib modules\n NB: following stdlib imports when using CPython will cause issues\n\n -F PATTERN, --exclude-import PATTERN\n do not follow imports to modules matching the given pattern, regardless of the\n level of -f\n\n -x PATTERN, --exclude PATTERN\n exclude functions and classes matching the given regular expression from being\n analysed\n\n -w {none,file,all,ALL}, --show-warnings {none,file,all,ALL}\n show warnings level meaning:\n none - do not show warnings\n file - show warnings for <file>\n all - show warnings for all files (default)\n All - show warnings for all files, including low-priority\n NB: errors and fatal errors are always shown\n\n -p {none,short,full}, --show-path {none,short,full}\n show path level meaning:\n none - do not show the file path in errors/warnings\n short - show an abbreviated path (default)\n full - show the full path\n E.g.: \"/home/user/very/deep/dir/path/file\" becomes \"~/.../dir/path/file\"\n\n --strict run rattr in strict mode, i.e. fail on any error\n --permissive THRESHOLD\n run rattr in permissive mode, with the given badness threshold (when threshold\n is zero or omitted, it is taken as infinite) (default: --permissive 0 when\n group omitted)\n \n typical badness values:\n +0 - info\n +1 - warning\n +5 - error\n +\u221e - fatal\n \n NB: badness is only contributed to by the target <file> and by the\n simplification stage (e.g. resolving function calls, etc).\n\n -i, --show-ir show the IR for the file and imports\n -r, --show-results show the results of analysis\n -s, --show-stats show stats Rattr statisitics\n -S, --silent show only errors and warnings\n\n --cache CACHE the file to cache the results to, if successful\n\n <filter-string> filter the output to functions matching the given regular expression\n\n <file> the Python source file to analyse\n\n```\n## pyproject.toml\n\nExample toml config:\n\n```toml\n[tool.rattr]\nfollow-imports = 0 # options are: (0, 1, 2, 3)\nstrict = true\n# permissive = 1 # (can be any positive int & mutex with 'strict = true')\nsilent = true\n# show-ir = true # (mutex with 'silent = true')\n# show-results = true # (mutex with 'silent = true')\n# show-stats = true # (mutex with 'silent = true')\nshow-path = 'none' # options are: ('none', 'short', 'full')\nshow-warnings = 'none' # options are: ('none', 'file', 'all', 'ALL')\nexclude-import = [ \n 'a\\.b\\.c.*',\n 'd\\..*',\n '^e$'\n]\nexclude = [\n 'a_.*',\n 'b_.*',\n '_c.*',\n]\ncache = 'cache.json'\n```\n\nWithout setting any command line or toml arguments specifically, the default configuration for rattr is the following:\n\n```toml\n[tool.rattr]\nfollow-imports = 1\npermissive = 0\nshow-ir = false\nshow-results = true\nshow-stats = false\nshow-path = 'short'\nshow-warnings = 'all'\nexclude-import = []\nexclude = []\ncache = ''\n```\n\n\n# Developer Notes\n\n## Use of Undocumented Behaviour\n\nIn `rattr/analyser/types.py` several `Union` types are defined for\nconvenience. In Python 3.8 to check if the variable `a` is an instance of any\nof the types within the `Union` the `typing` module provides `get_args` i.e.\none would use `isinstance(a, get_args(UnionTypeName))`. However, this function\nis not provided in Python 3.7 and so the undocumented attribute `__args__` of\nthe `UnionTypeName` must be used i.e. `isinstance(a, UnionTypeName.__args__)`.\nAs this is undocumented it should be changed when we upgrade to Python 3.8+\n(and `$EDITOR` will not syntax highlight or tab-complete it).\n\n\n## Annotations\n\nRattr provides the ability to annotate functions in the target file such that\nthey may be ignored completely, ignored with their results determined manually,\netc. Additionally, each assertor may provide it's own annotations to ignore\nand/or define behaviour.\n\nGeneral Rattr annotations are located in `rattr/analyser/annotations.py` and\nassertor specific annotations are to be added by the assertion developer --\nhowever they should be placed in the file containing the `Assertor` class.\n\n### Annotation Format\n\nAnnotations should take the form `rattr_<annotation_name>` to avoid namespace\nconflicts in importing code.\n\n### Detecting and Parsing Annotations\n\nThe `rattr/analyser/utils.py` file provides the following annotation utility\nfunctions:\n\n* `has_annotation(name: str, fn: ast.FunctionDef) -> bool`\n* `get_annotation(name: str, fn: ast.FunctionDef) -> Optional[ast.AST]`\n* `parse_annotation(name: str, fn: ast.FunctionDef) -> Dict[str, Any]`\n* `parse_rattr_results_from_annotation(fn: ast.FunctionDef) -> Dict[str, Literal[...]]:`\n* `safe_eval(expr: ast.expr, culprit: Optional[ast.AST]) -> Union[Literal, Iterable[Iterable[...[Literal]]]]`\n* `is_name(name: Any) -> bool`\n* `is_set_of_names(set_of_names: Any) -> bool`\n* `is_args(args: Any) -> bool`\n\n\n### Provided Annotations\n\nAnnotation Name | Location\n:-------------------------------------------|:--------------------------------\n`rattr_ignore` | `rattr/analyser/annotations.py`\n`rattr_results(<results>)` | `rattr/analyser/annotations.py`\n\n### Results Annotation Grammar\n\n```python\n\n@rattr_results(\n sets={\"a\", \"b.attr\"},\n calls=[\n (\"callee_function\", ([\"arg\", \"another\"], {\"kwarg\": \"some_var\"}))\n ]\n)\ndef decorated_function(...):\n # ...\n\n```\n\nAny argument to the decorator can be omitted and a default value will be used.\n\n\n## Known Issues\n\nNested functions are not currently analysed properly, functions containing\nnested functions must be annotated manually.\n\nComprehensions are not fully analysed, should be solvable by the same approach\nas nested functions -- \"un-nest\" them.\n\n\n--------------------------------------------------------------------------------\n\n\n# Usage Notes\n\nSee `python rattr -h`.\n\n\n## Errors and Warnings\n\nRattr can give five types of error/warnings: raised Python errors, output\nbeginning with \"info:\" or \"warning:\", output beginning with \"error:\", and\noutput beginning with \"fatal:\". The former can be seen as a developer caused\nerror, and the latter four are user errors.\n\n### User Error: \"info\" and \"warning\"\n\nWarns the user of potential issues or bad practise that should not affect the\nresults of analysis. Low-priority (often class based) warnings begin with\n\"info\".\n\n### User Error: \"error\"\n\nWarns the user of potential issues or bad practise that will likely affect the\nresults of analysis (though there are times when the results will still be\ncorrect).\n\n### User Error: \"fatal\"\n\nWarns the user of potential issues or bad practise so severe that the results\ncan not be produced for the given file.\n\n\n## Results Structure\n\nA dictionary from functions to results, which is in turn a dictionary of the\nvariables, attributes, etc (collectively nameables) that are get, set, called,\nor deleted.\n\n\n## Nameables Format\n\nPythonic Name | Python Example | Rattr Result Format\n:---------------|:------------------------------|:---------------------\nName | `name` | `name`\nStarred | `*name` | `*name`\nAttribute | `name.attr` | `name.attr`\nCall | `name(a, b, ...)` | `name()`\nSubscript | `name[0]` or `name['key']` | `name[]`\n\nThe above can be nested in Rattr as in Python, for example the Python snippet\n`name.method(arg_one, arg_two, ...).result_attr['some key']` will become\n`name.method().result_attr[]`.\n\nHowever, some expression do not have resolvable names. For example, given the\nclass `A` and instances `a_one`, `a_two`; assuming that `A` implements\n`__add__`, which over two names of type `A` returns an `A`; and, `A` provides\nthe attribute `some_attr`; the following is legal Python code\n`(a_one + a_two).some_attr`. Another example of code whose name is unresolvable\nis `(3).to_bytes(length=1, byteorder='big')`.\n\nRattr will handle the above cases by returning a produced local name -- the\nresult of prepending the AST node type with an '@'. The former example\nwill become `@BinOp.some_attr`, and the latter `@Int.to_bytes`.\n\n\n## Example Results\n\n```\n{\n ...\n\n \"my_function\": {\n \"gets\": [\n \"variable_a\",\n \"variable_b\",\n \"object_a.some_attr\",\n ],\n \"sets\": [\n \"object_a.set_me\",\n ],\n \"dels\": [],\n \"calls\": [\n \"min()\",\n \"max()\"\n ]\n },\n}\n```\n\n## Support for Python 3.8\n\nBetween Python 3.7 and Python 3.8 there were several significant changes that\neffect Rattr and how it works, namely:\n\n1. the introduction of the walrus operator;\n2. the addition of `posonlyargs` to `ast.arguments`;\n3. complete rework of the representation of constants in `ast`.\n\nAs it stands Rattr will run on-and-under Python 3.8, however, with varying\nsupport for the above. Specifically: 1. is not supported, and usage will cause\nan error; 2. is not supported, and usage results in undefined behaviour; and 3.\nis fully supported.\n\nAn additional issue with Python 3.7/3.8 cross-compatibility is the introduction\nof `typing.get_origin` and `typing.get_args`, removing the need to rely on the\nundefined behaviour of `Union().__args__`. Though, as the latter works in both,\nthis does not affect the execution of Rattr -- it just results in some\ncomplaints by `mypy` which could be avoided it only Python 3.8 were supported.\n\nLinks regarding the above:\n\n[1] https://stackoverflow.com/questions/45957615/check-a-variable-against-union-type-at-runtime-in-python-3-6\n-- answers 1 and 2 specifically touch on the `typing.get_args` /\n`Union().__args__` issue.\n\n[2] https://greentreesnakes.readthedocs.io/en/latest/nodes.html#literals\n-- literals are very different.\n\n[3] https://greentreesnakes.readthedocs.io/en/latest/nodes.html#NamedExpr\n-- walrus operator.\n\n[4] https://greentreesnakes.readthedocs.io/en/latest/nodes.html#arguments\n-- `posonlyargs`.\n\n\n--------------------------------------------------------------------------------\n\n\n# Known Issues\n\nFor now these will throw a fatal error -- in the future Rattr should be more\n\"feature complete\" and should handle these cases properly.\n\n\n## Globals\n\n```python\n>>> y = 8\n>>> def fn(a):\n... global y\n... y = a\n...\n>>> fn(3)\n>>> y\n3\n>>>\n```\n\n\n## Redefinitions\n\n```python\n\ndef fn(m):\n print(m.attr_one)\n\n m = MyCoolClass()\n\n print(m.attr_two)\n\n```\n\nRattr will produce `{ \"sets\": {\"m.attr_one\", \"m.attr_two\"} }`\\\nBut should produce `{ \"sets\": {\"m.attr_one\", \"@local:m.atter_two\"} }`?\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Rattr rats on your attrs.",
"version": "0.1.8",
"project_urls": {
"Homepage": "https://github.com/SuadeLabs/rattr"
},
"split_keywords": [
"automation",
"linting",
"type-checking",
"attributes",
"rats"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "05e23ab8d2064799124ca4f9a847eb348e26399d800bfa1d01738ba2db026ccd",
"md5": "b06f770195cbadaf142b7f3574583019",
"sha256": "2046f6615508664c25f8c982aba8d670de45c1ceea6136cce5161e1ed8613ddf"
},
"downloads": -1,
"filename": "rattr-0.1.8-py3-none-any.whl",
"has_sig": false,
"md5_digest": "b06f770195cbadaf142b7f3574583019",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 101854,
"upload_time": "2023-07-24T13:36:59",
"upload_time_iso_8601": "2023-07-24T13:36:59.960986Z",
"url": "https://files.pythonhosted.org/packages/05/e2/3ab8d2064799124ca4f9a847eb348e26399d800bfa1d01738ba2db026ccd/rattr-0.1.8-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "c5bb4894c9eff498bfbeca7fe042f179033225dcccc196a048eb9ee3de07f2fd",
"md5": "af0de5fd94fdfc86272e1131d55c5b3b",
"sha256": "23947603441fd5468c3f5f2a8c748e246d182415c4f140f22b4de2424fcd44ce"
},
"downloads": -1,
"filename": "rattr-0.1.8.tar.gz",
"has_sig": false,
"md5_digest": "af0de5fd94fdfc86272e1131d55c5b3b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 92646,
"upload_time": "2023-07-24T13:37:01",
"upload_time_iso_8601": "2023-07-24T13:37:01.168306Z",
"url": "https://files.pythonhosted.org/packages/c5/bb/4894c9eff498bfbeca7fe042f179033225dcccc196a048eb9ee3de07f2fd/rattr-0.1.8.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-07-24 13:37:01",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "SuadeLabs",
"github_project": "rattr",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "rattr"
}
JSON
