Saravanan666/pypi-org huggingface dataset:
Package: zdsync
zdsyncis a command-line utility for syncing Zendesk environments.DependenciesPython 3.5+zenpyUsageIf you install withpython setup.py installor through pip, this should drop a program namedzdsyncinto your PYTHONHOME. Otherwise, you can usePYTHONPATH=. python -m zdsync.clito get the same effect.There are two required environment variables,SANDBOX_SUBDOMAIN- The subdomain of your sandbox environment, e.g.mycompany1552085434.PRODUCTION_SUBDOMAIN- The subdomain of your production environment, e.g.mycompany.There are three ways to authenticate to the Zendesk API and different environment variables are needed depending on your preferred method of authentication.Email & PasswordSANDBOX_EMAIL- The email that is used as your username when logging into your sandbox environment.SANDBOX_PASSWORD- The password that is used when logging into your sandbox environment.PRODUCTION_EMAIL- The email that is used as your username when logging into your production environment.PRODUCTION_PASSWORD- The password that is used when logging into your production environment.Email & API TokenSANDBOX_EMAIL- The email that is used as your username when logging into your sandbox environment.SANDBOX_TOKEN- An API Token for the sandbox environment.PRODUCTION_EMAIL- The email that is used as your username when logging into your production environment.PRODUCITON_TOKEN- An API Token for the production environment.OAuth TokenSANDBOX_OAUTH_TOKEN- An oauth token withread/writeaccess to the sandbox environment.PRODUCTION_OAUTH_TOKEN- An oauth token withread onlyaccess to the production environment.There are five supported objects for syncing,--brands--groups--ticket-fields--ticket-forms--macrosIt its recommended to sync in this order since there are object dependencies as you progress through the list. If you pass the--allflag it will sync in this order.Just passing an object flag or--allwill print out the status of the environments,$ zdsync --macros

The following Macros only exist in the sandbox:


The following Macros only exist in production:


The following Macros are different between environments:
Customer not responding       Downgrade and inform          Close and redirect to topics  Take it!

