<commit_before># crontab_parser

A crontab parser inspired by [https://crontab.guru](crontab.guru).

![https://travis-ci.org/zeckalpha/crontab_parser.svg?branch=master](Status at Travis CI)


## Building

    docker build . -t crontab-parser


## Usage

    echo '1 2 3 4 5 command to run' | docker run -i crontab-parser

## TODO

At present this does not do validation or boundary checking, nor does it support
syntax such as:

- 5,10,15
- 5-10
- \*/5
- JAN-DEC / MON-SUN
- @yearly / @annually / @monthly / @weekly / @daily / @hourly / @reboot
- H
- a second field
- L
- W
- ?
- 5#3
- %
- Comments
<commit_msg>I always switch these in my markdown...<commit_after># crontab_parser

A crontab parser inspired by [https://crontab.guru](crontab.guru).

![Status at Travis CI](https://travis-ci.org/zeckalpha/crontab_parser.svg?branch=master)


## Building

    docker build . -t crontab-parser


## Usage

    echo '1 2 3 4 5 command to run' | docker run -i crontab-parser

## TODO

At present this does not do validation or boundary checking, nor does it support
syntax such as:

- 5,10,15
- 5-10
- \*/5
- JAN-DEC / MON-SUN
- @yearly / @annually / @monthly / @weekly / @daily / @hourly / @reboot
- H
- a second field
- L
- W
- ?
- 5#3
- %
- Comments

{'fraction_non_alphanumeric': 0.13541666666666666, 'fraction_numerical': 0.02564102564102564, 'mean_word_length': 2.8549382716049383, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1106147', 'n_tokens_mistral': 507, 'n_tokens_neox': 466, 'n_words': 144}