semvec/pypi-packages huggingface dataset:
ffcut 0.1.2
FFCut: Cutting Video with FFMpeg for Human Beings
License: MIT

=================================================
FFCut: Cutting Video with FFMpeg for Human Beings
=================================================

FFMpeg is a great tool, but cutting several parts of a video with it can
become a complex task. This small script serves to help with it.

Install it from PyPI::

    pip install --user ffcut

.. note:: ``--user`` flag makes ``pip`` install it to ``~/.local/bin``.

Then use like::

    ~/.local/bin/ffcut -i file1.mp4 -s ..0:10 -s 0:30..+20 -s 1:30..2:30 -s 3:00.. -i file2.mp4 -s 5:00.. -o final.mp4

Here you first specify input files with ``-i``, then slices to take from each
file with ``-s`` using format ``[begin]..[end]`` (both parts being optional).

You can also merge two or more files in one::

    ~/.local/bin/ffcut -i file1.mp4 -i file2.mp4 -o result.mp4

Use ``--copy`` flag to avoid re-encoding (may cause problems with playback).

Use built-in help for more details::

    ~/.local/bin/ffcut -h
django_schedulermanager 1.0.1
A package that allows you to schedule and unschedule jobs
License: MIT
Keywords: django_schedulermanager

Django Schedulermanager
=======================

Creates two commands ``schedulejob`` and ``unschedulejob`` that allows
you to schedule (and unschedule) background jobs.

If you have a brunch of jobs to start with your backend (e.g, if you
have to update your social feed every hour) you can just write the code
of the job, mark it with the ``schedulable`` decorator and the job will
be schedulable with the ``schedulejob`` command.

Right now the library uses ``django-rq`` + ``rq-scheduler``, but the
dependency on ``django-rq`` is not needed and will be removed soon.

How to use
----------

1. Install the library using ``pip install django_schedulermanager``
2. Add ``django_schedulermanager.apps.DjangoSchedulerManagerConfig`` to
   your INSTALLED\_APPS
3. Write your job code in a module named 'jobs' (Remember to insert the
   app in the ``INSTALLED_APPS`` list)
4. Import the ``schedulable`` annotation:
   ``from django_schedulermanager.decorators import schedulable``
5. Mark your function with ``schedulable``. You can pass to the
   decorator the following parameters:

   -  interval: The interval of the function. Required.
   -  scheduled\_time: When the function should start the first time.
      Required. It's a function.
   -  repeat: Not required, by default None which means 'repeat always'
   -  id: The ID of the job. It will also be the name of the job that
      you have to pass when using ``(un)schedulejob``. Not required, by
      default None which means 'use the name of the function'
   -  queue: The queue to use. By default 'default'

Now you can schedule and unschedule your jobs using
``python manage.py schedulejob <id>`` and
``python manage.py unschedulejob <id>``! Call those in your init script
and your jobs should schedule (and unschedule) automatically

See also ``test-project`` directory to see an example, if you want to
test the project, clone the repository and run the command
``make testproject``, it will copy the ``django_schedulermanager``
folder (the library code) in the ``test-project`` folder

TODO
----

-  [ ] Remove dependency on ``django-rq``
-  [ ] If present, read 'queue' from ``@job`` annotation
-  [ ] Add ``unschedulejob all`` to unschedule all the jobs
-  [ ] Add a command to remove all the scheduled jobs that don't have a
   function in the jobs.py files
merge_ics 0.2.0
Merge RFC5545 calendar files
License: MIT
Keywords: RFC5545 ics calendar

merge\_ics
==========

A simple Python script to merge
`RFC5545 <https://tools.ietf.org/html/rfc5545>`__ calendar files. It
accepts several input calendars (referred to as *sources*) and processes
them into one or more output calendar (*sinks*).

Installation
------------

::

    $ pip install merge_ics

Usage
-----

::

    $ merge_ics <config_file>

Config file format
------------------

``merge_ics`` reads configuration from YAML files passed through the
command line as above. These YAML files should contain two nodes:

-  ``sources`` specifies the input calendars, and
-  ``sinks`` describes the calendars that should be outputted by the
   script.

``sources``
^^^^^^^^^^^

The ``sources`` node should contain a mapping whose keys are arbitrary
identifiers for the input calendars. The values should again be
mappings, with the possible keys being ``filename`` and ``url``. The
value for ``filename`` should describe a local ics file, while that for
``url`` should point to a remote one. The presence of both keys will
result in ``merge_ics`` trying to read and parse the local copy,
downloading the remote copy only in case of error.

``sinks``
^^^^^^^^^

The ``sinks`` node should contain a collection, each of which is a
descriptor for an output calendar. These sink descriptors should contain
three keys:

-  ``filename``: the filename where to write the calendar.
-  ``sources``: a mapping with keys being the arbitrary identifiers of
   the sources that you want to merge. The events from each of these
   source calendars will be given the corresponding values in a
   ``CATEGORIES`` prop.
-  ``options``: a mapping of calendar-level props. Make sure to always
   include ``version`` and ``prodid`` (otherwise the resulting ics file
   will be non-conformant).

Example
~~~~~~~

::

    sources:
      1:
        filename: https://example.com/cal_local.ics
      online_cal:
        url: https://example.com/cal_online.ics
      2:
        filename: cal2.ics
        url: https://example.com/cal2.ics
    sinks:
      -
        filename: output_cal1.ics
        sources:
          1: Local Events
        options:
          version: 2.0
          prodid: -//Owner//LocalEvents//EN
          x-wr-calname: Local Events
          x-wr-caldesc: Events from my local calendar
          calscale: GREGORIAN
          method: PUBLISH
          x-published-ttl: PT15M
      -
        filename: output_cal123.ics
        sources:
          1: Local Events
          online_cal: Online Events
          2: Another Category
        options:
          version: 2.0
          prodid: -//Owner//Merged//EN
          x-wr-calname: Merged Calendar
          x-wr-caldesc: All my events
          calscale: GREGORIAN
          method: PUBLISH
          x-published-ttl: PT15M

License
-------

MIT
pylend 0.1.0
A Python library for interacting with the LendingClub REST API
License: MIT

pylend
------
A Python library for consuming the LendingClub public REST API. 

.. image:: https://travis-ci.org/Webs961/pylend.svg?branch=master
    :target: https://travis-ci.org/Webs961/pylend

.. image:: https://codecov.io/github/Webs961/pylend/coverage.svg?branch=master
   :target: https://codecov.io/github/Webs961/pylend
   :alt: Codecov

**Note**: This package is not written or supported by LendingClub.
ewer 0.13.dev0
Async Fork of Fast and simple WSGI-framework for small web-applications.
License: MIT

Bottle is a fast and simple micro-framework for small web applications. It
offers request dispatching (Routes) with URL parameter support, templates,
a built-in HTTP Server and adapters for many third party WSGI/HTTP-server and
template engines - all in a single file and with no dependencies other than the
Python Standard Library.

Homepage and documentation: http://bottlepy.org/

Copyright (c) 2015, Marcel Hellkamp.
License: MIT (see LICENSE for details)