taskcheck 0.3.3.post2__tar.gz → 0.4.0__tar.gz

{taskcheck-0.3.3.post2/taskcheck.egg-info → taskcheck-0.4.0}/PKG-INFO

@@ -1,10 +1,9 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: taskcheck
-Version: 0.3.3.post2
+Version: 0.4.0
 Summary: Automatic scheduler for taskwarrior
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
-License-File: LICENSE
 Requires-Dist: appdirs>=1.4.4
 Requires-Dist: icalendar>=6.0.1
 Requires-Dist: random-unicode-emoji>=2.8
@@ -40,7 +39,7 @@ It considers their estimated time to schedule all tasks starting from the most u
 
 #### UDAs
 
-Taskcheck leverages to UDAs, `estimated` and `time_map`. The `estimated` attribute is
+Taskcheck leverages two UDAs, `estimated` and `time_map`. The `estimated` attribute is
 the expected time to complete the task in hours. The `time_map` is a comma-separated list of strings
 that indicates the hours per day in which you will work on a task (e.g. `work`, `weekend`, etc.).
 The exact correspondence between the `time_map` and the hours of the day is defined in the configuration
@@ -74,25 +73,8 @@ how much time you have to work on which task in which day. For
 instance:
 
 - `taskcheck -r today` will show the tasks planned for today
-- `taskcheck -r 1w` will show the tasks planned for the next week,
+- `taskcheck -r 1w` will show the tasks planned for the next week
 