There are 257 other Macros that are the same between environments.In order to actually execute the sync you must pass the--executeflag,$ zdsync --macros --executeLicenseThis tool is licensed under the ISC License, the text of which is available atLICENSE.txt.
Package: ze2nb
zeppelin2nb: Zeppelin to jupyter notebookThis is my Zeppelin notebook to jupyter notebook python library repositories. This library is based on Ryan Blue's Jupyter/Zeppelin conversion:https://github.com/rdblue/jupyter-zeppelin.TheAPIcan be found at:https://runawayhorse001.github.io/ze2nb.
If you want to install it, you canInstall from PyPIYou can install the zeppelin2nb fromPyPI:pip install ze2nbInstall from RepoOr you can install the zeppelin2nb from the repo:1. clonegit clone https://github.com/runawayhorse001/ze2nb.git2. installcd ze2nb
pip install -r requirements.txt 
python setup.py install3. testcd zeppelin2nb/test
python demo.py4. uninstallpip uninstall ze2nb
Package: ze2nb-cli
Installationpip3installze2nb-cliUsageusage:ze2nb[-h][-iINPUT][--run-all][--out-pathOUT_PATH][--to-html][--to-py]optionalarguments:-h,--helpshowthishelpmessageandexit-iINPUT,--inputINPUTTheinputfile_name--run-allIfset,walksthroughthisdirectoryandconvertsall*.jsontoipynb--out-pathOUT_PATHOutputpath--to-htmlConvertstoHTML--to-pyConvertsto.py
Package: zeal-cli
Zeal CLIZeal CLI is a command-line-interface for managingZealdocsets on Linux. It's syntax is roughly based on the basic syntax of theaptpackage manager, because Zeal CLI is basically a package manager for docsets.FeaturesSimple, familiar command-line interfaceGets docsets from the same source as ZealEasy to install and use - no additional dependencies required.Docsets can still be managed within the Zeal GUIFree and Open-SourceTechnologiesPython 3PyInstallerUsageView theusage documentationfor using instructions.ContactTo submit a Bug Report or Feature Request, please open aGitHub Issue.To ask a question or get support, you can join myDiscord Serveror create a Discussions thread within this repository.ContributingThis project is maintained my Morpheus636. Contribution guidelines for all of my projects can be found athttps://docs.morpheus636.com/contributingCreditsZeal_CLI sources docsets fromDash, just like Zeal. Special thanks to Dash's developer,Kapelifor granting me permission to use their docsets.Copyright Notice© Copyright 2021-2022 Josh Levin (Morpheus636)This repository (and everything in it) is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.This repository is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.You should have received a copy of the GNU General Public License
along with this repository.  If not, seehttps://www.gnu.org/licenses/.
Package: zeal-feeds
zeal-feedszeal-feedsis a command line application for adding user contributed docsets toZeal,
as an alternative to looking up the URL of the XML feed and pasting in theAdd Feedoption.Table of ContentsInstallationUsageAcknowledgementsLicenseInstallationThe recommended way to installzeal-feedsis viapipx,
to provide an isolated installation.$pipxinstallzeal-feedsAlternatively,zeal-feedscan be installed viapip,
either for the current user or into the current Python virtual environment.WarningThis package will install several dependencies into the current environment.
Consider usingpipxto avoid dependency conflicts.$pipinstall--userzeal-feedsor$pipinstallzeal-feedsUsageTo search available feeds, usezeal-feeds search:$zeal-feedssearchalpine⠴ Loading index of user contributed docsetsMatching docsets:Alpinejs (3.7.x/5_2021-12-14)To install feeds, usezeal-feeds install.
The docset name needs to match the name from thesearchresults:$zeal-feedsinstallalpinejsattrsUsing cached index of user contributed docsetsDownloading Alpinejs ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00.   Installing AlpinejsDownloading attrs ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00.   Installing attrsIf a docset is already installed then it will be skipped.AcknowledgementsThis project was inspired byzeal-user-contrib,
but the apparent lack of annpmequivalent ofpipxfor isolated installations prompted writing a Python version.Thisarticleby Hynek Schlawack for introducing Dash/Zeal.https://zealusercontributions.vercel.app/for providing the docset API with XML feeds for Zeal.ContributingPlease open an issue or pull request on GitHub if you have questions, ideas, or issues.zeal-feedsuseshatch.
Runhatch run lintto run checks (Black, Ruff, and mypy) andhatch run test:pytestto run unit tests.Licensezeal-feedsis distributed under the terms of theMITlicense.
Package: zealous
Zealous FrameworkDocumentation:https://python-zealous.gitlab.io/zealous/Source Code:https://gitlab.com/python-zealous/zealousZealous is a framework that aims to simplify specification-driven development.It is built from the ground up with emphasis on static type checking to ensure that the
specification is respected while developing around it.The framework's core elements run in an asyncio event loop so concurrency is supported
out of the box.
Package: zeam.component
zeam.componentis inspired byzope.componentandgrokcore.component, but stays much simpler, and have less
base concepts. Hopefully this improve flexibility.RegistrationA base class can be used to register a component,zeam.component.Component. It supports all the directivesgrok.context,grok.adapts,grok.providesandgrok.namelike they are defined in Grok. You can use those to register your
component as either an Utility, an (named) Adapter or a (named)
MultiAdapter.An another possibility to register a component is to use thecomponentdecorator,zeam.component.component. It takes as
arguments the interfaces that the component adapts, and as keyword
arguments,providestheInterfacethat the component provides,
and asnamethe name under which it will be registered.LookupYou can lookup a specific registered component withzeam.component.getComponent. You can optionally provide:specs: a tuple of objects or specifications that the component
must adapt in order to be returned.provided: anInterfacethat the component must provides in
order to be returned.name: a name under which the component must be registered in
order to be returned.default: a default value that will be returned if no component
match the requirements. If you no default value is provided, and no
component is found, an exception will be triggered.You can lookup a list of possible registered component withzeam.component.getAllComponents. You can optionally provide:specs: tuple of objects or specification stat the component must
adapt in order to be returned.provided: anInterfacethat the component must provides in
order to be returned.Please note that in both cases the component is directly returned. In
any case, no construction is done with the result of the lookup.An helperzeam.component.getWrapperthat support the same options
than thezeam.component.getComponentfunction will call the result
of the lookup passing as argument the values given asspecsto
it. This is used in order to have agetAdapterorqueryAdapterlike behavior. Please note that if an error happens during the
initialization of the component, the error won’t be catched for you.Changes1.0 (2012/09/03)Initial release.
Package: zeam.form.autofields
zeam.form.autofieldsis able to collect fields definition for your
form. This enable you to create forms with a plugable list of fields.ContentsExampleAPIClassesDirectivesPropertiesChangelog1.0.1 (2012/05/02)1.0 (2011/11/08)ExampleYou need first to define a group of fields. This will be just an
interface:>>> from zope.interface import Interface

