Saravanan666/pypi-org huggingface dataset:
Package: ibus-theme-tools
IBus Theme ToolsWelcome to contribute your translation on Weblate!中文 ChinesePython Library DependencyPre-knowledgeIBus has its front-end based on GTK, and GNOME replace that front-end with its GJS version to make it more unified with GNOME.As a result, in non-GNOME Shell desktop environment, the display effect of IBus is determined by the current GTK theme.$HOME/.config/gtk-3.0/settings.inidefines the current GTK3 theme and font size.Example of the content of the file is as follows:[Settings]gtk-theme-name=Materia-lightgtk-font-name=更纱黑体 SC 12In the above content,gtk-theme-namespecifies that the current GTK theme ismaterial-light,gtk-font-namespecifies that the current font is更纱黑体 SCand the font size is `12 '.The IBus font and font size can be changed by modifying the above documents.As for the color scheme of IBus, you can specify that it uses specific GTK theme when IBus starts, and then customize the color matching of IBus.InstallationYou can directly use pip to install:pipinstallibus-theme-tools
ibus-theme-toolsOr just install manually:gitclonehttps://github.com/openSUSE/IBus-Theme-Tools.gitcdIBus-Theme-Tools&&python3setup.pyinstall
ibus-theme-toolsIf you use Arch Linux, you can also use AUR to install as a system extension:yay-Sibus-theme-toolsUbuntu PPAFunctionalityNon-GNOME desktopGenerate the IBus GTK theme in a non-GNOME Shell desktop environment and supporting to select a background picture or configure border radius.Runibus_theme_tools.pyscript, operate according to prompted message.After generating the new theme, just select the theme in the system theme configuration.If you install themes that support GNOME shell style, you can also choose to extract IBus style, but you can only use it on GNOME desktop.Customize IBus colors (Create a GTK theme)Create a GTK3 theme calledibus-custom-themeby running:mkdir-p$HOME/.themes/ibus-custom-theme/gtk-3.0$EDITOR$HOME/.themes/ibus-custom-theme/gtk-3.0/gtk.cssthen edit the file content. An example can be:*{color:#0b141a;/* Font Color */background-color:#ffffff;/* Background Color */-gtk-secondary-caret-color:#d4d4d4;/* Highlight Background Color */}After that, run the program, then select the themeibus-custom-themewhich you just created.GNOME desktopExtracting IBus style from GNOME Shell theme, implement it using CSS parser librarytinycss2in Python. Additional IBus style sheets are generated for users to modify and test.Runibus_theme_tools.pyscript, operate according to prompted message.When user chooses a theme from the list, this script will first read the theme CSS file, extract the IBus related style classes (.candidate-*), then write it to stylesheet.Then use theCustomize IBus GNOME Shell extensionto import and apply themes.Note:If your IBus style sheet has changed after application, please close and reopen the correspondingcustom IME themeto make it effective.Starting from v69, now this extension support stylesheets hot reload, CSS changes will reflect in real-time.Sample extracted stylesheet:exportedIBusTheme.cssNoteThis project was part of the achievement of@HollowMan6partipating theGoogle Summer of Code 2021atOpenSUSE.
Package: ibutsu-utils
Ibutsu UtilitiesSome command line utilities forIbutsu. There are currently two
tools:Download artifacts - ibutsu-downloadUpload test runs - ibutsu-uploadCombine JUnit XML files - ibutsu-xmergeInstallationThese utilities are available onPyPIand can be installed withpip:$ pip install ibutsu-utilsDownload ToolTheibutsu-downloadcommand line tool downloads an artifact from Ibutsu.$ ibutsu-download -h
usage: ibutsu-download [-h] -H HOST [-t API_TOKEN] [-o OUTPUT] artifact_id

A tool to download an artifact from an Ibutsu server

positional arguments:
  artifact_id           The ID of the artifact to download

options:
  -h, --help            show this help message and exit
  -H HOST, --host HOST  The Ibutsu instance for uploading, e.g. https://my.ibutsu.com/api
  -t API_TOKEN, --api-token API_TOKEN
                        An API token for authentication
  -o OUTPUT, --output OUTPUT
                        The destination to save the file. If omitted will use the current directory and the artifact file nameUpload ToolTheibutsu-uploadcommand line tool uploads JUnit XML or Ibutsu archives to Ibutsu.$ ibutsu-upload --help
usage: ibutsu-upload [-h] -H HOST -p PROJECT [-t API_TOKEN] [-s SOURCE] [-m METADATA] [-w] input [input ...]

A tool to upload a jUnit XML or Ibutsu archive to Ibutsu

positional arguments:
  input                 The file(s) to upload

options:
  -h, --help            show this help message and exit
  -H HOST, --host HOST  The Ibutsu instance for uploading, e.g. https://my.ibutsu.com/api
  -p PROJECT, --project PROJECT
                        The project for the upload
  -t API_TOKEN, --api-token API_TOKEN
                        An API token for authentication
  -s SOURCE, --source SOURCE
                        The source used in the test results
  -m METADATA, --metadata METADATA
                        Additional metadata to set when uploading, in the format of dotted.key.path=value
  -w, --wait            Wait for the upload to complete (by default this command does not wait)Combine ToolSome test runners output multiple JUnit XML files for a single test run. Theibutsu-xmergeutility will combine multiple XML files into a single file.$ ibutsu-xmerge --help
usage: ibutsu-xmerge [-h] [-o OUTPUT] input [input ...]

positional arguments:
  input                 Input files

options:
  -h, --help            show this help message and exit
  -o OUTPUT, --output OUTPUT
                        Output to a file. Defaults to stdout without this.
Package: ib-wrapper
==========IB Wrapper==========.. image:: https://img.shields.io/pypi/v/ib_wrapper.svg:target: https://pypi.python.org/pypi/ib_wrapper.. image:: https://img.shields.io/travis/asteriogonzalez/ib_wrapper.svg:target: https://travis-ci.org/asteriogonzalez/ib_wrapper.. image:: https://readthedocs.org/projects/ib-wrapper/badge/?version=latest:target: https://ib-wrapper.readthedocs.io/en/latest/?badge=latest:alt: Documentation StatusDynamic runtime TWS IB API for pythonInspired in https://github.com/erdewit/ib_insync but much simplier.As the TWS-API wrapping is made dynamically, is always up-to-date with the underlying API installed version.Is not necessary to make code maintenance tasks every time IB release a new version.* Free software: MIT license* Documentation: https://ib-wrapper.readthedocs.io.Features--------* TODO- make a command line version to testing basic usages.- make test that check a trading session using a demo account.Credits-------This package was created with Cookiecutter_ and the `audreyr/cookiecutter-pypackage`_ project template... _Cookiecutter: https://github.com/audreyr/cookiecutter.. _`audreyr/cookiecutter-pypackage`: https://github.com/audreyr/cookiecutter-pypackage=======History=======0.1.0 (2019-01-18)------------------* First release on PyPI.
Package: icaclswrap
icaclswrapWindows ACL permissions management through wrapping calls to icacls windows executableFree software: MIT licenseDocumentation:https://icacls-wrapper.readthedocs.io.FeaturesCall windows executable ‘icacls’ to set persmissions with windows access control listsWraps calls as python functions, return values as python objects and exceptionsDownside: only works with access to the windows ‘icacls’ command, on a windows machineCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2018-12-04)First release on PyPI.
Package: ical
This is an iCalendar rfc 5545 implementation in python. The goal of this
project is to offer a calendar library with the relevant and practical
features needed for building a calendar application (e.g. recurring
events).ical's main focus is on simplicity, and the internal implementation
is based on existing parsing libraries, where possible, making it
easy to support as much as possible of rfc5545. It is not a goal to
support everything exhaustively, however, the simplicity of the
implementation makes it easy to do so.Seedocumentationfor full quickstart and API reference.QuickstartThe example below creates a Calendar, then adds an all day event to
the calendar, then iterates over all events on the calendar.fromdatetimeimportdatefromical.calendarimportCalendarfromical.eventimportEventcalendar=Calendar()calendar.events.append(Event(summary="Event summary",start=date(2022,7,3),end=date(2022,7,4)),)foreventincalendar.timeline:print(event.summary)Reading ics filesThis example parses an .ics file from disk and creates aical.calendar.Calendarobject, then
prints out the events in order:frompathlibimportPathfromical.calendar_streamimportIcsCalendarStreamfromical.exceptionsimportCalendarParseErrorfilename=Path("example/calendar.ics")withfilename.open()asics_file:try:calendar=IcsCalendarStream.calendar_from_ics(ics_file.read())exceptCalendarParseErroraserr:print(f"Failed to parse ics file '{str(filename)}':{err}")else:print([event.summaryforeventincalendar.timeline])Writing ics filesThis example writes a calendar object to an ics output file:frompathlibimportPathfromical.calendar_streamimportIcsCalendarStreamfilename=Path("example/output.ics")withfilename.open()asics_file:ics_file.write(IcsCalendarStream.calendar_to_ics(calendar))Application-level APIsThe above APIs are used for lower level interaction with calendar components,
however applications require a higher level interface to manage some of the
underlying complexity. Theical.storelibrary is used to manage state at a higher
level (e.g. ensuring timezones are created properly) or handling edits to
recurring events.Recurring eventsA calendar event may be recurring (e.g. weekly, monthly, etc). Recurring events
are represented in aical.calendar.Calendarwith a singleical.event.Eventobject, however
when observed through aical.timeline.Timelinewill be expanded based on the recurrence rule.
See therrule,rdate, andexdatefields on theical.event.Eventfor more details.Related WorkThere are other python rfc5545 implementations that are more mature, and having
been around for many years, are still active, and served as reference
implementations for this project:Ics.py -githubdocs- Since 2013icalendargithubdocs- Since 2005
Package: ical2notion
ical2notionICal2Notion is a simple command line tool that is used to update a Notion database from an .ical file hosted online (like on Google Calendar).InstallationTo install clone the repository and runpython setup.py install.UsageFind your Notion authentication token. This is located in thetoken_v2cookie under the domainwww.notion.so.Navigate to a Notion workspaceClick the lock on the left hand side of the URL barClick CookiesDrop down thewww.notion.solistDrop down theCookieslistCopy the content from thetoken_v2cookieCreate a database for the Google Calendar to be populated intoCreate a new pageCreate an inline tableClick "Open as page"Populate the database with a Name (Text), Do (Date), and Type (Select with "Event" tag premade).Copy that URLFind your ical public linkOpen google calendarClick on the three dots to the right of a calendar listed under My calendars on the bottom leftClick settings and sharingScroll all the way to the bottom and copy the "Secret address in iCal format" linkRunical2notion [TOKEN] [URL] [iCal]. You can list multiple icals at the end.TODOReoccuring tasks
Package: ical2orgpy
ical2orgpyThis script converts an ical calendar (for instance, as exported from google
calendar) into an org-mode document. It is conceived as a replacement of the
awk script located here:http://orgmode.org/worg/org-tutorials/org-google-sync.htmlThe main difference is that ical2orgpy correctly manages recurring events
of “yearly”, “daily” and “weekly” types. ical2orgpy duplicates all
recurring events falling into a specified time-frame into the exported
org-document.InstallationThe commandical2orgpyis provided by means of python packageical2orgpy.You can install withpip(preferably into its own into virtualenv):$ pip install ical2orgpyInstallation withpipxis recommended because
this will manage the virtualenv for you.Installing from source codeYou can install the package directly from git source like this:$ cd <to project folder>
$ pip install --user .To use the script, just call:$ ~/.local/bin/ical2orgpyUsageSimply use theical2orgpycommand:$ ical2orgpy --helpor, if installed locally from the git repo:$ ~/.local/bin/ical2orgpy --helpThe script requires two files, the input ics and the output org
document. Usually,ical2orgpyis called within a script that grabs the
ical file from some source (i.e. Google Calendar), and generates the
appropriate org document. Such an script would have the following shape:#!/bin/bash

# customize these
WGET=<path to wget>
ICS2ORG=<path to ical2org>
ICSFILE=$(mktemp)
ORGFILE=<path to orgfile>
URL=<url to your private Google calendar>

# no customization needed below

$WGET -O $ICSFILE $URL
$ICS2ORG $ICSFILE $ORGFILE
rm -f $ICSFILESee further instructions here:http://orgmode.org/worg/org-tutorials/org-google-sync.htmlDevelopmentClone the repository and cd into it.Create a virtualenv and install dependencies:$ pip install .
$ pip install -r test_requirements.txtRun tests to check everything is working:$ pytestYou can also use tox to create the virtualenv e.g.:$ tox -e py39Then activate the virtualenv:$ source .tox/py39/bin/activate
(py39)$And use the package.
Package: ical2vdir
ical2vdir 📅Convert / split singleiCalendar.icsfile into avdirdirectory.Pre-existing files will be updated or left unchanged.Compatible withkhal.Setup$sudoapt-getinstallpython3-icalendar# optional$pip3install--user--upgradeical2vdirUsage$ical2vdir<input.ics--output-dir/some/pathOr download.icsfromGoogle Calendar:$curlhttps://calendar.google.com/calendar/ical/someone%40gmail.com/private-1234/basic.ics\|pipenvrunical2vdir--output-diroutput/Remove files from output directory that are not available in input:$ical2vdir<input.ics--output-dir/some/path--delete
Package: icalendar_light
https://github.com/idlesign/icalendar_lightDescriptionLight and easy iCalendar event readerNo fancy stuff, just iCalendar (.ics) events reading.Requires Python 3.6+;Usesnamedtuplefor event representation;Features iterative event reading to be fast and minimize memory usage.APIfromicalendar_light.toolboximportCalendarforeventinCalendar.iter_events_from_file('my_calendar.ics'):print(Calendar.event_stringify(event))# Or get events upcoming in next 5 days from iCalendar represented as lines:lines=[]# Let's imagine this one is not empty %)events=Calendar.iter_events_upcoming(lines,days_forward=5)CLIRequiresclickpackage (can be installed with:pip install icalendar_light[cli]).;Showupcomingeventfornext90days$icalendar_lightupcomingmy_calendar.ics--days90
Package: icalevents
iCalEventsSimple Python 3 library to download, parse and query iCal sources.Build infolast push:master:Documentationhttps://icalevents.readthedocs.io/en/latest/UsageiCloud:fromicalevents.icaleventsimporteventses=events(<iCloudURL>,fix_apple=True)Google:fromicalevents.icaleventsimporteventses=events(<GoogleCalendarURL>)ContributingYou will needpoetryandpre-commitinstalled and than run.pre-commitinstallHappy contributing!
Package: icalevnt
iCalEventsSimple Python 3 library to download, parse and query iCal sources.Build infolast push:master:Documentationhttps://icalevents.readthedocs.io/en/latest/UsageiCloud:fromicalevents.icaleventsimporteventses=events(<iCloudURL>,fix_apple=True)Google:fromicalevents.icaleventsimporteventses=events(<GoogleCalendarURL>)ContributingYou will needpoetryandpre-commitinstalled and than run.pre-commitinstallHappy contributing!
Package: icall
Parameters call function, :-)You can do:from __future__ import print_function

print('x', 'y', sep=',')But I can not do:from __future__ import print_function

parameters = ('x', 'y', sep=',')
print(parameters)With icall, I can do similar thing:from __future__ import print_function
from icall import ICall

parameters = ICall('x', 'y', sep=',')
parameters(print)Sometimes, you may use Parameters(similar to ICall):from __future__ import print_function
from icall import Parameters

parameters = Parameters('x', 'y', sep=',')
parameters(format)Changes0.3.3(2014-09-16)Use reStructedText in text files.0.3.0Rename package ‘callwith’ to ‘icall’
Package: ical-library
Fast, yet simple, iCalendar reader with excellent recurrence support.RFC 5545compliant.Documentation:https://jorricks.github.io/iCal-library/Source Code:https://github.com/Jorricks/iCal-libraryFeatures🚀 Easy python interface. It's as simple as 'client.load_ics_file("<my_file>").timeline' to show all your events of that week.📈 Timeline support. Show exactly what is planned for a specific week.✨Fully functionalsupport for recurring iCal components. E.g. Any recurring event will show up as intended within the timeline interface. This includes:Recurring components/events based on RRule.Recurring components/events based on RDate.Excluding components/events based on EXDate.Any combination of the above three.Redefined/changed components/events correctly show the latest version.⏩ Very fast parsing due to lazy evaluation of iCal properties.⁉️ Debugger supported. Any issues? Open up a debugger and inspect all values.🔅 Minimal dependencies. Onlypython-dateutilandpendulum.🆎 Fully typed code base.RequirementsPython 3.8+iCal-library uses two major libraries for their date and time utilities:Pendulumfor its extensions on datetime objects and parsing of durations.Python-Dateutilfor its RRule support.InstallationTo use iCal-library, first install it using pip:pip install iCal-libraryExampleA simple example. Please lookin the docsfor more examples.fromical_libraryimportclientcalendar=client.parse_icalendar_file("/home/user/my_icalendar.ics")print(calendar.events)print(calendar.todos)print(calendar.journals)print(calendar.free_busy_list)print(calendar.time_zones)Note: iCal-library is fully Debugger compliant, meaning it is very easy to use a debugger with this project. It will be much faster to see all the different attributes and functions from inside a Python debugger. If you are unsure whether your IDE supports it, take a lookhereunder the sections 'IDEs with Debug Capabilities'.LimitationsCurrently, it is not supported to write ICS files. If this is a deal-breaker for you, it should be relatively straight forward to add it, so please consider submitting a PR for this :). However, this will be added shortly!Why yet another iCalendar library?I first tried several libraries for iCalendar events. However, none of them supported recurring events as well as they should be. For some libraries my calendar loaded but then didn't show my recurring events, while others simply threw stacktraces trying to load it. Furthermore, I noticed that my calendar (with over 2000 events) took ages to load.
After traversing the code of the other libraries I decided I wanted to build my own. With some key principles:Recurring components should be the main priority to get working.No strict evaluation that could lead to errors while parsing the file.Lazy evaluation for iCalendar properties to speed up the process.Ideas for additional featuresSupport quoted property parameters containing special characters.Support the new Properties for iCalendar (RFC 7986).Support CalDev (RFC 4791).
Package: icalretriever
ICalRetriever is a HTTP ICS retriever. It is designed to be called by a
crontab each hour in order to download an ICalendar file from a designed
HTTP location, eventually apply filters on it, and then write it to the
disk.Then, you can serve the ICal to WebDAV clients (using Radicale WebDAV
server for example) in readonly mode, so that their synchronised ICal
file is updated each hour conforming to the ICS HTTP source.InstallingICalRetriever is available on PyPI asicalretriever.UsageSimply call the retriever with the configuration file as parameter.$ icalretriever-retrieve.py myConfig.ymlConfiguration fileConfiguration is written in YAML.You can sync multiple calendar using one configuration file. Here is an
example of configuration file you may want to copy and adapt to your
needs:calendars:
 - name: Fake calendar (filtered)
   file: output_filtered.ics
   url: http://perdu.com/fake.ics
   filters:
     - name: remove_days
       args: [5, 6]
     - name: remove_name
       args: ["Boring event I dont want", "Another boring event"]

 - name: Fake calendar (not filtered)
   file: output.ics
   url: http://perdu.com/fake.icsLicenseThis program is brought to you under MIT license. For further
informations, please read the provided LICENSE file.
Package: icalstatus
ICAL Status - Status bar for ICS CalendersChangelog0.0.6Require python 3.11+ and upgrade dependenciesInstallationpipinstallicalstatusStatusTo run, one of:icalstatusicalwaybarConfigurationFor the status you must specify you calendar URL either on the commandline or in the
configuration file~/.config/icalstatus/config:E.g, for OWA:[DEFAULT]
calendar-url=https://(HOST)/owa/calendar/(...)/calendar.icsAll options can be specified in the same configuration file and
the other available options are:usage: ICAL Status [-h] [--calendar-url CALENDAR_URL] [--timezone TIMEZONE] [--no-verify] [--proxy PROXY] [--all] [--humanize-after HUMANIZE_AFTER]
                   [--alert-sec-before ALERT_SEC_BEFORE]

options:
  -h, --help            show this help message and exit
  --calendar-url CALENDAR_URL
                        URI for ICS Calendar
  --timezone TIMEZONE   Timezone (default=CET)
  --no-verify           Ignore SSL verification errors
  --proxy PROXY         Proxy for ICS url
  --all                 Include events that are not today
  --humanize-after-sec HUMANIZE_AFTER
                        Humanize meeting date if less than this many seconds
                        until meeting
  --alert-sec-before ALERT_SEC_BEFORE
                        Alert meeting at specified seconds before start.
                        This will switch class for output on waybar.Options:allBy default, only todays events will be shown (and output will be empty if
no more event the same day). Specify--allto show all events.humanize-after-secMeeting time will be show in "human format" if it less than this
many seconds until the meeting. E.g. if the time is 11:30 and you
have specified--humanize-after-sec 3600the output will be<Meeting> in 30 minutesIf you at 11:30 specified--humanize-afterit will show<Meeting> @12:00alert-sec-beforeThis option is only relevant foricalwaybar. If is is less than this
many seconds to the meeting, it will useclass: alert, otherwizeclass: normal. Examples (when running the command at 11:50):icalwaybar --alert-sec-before 900
{"text": "<Meeting> in 10 minutes", "class": "alert"}icalwaybar --alert-sec-before 300
{"text": "<Meeting> in 10 minutes", "class": "normal"}ParseA tool to parse ics files and output summary to stdout is included:icalparseCreditsOriginal code/idea from Geir Skjøtskift (https://github.com/geirskjo).