-## Algorithm
-
-The algorithm simulates what happens if you work on a task for a certain time on a given day.
-
-For each day X starting from today, it sorts the tasks by decreasing urgency. 
-It start from the most urgent tasks that can be allocated on day X depending on the task's
-`time_map` and on your calendars. It allocates a few number of hours to the task,
-then recomputes the urgencies exactly as Taskwarrior would do
-if it was running on day X. Having recomputed the urgencies, it restarts.
-
-If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
-task will get scheduled in its place.
-
-For `today`, taskcheck will consider as allocated the hours already past.
-
-The maximum time that is allocated at each attempt is by default 2 hours
-(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
 
 ## Configuration
 
@@ -139,6 +121,25 @@ include_unplanned = true # include unplanned tasks in the report in an ad-hoc se
 additional_attributes_unplanned = ["due", "urgency"] # additional attributes to show in the report for unplanned tasks
 ```
 
+## Algorithm
+
+The algorithm simulates what happens if you work on a task for a certain time on a given day.
+
+For each day X starting from today, it sorts the tasks by decreasing urgency. 
+It start from the most urgent tasks that can be allocated on day X depending on the task's
+`time_map` and on your calendars. It allocates a few number of hours to the task,
+then recomputes the urgencies exactly as Taskwarrior would do
+if it was running on day X. Having recomputed the urgencies, it restarts.
+
+If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
+task will get scheduled in its place.
+
+For `today`, taskcheck will skip the hours in the past -- i.e. if you're running at 12 pm, it will
+skip all the available slots until 12 pm.
+
+The maximum time that is allocated at each attempt is by default 2 hours
+(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
+
 ## Tips and Tricks
 
 - You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.

{taskcheck-0.3.3.post2 → taskcheck-0.4.0}/README.md

@@ -27,7 +27,7 @@ It considers their estimated time to schedule all tasks starting from the most u
 
 #### UDAs
 
-Taskcheck leverages to UDAs, `estimated` and `time_map`. The `estimated` attribute is
+Taskcheck leverages two UDAs, `estimated` and `time_map`. The `estimated` attribute is
 the expected time to complete the task in hours. The `time_map` is a comma-separated list of strings
 that indicates the hours per day in which you will work on a task (e.g. `work`, `weekend`, etc.).
 The exact correspondence between the `time_map` and the hours of the day is defined in the configuration
@@ -61,25 +61,8 @@ how much time you have to work on which task in which day. For
 instance:
 
 - `taskcheck -r today` will show the tasks planned for today
-- `taskcheck -r 1w` will show the tasks planned for the next week,
+- `taskcheck -r 1w` will show the tasks planned for the next week
 
-## Algorithm
-
-The algorithm simulates what happens if you work on a task for a certain time on a given day.
-
-For each day X starting from today, it sorts the tasks by decreasing urgency. 
-It start from the most urgent tasks that can be allocated on day X depending on the task's
-`time_map` and on your calendars. It allocates a few number of hours to the task,
-then recomputes the urgencies exactly as Taskwarrior would do
-if it was running on day X. Having recomputed the urgencies, it restarts.
-
-If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
-task will get scheduled in its place.
-
-For `today`, taskcheck will consider as allocated the hours already past.
-
-The maximum time that is allocated at each attempt is by default 2 hours
-(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
 
 ## Configuration
 
@@ -126,6 +109,25 @@ include_unplanned = true # include unplanned tasks in the report in an ad-hoc se
 additional_attributes_unplanned = ["due", "urgency"] # additional attributes to show in the report for unplanned tasks
 ```
 
+## Algorithm
+
+The algorithm simulates what happens if you work on a task for a certain time on a given day.
+
+For each day X starting from today, it sorts the tasks by decreasing urgency. 
+It start from the most urgent tasks that can be allocated on day X depending on the task's
+`time_map` and on your calendars. It allocates a few number of hours to the task,
+then recomputes the urgencies exactly as Taskwarrior would do
+if it was running on day X. Having recomputed the urgencies, it restarts.
+
+If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
+task will get scheduled in its place.
+
+For `today`, taskcheck will skip the hours in the past -- i.e. if you're running at 12 pm, it will
+skip all the available slots until 12 pm.
+
+The maximum time that is allocated at each attempt is by default 2 hours
+(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
+
 ## Tips and Tricks
 
 - You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.

{taskcheck-0.3.3.post2 → taskcheck-0.4.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "taskcheck"
-version = "0.3.3-2"
+version = "0.4.0"
 description = "Automatic scheduler for taskwarrior"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -14,3 +14,6 @@ dependencies = [
 
 [project.scripts]
 taskcheck = "taskcheck.__main__:main"
+
+[tool.setuptools]
+license-files = []

{taskcheck-0.3.3.post2 → taskcheck-0.4.0}/taskcheck/__main__.py

@@ -20,6 +20,12 @@ arg_parser.add_argument(
     action="store",
     help="generate a report of the tasks based on the scheduling; can be any Taskwarrior datetime specification (e.g. today, tomorrow, eom, som, 1st, 2nd, etc.). It is considered as `by`, meaning that the report will be generated for all the days until the specified date and including it.",
 )
+arg_parser.add_argument(
+    "-s",
+    "--schedule",
+    action="store_true",
+    help="perform the scheduling algorithm, giving a schedule and a scheduling UDA and alerting for not completable tasks",
+)
 
 args = arg_parser.parse_args()
 
@@ -33,21 +39,27 @@ def load_config():
 
 def main():
     # Load data and check tasks
+    print_help = True
     if args.install:
         from taskcheck.install import install
 
         install()
         return
 
+    if args.schedule:
+        config = load_config()
+        check_tasks_parallel(config, verbose=args.verbose)
+        print_help = False
+
     if args.report:
         from taskcheck.report import generate_report
 
         config = load_config()
         generate_report(config, args.report, args.verbose)
-        return
+        print_help = False
 
-    config = load_config()
-    check_tasks_parallel(config, verbose=args.verbose)
+    if print_help:
+        arg_parser.print_help()
 
 
 if __name__ == "__main__":

{taskcheck-0.3.3.post2 → taskcheck-0.4.0}/taskcheck/install.py

@@ -68,19 +68,19 @@ def install():
         ("urgency.uda.estimated.PT21H.coefficient", "10.38"),
         ("urgency.uda.estimated.PT22H.coefficient", "10.53"),
         ("urgency.uda.estimated.PT23H.coefficient", "10.67"),
-        ("urgency.uda.estimated.PT24H.coefficient", "10.80"),
-        ("urgency.uda.estimated.PT25H.coefficient", "10.93"),
-        ("urgency.uda.estimated.PT26H.coefficient", "11.05"),
-        ("urgency.uda.estimated.PT27H.coefficient", "11.16"),
-        ("urgency.uda.estimated.PT28H.coefficient", "11.27"),
-        ("urgency.uda.estimated.PT29H.coefficient", "11.37"),
-        ("urgency.uda.estimated.PT30H.coefficient", "11.47"),
-        ("urgency.uda.estimated.PT31H.coefficient", "11.56"),
-        ("urgency.uda.estimated.PT32H.coefficient", "11.65"),
-        ("urgency.uda.estimated.PT33H.coefficient", "11.73"),
-        ("urgency.uda.estimated.PT34H.coefficient", "11.81"),
-        ("urgency.uda.estimated.PT35H.coefficient", "11.89"),
-        ("urgency.uda.estimated.PT36H.coefficient", "11.96"),
+        ("urgency.uda.estimated.P1D.coefficient", "10.80"),
+        ("urgency.uda.estimated.P1DT1H.coefficient", "10.93"),
+        ("urgency.uda.estimated.P1DT2H.coefficient", "11.05"),
+        ("urgency.uda.estimated.P1DT3H.coefficient", "11.16"),
+        ("urgency.uda.estimated.P1DT4H.coefficient", "11.27"),
+        ("urgency.uda.estimated.P1DT5H.coefficient", "11.37"),
+        ("urgency.uda.estimated.P1DT6H.coefficient", "11.47"),
+        ("urgency.uda.estimated.P1DT7H.coefficient", "11.56"),
+        ("urgency.uda.estimated.P1DT8H.coefficient", "11.65"),
+        ("urgency.uda.estimated.P1DT9H.coefficient", "11.73"),
+        ("urgency.uda.estimated.P1DT10H.coefficient", "11.81"),
+        ("urgency.uda.estimated.P1DT11H.coefficient", "11.89"),
+        ("urgency.uda.estimated.P1DT12H.coefficient", "11.96"),
         (
             "report.ready.columns",
             "id,start.age,entry.age,depends.indicator,priority,project,tags,recur.indicator,scheduled.relative,due.relative,until.remaining,description,urgency",

{taskcheck-0.3.3.post2 → taskcheck-0.4.0}/taskcheck/report.py

@@ -315,7 +315,7 @@ def build_tasks_table(config, tasks):
     for task in tasks:
         task_id = f"[bold green]#{task['id']}[/bold green]"
         project = task.get("project", "")
-        description = Text(task["description"], style="white")
+        description = Text(task["description"], style="italic")
         hours = f"[yellow]{task['scheduling_hours']}[/yellow]"
         emoji = get_task_emoji(config, task)
 
@@ -382,7 +382,7 @@ def build_unplanned_tasks_table(config, tasks):
     for task in tasks:
         task_id = f"[bold green]#{task['id']}[/bold green]"
         project = task.get("project", "")
-        description = Text(task["description"], style="white")
+        description = Text(task["description"], style="italic")
         emoji = get_task_emoji(config, task)
 
         table.add_row(

{taskcheck-0.3.3.post2 → taskcheck-0.4.0/taskcheck.egg-info}/PKG-INFO

@@ -1,10 +1,9 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: taskcheck
-Version: 0.3.3.post2
+Version: 0.4.0
 Summary: Automatic scheduler for taskwarrior
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
-License-File: LICENSE
 Requires-Dist: appdirs>=1.4.4
 Requires-Dist: icalendar>=6.0.1
 Requires-Dist: random-unicode-emoji>=2.8
@@ -40,7 +39,7 @@ It considers their estimated time to schedule all tasks starting from the most u
 
 #### UDAs
 
-Taskcheck leverages to UDAs, `estimated` and `time_map`. The `estimated` attribute is
+Taskcheck leverages two UDAs, `estimated` and `time_map`. The `estimated` attribute is
 the expected time to complete the task in hours. The `time_map` is a comma-separated list of strings
 that indicates the hours per day in which you will work on a task (e.g. `work`, `weekend`, etc.).
 The exact correspondence between the `time_map` and the hours of the day is defined in the configuration
@@ -74,25 +73,8 @@ how much time you have to work on which task in which day. For
 instance:
 
 - `taskcheck -r today` will show the tasks planned for today
-- `taskcheck -r 1w` will show the tasks planned for the next week,
+- `taskcheck -r 1w` will show the tasks planned for the next week
 
-## Algorithm
-
-The algorithm simulates what happens if you work on a task for a certain time on a given day.
-
-For each day X starting from today, it sorts the tasks by decreasing urgency. 
-It start from the most urgent tasks that can be allocated on day X depending on the task's
-`time_map` and on your calendars. It allocates a few number of hours to the task,
-then recomputes the urgencies exactly as Taskwarrior would do
-if it was running on day X. Having recomputed the urgencies, it restarts.
-
-If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
-task will get scheduled in its place.
-
-For `today`, taskcheck will consider as allocated the hours already past.
-
-The maximum time that is allocated at each attempt is by default 2 hours
-(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
 
 ## Configuration
 
@@ -139,6 +121,25 @@ include_unplanned = true # include unplanned tasks in the report in an ad-hoc se
 additional_attributes_unplanned = ["due", "urgency"] # additional attributes to show in the report for unplanned tasks
 ```
 
+## Algorithm
+
+The algorithm simulates what happens if you work on a task for a certain time on a given day.
+
+For each day X starting from today, it sorts the tasks by decreasing urgency. 
+It start from the most urgent tasks that can be allocated on day X depending on the task's
+`time_map` and on your calendars. It allocates a few number of hours to the task,
+then recomputes the urgencies exactly as Taskwarrior would do
+if it was running on day X. Having recomputed the urgencies, it restarts.
+
+If after 2 hours a long task has decreased its urgency, it will be noticed and the newer most urgent
+task will get scheduled in its place.
+
+For `today`, taskcheck will skip the hours in the past -- i.e. if you're running at 12 pm, it will
+skip all the available slots until 12 pm.
+
+The maximum time that is allocated at each attempt is by default 2 hours
+(or less if the task is shorter), but you can change it by tuning the Taskwarrior UDA `min_block`.
+
 ## Tips and Tricks
 
 - You can exclude a task from being scheduled by removing the `time_map` or `estimated` attributes.