>>> class IReplyFields(Interface):
...    passNow you can define groups of fields:>>> from zeam.form import base, autofields

>>> class ReplyInformation(autofields.AutoFields):
...     autofields.group(IReplyFields)
...     autofields.order(0)
...     fields = base.Fields(base.Field('Comment'))

>>> class ReplyBlogInformation(autofields.AutoFields):
...     autofields.group(IReplyFields)
...     autofields.order(10)
...     fields = base.Fields(base.Field('Blog URL'))And you will be able to use those fields on your form somewhere else:>>> class ReplyForm(base.Form):
...     fields = autofields.FieldsCollector(IReplyFields)APIIn addition to its API,zeam.form.autofieldsexport the one ofzeam.form.base.ClassesAutoFieldsBase classes used to define a group of Fields to be included in a form.DirectivesgroupDirective used onAutoFieldswhich select for which group you
whish to provide the fields for. A group is just a plain zope
interface, that will be given as parameter to theFieldsCollector.viewDirective used onAutoFieldsthat will let you specify for
which Form (or view) you whish to provide the fields for. This
directive is not required, and default toIBrowserView.orderOptional directive which let decide in wich order the fields will
included at the end.PropertiesFieldsCollectorProperty used to collect form Fields for you.Changelog1.0.1 (2012/05/02)Update to use the latest version ofgrokcore.component.1.0 (2011/11/08)Initial release
Package: zeam.form.layout
zeam.form.layoutlet you embbed azeam.form.baseform inside a
layout created withgrokcore.layout.You just have to importForm(orComposedForm) fromzeam.form.layoutinstead of their original package.Default templates are defined ready to be used inside a layout.Changelog0.3.1 (2012/10/11)Modernize and fix broken tests, that were still relying onmegrok.layout.0.3 (2012/04/27)Usegrokcore.chameleoninstead ofmegrok.chameleon.Usegrokcore.layoutinstead ofmegrok.layout.0.2 (2010-10-27)Corrected templates to use the latest version ofzeam.form.base.Added tests related to templates rendering.0.1 (2010-06-01)Initial release
Package: zeam.form.plone
zeam.form.ploneprovides support forzeam.form.baseinto Plone
3, 4 and 5:make forms and security work in Zope 2,default form template using Plone macros,provide a simple simple edit form,use Plone status message system to report status,provides extra widgets, like a WYSIWYG text widget.ExampleLet’s define a simple example:from zeam.form.plone import EditForm
from zeam.form.base import Fields

class EditPeople(EditForm):
    label = u"Edit people"
    fields = Fields(IPeople)
    fields['summary'].mode = 'plone.wysiwyg'If you install the extensionZeam Formyou will get nicer CSS and
extra JS for the widgets.For more information information, please refer tozeam.form.baseand to the Grok documentation.Changes1.1 (2017-06-22)Support zeam.form.ztk and zeam.form.base >= 1.31.0 (2011/08/11)Support zeam.form.ztk 1.1.Add CSS and JS for new collection widgets.1.0b1 (2010/05/03)Initial release.
Package: zeam.form.rdb
zeam.form.rdbprovides an helper to generate form fields forzeam.form.base, usingzeam.form.ztkfields from anSQLAlchemymodel.To accomplish, you must create your fields using the descriptorModelFieldsin your form. It will automatically fetch the context
of the form, and generate the fields accordingly, caching them (for
performance reasons).Example:from zeam.form.rdb import ModelFields
from zeam.form.base import Form

class MyForm(Form):
    label = "Test form"
    fields = ModelFields()In yourSQLAlchemyschema, you can use the extra dictionnaryinfoto control the widget generated. Foreign key will generate a
choice of possible values to select, using the column you desire as
title.Example:from sqlalchemy import Column, ForeignKey
from sqlalchemy.types import Integer, String
from zeam.form.ztk.widgets.uri import URIField

idT_Effort = Column(
    'idT_Effort',
    Integer,
    primary_key=True,
    info={'title': u"Identifier"})
idT_Opportunity = Column(
    'idT_Opportunity',
    Integer,
    ForeignKey('T_Opportunity.idT_Opportunities'),
    info={'title': u'Opportunity',
          'foreignTitleColumn': 'Title'})
Name = Column(
    'Name',
    String(45),
    info={'minLength': 20,
          'maxLength': 45})
