icalcli 1.0.5__tar.gz → 1.1__tar.gz

{icalcli-1.0.5 → icalcli-1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: icalcli
-Version: 1.0.5
+Version: 1.1
 Summary: Icalendar Calendar Command Line Interface
 Home-page: https://github.com/jrvarma/icalcli
 Maintainer: Jayanth R. Varma
@@ -12,8 +12,13 @@ Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.6
 Description-Content-Type: text/markdown
-Provides-Extra: parsedatetime
 License-File: LICENSE
+Requires-Dist: python-dateutil
+Requires-Dist: parsedatetime
+Requires-Dist: icalendar
+Requires-Dist: recurring_ical_events
+Provides-Extra: parsedatetime
+Requires-Dist: parsedatetime; extra == "parsedatetime"
 
 # icalcli
 
@@ -23,7 +28,7 @@ License-File: LICENSE
 
 Unlike [gcalcli](https://github.com/insanum/gcalcli) which is tied to Google Calendar, `icalcli` is agnostic to (abstracts away from) the actual backend calendar service. It relies on a backend interface which interacts with the backend calendar to perform all the CRUD (Create, Retrieve, Update and Delete) operations on the actual calendar. The package includes two backends:
 
-* The `etesync_backend` subpackage provides a backend interface to the [EteSync](https://www.etesync.com/) calendar. In fact, `icalcli` was created primarily to provide a command line interface to my self hosted `EteSync` calendar.
+* The `etesync_backend` subpackage provides a backend interface to the [EteSync](https://www.etesync.com/) calendar (versions 1.0 and 2.0). In fact, `icalcli` was created primarily to provide a command line interface to my self hosted `EteSync` calendar.
 
 * The `file_backend` subpackage provides a backend interface to a calendar contained in a local `ics` file. This is useful as a viewer/editor of `ics` files. It is also useful to try out `icalci` without having any other backend configured.
 
@@ -50,6 +55,12 @@ The two included backends would also be useful to those who wish to write their
 pip install icalcli
 ```
 
+or via `pipx`:
+
+```sh
+pipx install icalcli
+```
+
 ### Install from source
 
 ```sh
@@ -57,6 +68,13 @@ git clone https://github.com/jrvarma/icalcli.git
 cd icalcli
 python setup.py install
 ```
+
+or via `pipx`:
+
+```sh
+pipx install . --editable
+```
+
 ## Usage
 
 ### Command line arguments
@@ -97,7 +115,7 @@ backend_interface = ICSInterface(["/path/to/ics-file-1", "/path/to/ics-file-2"])
 
 ```
 
-#### Example configuration for etesync_backend
+#### Example configuration for etesync_backend (etesync 1.0)
 
 This configuration assumes that all the credentials are stored in a plain text (`json`) file. In practice, you would use a more secure storage (perhaps, the `Gnome keyring`) or just read it from the terminal.
 
@@ -116,6 +134,34 @@ backend_interface = EtesyncInterface(
 ```
 See the [Example code](https://github.com/jrvarma/icalcli/issues/1#issuecomment-979851222) for getting the  `uid` and `authToken` for the `etesync` calendar.
 
+#### Example configuration for etebase_backend (etesync 2.0)
+
+This configuration assumes that all the credentials are stored in a plain text (`json`) file. In practice, you would use a more secure storage (perhaps, the `Gnome keyring`) or just read it from the terminal.
+
+```
+from icalcli import EtebaseInterface
+import json
+
+conf_file = '/path/to/json-file'
+with open(conf_file, 'r') as fp:
+    c = json.load(fp)
+
+backend_interface = EtebaseInterface(c['user'], c['server_url'], c['password'],
+                                     c['calendar_uid'], silent=False)
+```
+
+The `calendar_uid` can be obtained using the following code. This code assumes that the `dict c` has been populated with the credentials from the `json` file as above.
+
+```
+from etebase import Client, Account, FetchOptions
+
+client = Client(c['user'], c['server_url'])
+etebase = Account.login(client, c['user'], c['password'])
+col_mgr = etebase.get_collection_manager()
+print({col.uid: col.meta
+      for col in col_mgr.list("etebase.vevent").data})
+```
+
 ## Recurring events and default search period
 
 `icalcli` understands the `RRULE`, `RDATE`, `EXRULE`, `EXDATE` elements of the `icalendar` specification. These elements can be added while creating or editing events using `--rrule`, `--rdate`, `--exrule` and `--exdate` options.

icalcli-1.0.5/icalcli.egg-info/PKG-INFO → icalcli-1.1/README.md

@@ -1,20 +1,3 @@
-Metadata-Version: 2.1
-Name: icalcli
-Version: 1.0.5
-Summary: Icalendar Calendar Command Line Interface
-Home-page: https://github.com/jrvarma/icalcli
-Maintainer: Jayanth R. Varma
-Maintainer-email: jrvarma@gmail.com
-Classifier: Development Status :: 3 - Alpha
-Classifier: Environment :: Console
-Classifier: Intended Audience :: End Users/Desktop
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Requires-Python: >=3.6
-Description-Content-Type: text/markdown
-Provides-Extra: parsedatetime
-License-File: LICENSE
-
 # icalcli
 
 ### An iCalendar Command Line Interface
@@ -23,7 +6,7 @@ License-File: LICENSE
 
 Unlike [gcalcli](https://github.com/insanum/gcalcli) which is tied to Google Calendar, `icalcli` is agnostic to (abstracts away from) the actual backend calendar service. It relies on a backend interface which interacts with the backend calendar to perform all the CRUD (Create, Retrieve, Update and Delete) operations on the actual calendar. The package includes two backends:
 
-* The `etesync_backend` subpackage provides a backend interface to the [EteSync](https://www.etesync.com/) calendar. In fact, `icalcli` was created primarily to provide a command line interface to my self hosted `EteSync` calendar.
+* The `etesync_backend` subpackage provides a backend interface to the [EteSync](https://www.etesync.com/) calendar (versions 1.0 and 2.0). In fact, `icalcli` was created primarily to provide a command line interface to my self hosted `EteSync` calendar.
 
 * The `file_backend` subpackage provides a backend interface to a calendar contained in a local `ics` file. This is useful as a viewer/editor of `ics` files. It is also useful to try out `icalci` without having any other backend configured.
 
@@ -50,6 +33,12 @@ The two included backends would also be useful to those who wish to write their
 pip install icalcli
 ```
 
+or via `pipx`:
+
+```sh
+pipx install icalcli
+```
+
 ### Install from source
 
 ```sh
@@ -57,6 +46,13 @@ git clone https://github.com/jrvarma/icalcli.git
 cd icalcli
 python setup.py install
 ```
+
+or via `pipx`:
+
+```sh
+pipx install . --editable
+```
+
 ## Usage
 
 ### Command line arguments
@@ -97,7 +93,7 @@ backend_interface = ICSInterface(["/path/to/ics-file-1", "/path/to/ics-file-2"])
 
 ```
 
-#### Example configuration for etesync_backend
+#### Example configuration for etesync_backend (etesync 1.0)
 
 This configuration assumes that all the credentials are stored in a plain text (`json`) file. In practice, you would use a more secure storage (perhaps, the `Gnome keyring`) or just read it from the terminal.
 
@@ -116,6 +112,34 @@ backend_interface = EtesyncInterface(
 ```
 See the [Example code](https://github.com/jrvarma/icalcli/issues/1#issuecomment-979851222) for getting the  `uid` and `authToken` for the `etesync` calendar.
 
+#### Example configuration for etebase_backend (etesync 2.0)
+
+This configuration assumes that all the credentials are stored in a plain text (`json`) file. In practice, you would use a more secure storage (perhaps, the `Gnome keyring`) or just read it from the terminal.
+
+```
+from icalcli import EtebaseInterface
+import json
+
+conf_file = '/path/to/json-file'
+with open(conf_file, 'r') as fp:
+    c = json.load(fp)
+
+backend_interface = EtebaseInterface(c['user'], c['server_url'], c['password'],
+                                     c['calendar_uid'], silent=False)
+```
+
+The `calendar_uid` can be obtained using the following code. This code assumes that the `dict c` has been populated with the credentials from the `json` file as above.
+
+```
+from etebase import Client, Account, FetchOptions
+
+client = Client(c['user'], c['server_url'])
+etebase = Account.login(client, c['user'], c['password'])
+col_mgr = etebase.get_collection_manager()
+print({col.uid: col.meta
+      for col in col_mgr.list("etebase.vevent").data})
+```
+
 ## Recurring events and default search period
 
 `icalcli` understands the `RRULE`, `RDATE`, `EXRULE`, `EXDATE` elements of the `icalendar` specification. These elements can be added while creating or editing events using `--rrule`, `--rdate`, `--exrule` and `--exdate` options.

{icalcli-1.0.5 → icalcli-1.1}/icalcli/__init__.py

@@ -4,7 +4,9 @@ __author__ = 'Jayanth Varma (modified gcalcli by Eric Davis et al.)'
 from icalcli.icalcli import IcalendarInterface  # noqa F401
 try:
     from icalcli.etesync_backend.etesync_crud import EtesyncCRUD  # noqa F401
-    from icalcli.etesync_backend.etesync_interface import EtesyncInterface  # noqa F401
+    from icalcli.etesync_backend.etesync_interface import EtesyncInterface  # noqa F
+    from icalcli.etesync_backend.etebase_crud import EtebaseCRUD  # noqa F401
+    from icalcli.etesync_backend.etebase_interface import EtebaseInterface  # noqa F401
 except ImportError:
     pass
 

icalcli-1.1/icalcli/etesync_backend/etebase_crud.py

@@ -0,0 +1,137 @@
+#!/usr/bin/env python
+
+# this is part of the etesync 2.0 backend
+# for etesync 1.0 backend see etesync_crud.py
+
+from etebase import Client, Account, FetchOptions
+from time import sleep, time
+
+# The EtesyncCRUD class exposes methods for each of the CRUD operations
+# (Create, Retrieve, Update and Delete) and for sync with the server.
+# It handles only one calendar
+
+# The class is initialized with user details, authToken and
+# EITHER the encryption password OR the cipher key.
+
+# Intended usage is that a calling program (a CLI) obtains user credentials
+# from terminal input or some secure storage (like a key ring)
+# and then creates an instance of EtesyncCRUD as follows:
+
+# crud = EtebaseCRUD(user, server_url, password, calendar_uid)
+
+# The CLI program can then perform CRUD operations by calling
+# crud.create_event, crud.retrieve_event,
+# crud.update_event and crud.delete_event
+
+# The CLI must explicitly call crud.sync when needed. For example:
+# (a) if the server has been updated from another device
+# (b) after any CRUD operation other than Retrieve
+
+# No exception handling is done. That is left to the CLI.
+
+
+class EtebaseCRUD:
+    def __init__(self, user, server_url, password, calendar_uid, silent=True):
+        """Initialize
+
+        Parameters
+        ----------
+        user : etebase username
+        password : etebase password
+        server_url : url of etebase server
+        calendar_uid : uid of calendar
+        """
+        client = Client(user, server_url)
+        etebase = Account.login(client, user, password)
+        col_mgr = etebase.get_collection_manager()
+        collection = col_mgr.fetch(calendar_uid)
+        self.item_mgr = col_mgr.get_item_manager(collection)
+        self.sync(silent)
+
+    def create_event(self, event, uid):
+        """Create event
+
+        Parameters
+        ----------
+        event : iCalendar file as bytes
+        (calendar containing one event to be added)
+        """
+        item = self.item_mgr.create(
+            {
+                "name": uid,
+                "mtime": int(round(time() * 1000))
+            },
+            event
+        )
+        self.item_mgr.batch([item])
+
+    def update_event(self, event, uid):
+        """Edit event
+
+        Parameters
+        ----------
+        event : iCalendar file as bytes
+        (calendar containing one event to be updated)
+        uid : uid of event to be updated
+        """
+        item = self.item_mgr.fetch(uid)
+        item.content = event
+        self.item_mgr.batch([item])
+
+    def retrieve_event(self, uid):
+        r"""Retrieve event by uid
+
+        Parameters
+        ----------
+        uid : uid of event to be retrieved
+
+        Returns
+        -------
+        iCalendar file (as a string)
+        """
+        return self.item_mgr.fetch(uid).content.decode()
+
+    def all_events(self):
+        """Retrieve all events in calendar
+
+        Returns
+        -------
+        List of iCalendar files (as strings)
+        """
+        return [e.content.decode() for e in self.items.data if not e.deleted]
+
+    def delete_event(self, uid):
+        """Delete event and sync calendar
+
+        Parameters
+        ----------
+        uid : uid of event to be deleted
+        """
+        item = self.item_mgr.fetch(uid)
+        item.delete()
+        self.item_mgr.batch([item])
+
+    def sync(self, silent=False):
+        """Initialize
+
+        Parameters
+        ----------
+        silent : boolean whether to report sync attempt and success
+        """
+        silent or print("Syncing with server. Please wait")
+        msg = "etebase fetch attempt {:} failed. Will retry after {:} seconds"
+        delay = 5
+        synced = False
+        for i in range(5):
+            try:
+                self.items = self.item_mgr.list(FetchOptions().limit(10**6))
+                synced = True
+                break
+            except Exception:
+                silent or print(msg.format(i+1, delay))
+                sleep(delay)
+        if synced:
+            silent or print("Syncing completed.")
+            self.all_events()
+        else:
+            print("Syncing with server failed after 5 attempts")

icalcli-1.1/icalcli/etesync_backend/etebase_interface.py

@@ -0,0 +1,94 @@
+#!/usr/bin/env python
+
+# this is part of the etesync 2.0 backend
+# for etesync 1.0 backend see etesync_interface.py
+
+from icalcli.etesync_backend.etebase_crud import EtebaseCRUD
+from icalendar import Calendar
+
+
+# The EtebaseInterface class is basically a wrapper around the
+# EtebaseCRUD class from which it is derived
+# The CRUD operations (Create, Retrieve, Update and Delete)
+# work with icalendar events (VEVENT). While calling EtebaseCRUD methods,
+# both inputs and return values are converted to/from
+# ics calendar bytes/strings
+
+# The class is initialized with user details and credentials.
+
+# Intended usage is that a calling program obtains user credentials
+# from terminal input or some secure storage (like a key ring)
+# and then creates an instance of EtebaseCRUD as follows:
+
+# etes = EtebaseInterface(user, server_url, password, calendar_uid)
+
+# The calling program can then perform CRUD operations by calling
+# etes.create_event, etes.retrieve_event,
+# etes.update_event and etes.delete_event
+
+# The calling program must explicitly call etes.sync when needed. For example:
+# (a) if the server has been updated from another device
+# (b) after any CRUD operation other than Retrieve
+
+# No exception handling is done. That is left to the calling program.
+
+
+class EtebaseInterface (EtebaseCRUD):
+    def __init__(self, user, server_url, password, calendar_uid, silent=True):
+        r"""Initialize EtebaseInterface
+
+        Parameters
+        ----------
+        user : etebase username
+        password : etebase password
+        server_url : url of etebase server
+        calendar_uid : uid of calendar
+        """
+        super(EtebaseInterface, self).__init__(
+            user, server_url, password, calendar_uid, silent)
+        self.all_events()
+
+    def all_events(self):
+        self.events = [Calendar.from_ical(ev).walk('VEVENT')[0]
+                       for ev in EtebaseCRUD.all_events(self)]
+
+    def create_event(self, event, vtimezone=None):
+        r"""Create event
+
+        Parameters
+        ----------
+        event : event to be added (iCalendar object)
+        """
+        ics = self.event_to_ics(event, vtimezone)
+        EtebaseCRUD.create_event(self, ics)
+
+    def update_event(self, event, vtimezone=None):
+        r"""Update event
+
+        Parameters
+        ----------
+        event : event to be added (iCalendar object)
+        """
+        uid = event.decoded('uid').decode()
+        ics = self.event_to_ics(event, vtimezone)
+        EtebaseCRUD.update_event(self, ics, uid)
+
+    def event_to_ics(self, event, vtimezone=None):
+        r"""Make calendar byte array (ics) from event
+
+        Parameters
+        ----------
+        event : event to be added (iCalendar object)
+        """
+        cal = Calendar()
+        cal.add_component(event)
+        if vtimezone:
+            cal.add_component(vtimezone)
+        ics = cal.to_ical()
+        return ics
+
+    def sync(self, vtimezone=None):
+        r"""Sync with server and rebuild vevent list
+        """
+        EtebaseCRUD.sync(self)
+        self.all_events()

{icalcli-1.0.5 → icalcli-1.1}/icalcli/etesync_backend/etesync_crud.py

@@ -1,5 +1,8 @@
 #!/usr/bin/env python
 
+# this is part of the etesync 1.0 backend
+# for etesync 2.0 backend see etebase_crud.py
+
 import etesync as api
 from time import sleep
 

{icalcli-1.0.5 → icalcli-1.1}/icalcli/etesync_backend/etesync_interface.py

@@ -1,3 +1,8 @@
+#!/usr/bin/env python
+
+# this is part of the etesync 1.0 backend
+# for etesync 2.0 backend see etebase_interface.py
+
 from icalcli.etesync_backend.etesync_crud import EtesyncCRUD
 from icalendar import Calendar
 

{icalcli-1.0.5 → icalcli-1.1}/icalcli/file_backend/ics_interface.py

@@ -61,9 +61,9 @@ class ICSInterface:
             return
         if self.backup:
             with NamedTemporaryFile(mode='w',
-                                    suffix=self.filepath.suffix,
-                                    prefix=self.filepath.name,
-                                    dir=self.filepath.parent,
+                                    suffix=self.filepaths[0].suffix,
+                                    prefix=self.filepaths[0].name,
+                                    dir=self.filepaths[0].parent,
                                     delete=False) as fp:
                 fp.write(self.ics)
         cal = Calendar()
@@ -72,6 +72,6 @@ class ICSInterface:
         if vtimezone:
             cal.add_component(vtimezone)
         self.ics = cal.to_ical().decode()
-        with open(self.filepath, 'w') as fp:
+        with open(self.filepaths[0], 'w') as fp:
             fp.write(self.ics)
         self.all_events()

{icalcli-1.0.5 → icalcli-1.1}/icalcli/icalcli.py

@@ -385,13 +385,13 @@ class IcalendarInterface:
                                   decode().strip())
         if self.graphical_outputs.get('uid'):
             summary += " <%s>" % (event.Decoded('uid').decode().strip())
-        # if (
-        #         self.graphical_outputs.get('description')
-        #         and 'description' in event
-        #         and event.Decoded('description').decode().strip()
-        #         and self.outputs.get('description')
-        # ):
-        #     summary += event.Decoded('description'). decode().strip()
+        if (
+                self.graphical_outputs.get('description')
+                and 'description' in event
+                and event.Decoded('description').decode().strip()
+                and self.outputs.get('description')
+        ):
+            summary += event.Decoded('description'). decode().strip()
         return summary
 
     def get_week_events(self, start_dt, end_dt, event_list):
@@ -551,10 +551,11 @@ class IcalendarInterface:
         -------
         int: where to cut the word
         """
-        print_len = 0
+        # print_len = 0
 
         words = _u(string).split()
         for i, word in enumerate(words):
+            print_len = self.printed_len(' '.join(words[:i]))
             word_len = self.printed_len(word)
             if (
                     (cur_print_len + word_len + print_len
@@ -566,7 +567,7 @@ class IcalendarInterface:
                 if cut_idx == 0:
                     return self.word_cut(word)
                 return (print_len, cut_idx)
-            print_len += word_len + i  # +i for the space between words
+            # print_len += word_len + i  # +i for the space between words
         return (print_len, len(' '.join(words[:i])))
 
     def get_cut_index(self, event_string):
@@ -741,7 +742,6 @@ class IcalendarInterface:
                         curr_event.title)
                     padding = ' ' * (self.options['cal_width']
                                      - print_len)
-
                     self.printer.msg(
                             curr_event.title[:cut_idx] + padding,
                             curr_event.color)

icalcli-1.0.5/README.md → icalcli-1.1/icalcli.egg-info/PKG-INFO

@@ -1,3 +1,25 @@
+Metadata-Version: 2.1
+Name: icalcli
+Version: 1.1
+Summary: Icalendar Calendar Command Line Interface
+Home-page: https://github.com/jrvarma/icalcli
+Maintainer: Jayanth R. Varma
+Maintainer-email: jrvarma@gmail.com
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: End Users/Desktop
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.6
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: python-dateutil
+Requires-Dist: parsedatetime
+Requires-Dist: icalendar
+Requires-Dist: recurring_ical_events
+Provides-Extra: parsedatetime
+Requires-Dist: parsedatetime; extra == "parsedatetime"
+
 # icalcli
 
 ### An iCalendar Command Line Interface
@@ -6,7 +28,7 @@
 
 Unlike [gcalcli](https://github.com/insanum/gcalcli) which is tied to Google Calendar, `icalcli` is agnostic to (abstracts away from) the actual backend calendar service. It relies on a backend interface which interacts with the backend calendar to perform all the CRUD (Create, Retrieve, Update and Delete) operations on the actual calendar. The package includes two backends:
 
-* The `etesync_backend` subpackage provides a backend interface to the [EteSync](https://www.etesync.com/) calendar. In fact, `icalcli` was created primarily to provide a command line interface to my self hosted `EteSync` calendar.
+* The `etesync_backend` subpackage provides a backend interface to the [EteSync](https://www.etesync.com/) calendar (versions 1.0 and 2.0). In fact, `icalcli` was created primarily to provide a command line interface to my self hosted `EteSync` calendar.
 
 * The `file_backend` subpackage provides a backend interface to a calendar contained in a local `ics` file. This is useful as a viewer/editor of `ics` files. It is also useful to try out `icalci` without having any other backend configured.
 
@@ -33,6 +55,12 @@ The two included backends would also be useful to those who wish to write their
 pip install icalcli
 ```
 
+or via `pipx`:
+
+```sh
+pipx install icalcli
+```
+
 ### Install from source
 
 ```sh
@@ -40,6 +68,13 @@ git clone https://github.com/jrvarma/icalcli.git
 cd icalcli
 python setup.py install
 ```
+
+or via `pipx`:
+
+```sh
+pipx install . --editable
+```
+
 ## Usage
 
 ### Command line arguments
@@ -80,7 +115,7 @@ backend_interface = ICSInterface(["/path/to/ics-file-1", "/path/to/ics-file-2"])
 
 ```
 
-#### Example configuration for etesync_backend
+#### Example configuration for etesync_backend (etesync 1.0)
 
 This configuration assumes that all the credentials are stored in a plain text (`json`) file. In practice, you would use a more secure storage (perhaps, the `Gnome keyring`) or just read it from the terminal.
 
@@ -99,6 +134,34 @@ backend_interface = EtesyncInterface(
 ```
 See the [Example code](https://github.com/jrvarma/icalcli/issues/1#issuecomment-979851222) for getting the  `uid` and `authToken` for the `etesync` calendar.
 
+#### Example configuration for etebase_backend (etesync 2.0)
+
+This configuration assumes that all the credentials are stored in a plain text (`json`) file. In practice, you would use a more secure storage (perhaps, the `Gnome keyring`) or just read it from the terminal.
+
+```
+from icalcli import EtebaseInterface
+import json
+
+conf_file = '/path/to/json-file'
+with open(conf_file, 'r') as fp:
+    c = json.load(fp)
+
+backend_interface = EtebaseInterface(c['user'], c['server_url'], c['password'],
+                                     c['calendar_uid'], silent=False)
+```
+
+The `calendar_uid` can be obtained using the following code. This code assumes that the `dict c` has been populated with the credentials from the `json` file as above.
+
+```
+from etebase import Client, Account, FetchOptions
+
+client = Client(c['user'], c['server_url'])
+etebase = Account.login(client, c['user'], c['password'])
+col_mgr = etebase.get_collection_manager()
+print({col.uid: col.meta
+      for col in col_mgr.list("etebase.vevent").data})
+```
+
 ## Recurring events and default search period
 
 `icalcli` understands the `RRULE`, `RDATE`, `EXRULE`, `EXDATE` elements of the `icalendar` specification. These elements can be added while creating or editing events using `--rrule`, `--rdate`, `--exrule` and `--exdate` options.

{icalcli-1.0.5 → icalcli-1.1}/icalcli.egg-info/SOURCES.txt

@@ -1,9 +1,6 @@
-CHANGELOG.md
 LICENSE
 README.md
-exclude
 setup.py
-update-github.md
 icalcli/__init__.py
 icalcli/argparsers.py
 icalcli/icalcli.py
@@ -16,6 +13,8 @@ icalcli.egg-info/entry_points.txt
 icalcli.egg-info/requires.txt
 icalcli.egg-info/top_level.txt
 icalcli/etesync_backend/__init__.py
+icalcli/etesync_backend/etebase_crud.py
+icalcli/etesync_backend/etebase_interface.py
 icalcli/etesync_backend/etesync_crud.py
 icalcli/etesync_backend/etesync_interface.py
 icalcli/file_backend/__init__.py

{icalcli-1.0.5 → icalcli-1.1}/setup.py

@@ -5,7 +5,7 @@ with open("README.md", "r") as fh:
     long_description = fh.read()
 
 setup(name='icalcli',
-      version='1.0.5',
+      version='1.1',
       maintainer='Jayanth R. Varma',
       maintainer_email='jrvarma@gmail.com',
       description='Icalendar Calendar Command Line Interface',

icalcli-1.0.5/CHANGELOG.md

@@ -1,45 +0,0 @@
-# 1.0.5 released 2024-04-17
-
-* Added `cal5w` command to provide current week, two past weeks and two future weeks in a calendar format. 
-* Introduced option to get more event details (end time, alarm, location, free/busy) in week and calendar views.
-* Extended the file backend to allow multiple `ics` files in read only mode.
-
-# 1.0.4 released 2022-10-11
-Bug fixes
-
-# 1.0.3 released 2022-09-19
-Bug fixes
-
-# 1.0.2 released 2022-08-17
-Bug fixes
-
-# 1.0.1 released 2022-08-16
-Bug fixes
-
-# 1.0.0 released 2022-08-16
-
-## Added
-
-* Added support for recurring events using [python-recurring-ical-events ](https://github.com/niccokunzmann/python-recurring-ical-events). 
-* It is also possible to create and edit recurring events The recurrence rule has to be given as a string using the `--rrule` option to the `add` and `edit` commands (for example `--rrule FREQ=DAILY;COUNT=5`). Editing/deleting modifies/deletes all occurrences of the event. To delete a single occurrence, use `--exdate`.
-* Added support for creating/editing events using raw ICS text. This is mainly for properties (like `attendee` and `comment`) that are not available as command line options.
-* If duplicate UIDs are found, they are de-duplicated and the calendar is opened in read only mode. Editing a file with multiple UIDs is dangerous.
-
-## Changed
-
-* Searching for events without any start or end parameters now returns event occurrences only within the last 5 years and next 5 years (this number can be changed with the option `--default_past_years` and `--default_future_years`). More events can be obtained using explicit start and end parameters. For example, `s home '-10 y' 15y` will go back 10 years and forward 15 years. This change was necessitated because a single recurring event (without any `COUNT` or `UNTIL` restrictions) can generate an infinite number of occurrences.
-* The `-u` or `--uid` option has been removed and replaced by a more general `-p` or `--property` option that allows any property of the event to be searched. For example, `s -p rrule DAILY` will display all events with a recurrence rule that has a daily frequency.
-* Many Bug fixes.
-* Several method names were changed (the leading underscore was dropped from all method names), but these were intended to be used only internally. 
-
-# 0.9.9 released 2022-07-12
-
-## Added
-
-* Check for errors while parsing `iCalendar` events
-* Added option to provide stack trace for errors. By default, most errors are caught using try blocks and only a cryptic summary is provided. With this option, the stack trace is printed, but the program continues to run.
-
-## Changed
-
-* A few bug fixes
-

icalcli-1.0.5/exclude

@@ -1,7 +0,0 @@
-**build**
-**dist**
-**file_backend_n_screenshots**
-**egg-info**
-**__pycache__**
-exclude
-update-github.md

icalcli-1.0.5/update-github.md

@@ -1,33 +0,0 @@
-# After updating local file in /0/bp/
-
-* Update local github folder with remote by Pull from origin/master
-* `rsync -avc --dry-run --exclude-from ~/0/bp/icalcli/exclude \
-  /home/jrvarma/0/bp/icalcli/ /home/jrvarma/0/src/github/icalcli/`
-* `rsync -avc --exclude-from ~/0/bp/icalcli/exclude \
-  /home/jrvarma/0/bp/icalcli/ /home/jrvarma/0/src/github/icalcli/`
-* Commit changes in local github folder
-* Push to remote origin/master
-
-# After updating repo
-
-* `rsync -avc --dry-run  --exclude '.git/' --exclude screenshots\
-  ~/0/src/github/icalcli/ ~/0/bp/icalcli/ `
-* `rsync -avc  --exclude '.git/' \
-  ~/0/src/github/icalcli/ ~/0/bp/icalcli/ `
-
-## Update PyPi
-
-* Bump version number (Edit `setup.py`)
-
-```
-cd ~/0/bp/icalcli
-rm /0/bp/icalcli/dist/*
-python3 setup.py sdist bdist_wheel
-python3 -m twine upload dist/*
-```
-
-## Install new version from PyPi
-
-```
-pip install --upgrade icalcli
-```