URL = Column(
    'URL',
    String(63),
    info={'title': u"URL",
          'description': u"Website URL"
          'factory': URIField,
          'defaultValue': 'http://github.com',
          'required': True})For a ForeignKey, you have the possibility to provides multiple
columns toforeignTitleColumn, and a function to be called to
create the title asforeignTitleFactory, both in theinfodictionnary.foreignTitleQuerycan specified to refine the
SQLAlchemy request used to obtain the title terms.A field will be required unless the column is nullable, or the optionrequiredis given throughinfo.titleanddescriptionfrominfowill be used as well in
order to create the form field.Changes1.0.1 (2012/12/12)Fix title factory to support unicode values.1.0 (2012/10/11)Refactor not to rely any longer onzope.schemaormegrok.rdb. SQLAlchemy Column’s are directly converted to zeam
form fields. This requireszeam.form.ztk1.3 or higher.Add tests on field generation.1.0b2 (2012/06/21)Add support fortitle_queryto filter out terms in a generated
ForeignKey vocabulary.1.0b1 (2012/04/27)Initial version.
Package: zeam.form.silva
zeam.form.silvais the integration ofZeam ForminSilva.This packages provides forms for SMI (including default add and edit
forms for content), ZMI (service configuration forms), and public
views usage (page forms, and viewlet/content provider forms).For more information about this, please check theSilva developer
documentation.Code repositoryYou can find the code of this extension in Git:https://github.com/silvacms/zeam.form.silvaChanges2.0.5 (2013/12/20)Add classes to create forms for Silva services in SMI.Improve the upload widget when a clear button is displayed.2.0.4 (2013/10/09)Implement a new upload widget based on a different extension than before.2.0.3 (2013/05/24)Add a specific template and CSS for public form.Update SMI templates.Update javascript to support jQuery 1.9.Improve ID widget.2.0.2 (2013/03/07)Fix inline validation that was not activated inside dialogs.2.0.1 (2013/03/06)Update ID widget to work in a Zope context (for theAdd a Silva
RootZope homepage).Update default z-index for the upload widget, in order to make it
usuable via the reference windows inside the text editor.2.0 (2012/12/11)Use alternate layout for checkbox: they are displayed before the
label and not after.Add more contextual help in SMI special widgets.Update to Zeam form 1.3.IE and Webkit fixes for some Javascript widgets.Add a custom widget for the identifier field.Add support for a confirmation dialog when an action is clicked on.2.0c1 (2012/09/24)Add new widgets, combobox, multipickup and a date widget with the
jqueryUI date selector.Add support for XML serialization.Improve form templates and styling.Improve the JS (inline validation and form popup) integration.2.0b1 (2011/11/10)Update code for Zope 2.13 and Python 2.7.Add a bit HTML 5 support for forms.Usesfanstatic.Inline validation works on more fields now.Popup forms have been updated to work withsilva.ui.SMI forms now are REST-based on top ofsilva.ui.Add a new file upload widget, and a image cropping one, improves
other existing widgets.1.2 (2010/12/20)Add a new textarea widget calledlinesable to edit collection
of textlines.1.1 (2010/10/27)Review security restriction on add forms and edit forms.Add support foradd in positionin default add forms.Various improvements in the form code (status feedback), default
form templates and i18n.Add a datetime widget based on the JQueryUI datetime picker.Add some Javascript helpers: inline validation via AJAX query on
simple form widgets. By default the first required field of a form
gets the focus.Add support to create REST forms in a popup in SMI or included in
Kupu.Add support for public forms.Add support for zope.interfaces invariant by default in SMI forms.1.0 (2010/07/16)Initial release.
Package: zeam.form.table
zeam.form.tableis a extension tozeam.form.baseto create CRUD
forms: it let define forms that can work on a collection of contents
sharing the same form schema.As wellzeam.form.tablecan be embedded as a sub form in a
composed form built withzeam.form.composed.Changelog1.1.1 (2012/10/11)Update SelectField to be compatible withzeam.form.base1.3.1.1 (2012/09/24)Add support to provide item specific identifiers for lines checkbox.Update API to usezeam.form.base1.2.3.1.0.1 (2012/04/27)Update to usegrokcore.chameleoninstead ofmegrok.chameleon.Fix some action type when used withpostOnly.Fix template, add missing fields in it.1.0 (2011/11/07)Add different strategies to apply actions to table lines. You can by
choice have one action that takes all selected and all not selected
lines, one actions on lines that have been selected or deselected or
lastly an action that execute only on select lines.Add support for batching on table forms.You can now customize the selection field.Update to work with zeam.form.base 1.2.Update tests.1.0b1 (2010/10/27)Initialproof of conceptrelease.
Package: zeam.form.viewlet
zeam.form.viewletprovide you with aZeam
Formin a viewlet.ExampleQuick example:from zeam.form import base
from zeam.form.viewlet import ViewletForm

class CallUs(ViewletForm):

   label = u"Call us"

   fields = base.Fields(base.Field("Phone number"))
   actions = base.Actions(base.Action("Call"))Changelog1.2.1 (2012/04/27)Update to usegrokcore.chameleoninstead ofmegrok.chameleon.1.2 (2011/11/08)Update test with a cleaner setup.1.1 (2010/10/18)Add a ViewletManagerForm.Add tests.Update form templates to be compatible with last version ofzeam.form.base.1.0 (2010/07/16)Initial release.
Package: zeam.jsontemplate
zeam.jsontemplateIntroductionThis library packages a patched version of json template forfanstatic. This behaved exactly like the official version, except
it add an optionundefined_callablethat is a function that will
be called in case of an undefined value, to return the value to be
use.This requires integration between your web framework andfanstatic,
and making sure that the original resources (shipped in theresourcesdirectory inzeam.jsontemplate) are published to some URL.How to use?You can importjsontemplatefromzeam.jsontemplateandneedit where you want these resources to be included on a page:>>> from zeam.jsontemplate import jsontemplate
>>> jsontemplate.need()CHANGES0.1 (2011/11/07)Initial release.
Package: zebra
Usage:from zebra import Zebra

z = Zebra( [queue] )
  Constructor with optional printer queue

z.getqueues()
  Return a list containing available printer queues

z.setqueue( queue )
  Set the printer queue

z.setup( direct_thermal=None, label_height=None, label_width=None )
  Set up the label printer using EPL2. Parameters are not set if they are None.
  Not necessary if using AutoSense (hold feed button while powering on)
    direct_thermal - True if using direct thermal labels
    label_height   - tuple (label height, label gap) in dots
    label_width    - in dots

z.reset_default()
  Resets the printer to factory settings using EPL2

z.reset()
  Resets the printer using EPL2 - equivalent of switching off/on

z.autosense()
  Run AutoSense by sending an EPL2 command
  Get the printer to detect label and gap length and set the sensor levels

z.print_config_label()
  Send an EPL2 command to print label(s) with current config settings

z.store_graphic( name, filename )
  Store a 1 bit .PCX file on the label printer using EPL2
    name     - name to be used on printer
    filename - local filename

z.print_graphic( x, y, width, length, data, qty )
    Print a label from 1 bit data, using EPL2
      x,y    - top left coordinates of the image, in dots
      width  - width of image, in dots.  Must be a multiple of 8.
      length - length of image, in dots
      data   - raw graphical data, in bytes
      qty    - number of labels to print

z.output( commands )
  Output raw commands to the printer

z.print_config_label()
  Print label(s) containing the current printer configuration using EPL2Note:If you are on a Linux or MacOSX machine using CUPS, you may need to set up a
printer queue using the admin panel athttp://localhost:631Changelog0.1.0class name is now ‘Zebra’ instead of ‘zebra’Fix for missing win32print module in pypiDrop python 2 supportuse setuptools instead of distutilsimprove documentationAdded reset(), reset_default(), autosense(), print_config_label() and
print_graphic() functions0.0.5Added -oraw to lpr command to make more CUPS installations work0.0.4 and earlierUndocumented!
Package: zebracorn
ZebracornZebracorn is a lightweight, multi-platform, multi-architecture CPU emulator framework
based on a fork ofUnicorn.The API is identical to Unicorn, but Zebracorn offers a few additional features:Hooks:RDTSC instructionBlock TranslationCallback after N blocks executedExecution Info:Block count executedInstruction count executedInstruction Meta:Tiny Code Generator (TCG) representation of each instructionUnicorn AFL integrationThese APIs are only supported through the Python bindings.The Zebracorn engine is primarily made available to support functionality in thezelos binary emulator.InstallationZebracorn is distributed as a pythonpippackage. Other bindings are not supported. To install the python package:$pipinstallzebracornPython packages are available for Windows, Linux and MacOS.LicenseUnicorn and Qemu are released under theGPL license.