Saravanan666/pypi-org huggingface dataset:
Package: z0lib
Overviewz0lib is a simple bash and python library.It was created to give support to bash and python software.
The package has both bash version and both python version of functions.
Since 2022, bash development was abandoned and only python code is stil upgraded.ImportantHowever, most functions are still available for bash scripts.The available libraries are:z0librc: bash version libraryz0librun.py: python version libraryFeaturesDescription,bash,python,Note(s)
run_traced,✅,✅,Run os command with trace
xuname,✅,❌,OS indentity (python has native function)
parseoptargs,✅,❌,Command line parser (python has native function)
link_cfg,✅,❌,Get values from configuration file (python has native function)Getting startedPrerequisitesZeroincombenze tools requires:Linux Centos 7/8 or Debian 9/10 or Ubuntu 18/20/22python 2.7+, some tools require python 3.6+, best python 3.8+bash 5.0+InstallationStable version via Python Packagepip install z0libCurrent version via Gitcd $HOME
[[ ! -d ./tools ]] && git clone https://github.com/zeroincombenze/tools.git
cd ./tools
./install_tools.sh -pUT
source $HOME/devel/activate_toolsUpgradeStable version via Python Packagepip install --upgrade z0libCurrent version via Gitcd ./tools
./install_tools.sh -pUT
source $HOME/devel/activate_toolsChangeLog History2.0.9 (2024-02-01)[IMP] Internal matadata2.0.8 (2023-10-16)[FIX] parseopt2.0.7 (2023-07-20)[FIX] run_traced return system exit code[IMP] run_traced: new rtime parameter to show rtime output[IMP] New main2.0.5 (2023-05-14)[FIX] Sometime configuration init fails[IMP] Configuration name LOCAL_PKGS read real packages[IMP] is_pypi function more precise2.0.4 (2023-04-10)[FIX] run_traced: cd does not work w/o alias[IMP] coveralls and codecov are not more dependencies2.0.3 (2022-12-22)[FIX] run_traced: –switch sometime crashes[FIX] run_traced: alias function2.0.2 (2022-12-07)[FIX] best recognition of python version[FIX] run_traced: fail with python 22.0.1 (2022-10-20)[IMP] Stable version2.0.0.4.1 (2022-10-20)[FIX] run_traced: wrong execution for “cd <path>; …”[IMP] CFG_init ‘ALL’: set ODOO_ROOT2.0.0.4 (2022-10-05)[IMP] python2 tests2.0.0.3 (2022-09-30)[FIX] run_traced return code2.0.0.2 (2022-09-14)[IMP] run_traced for python apps2.0.0.1 (2022-09-06)[IMP] set_pybin accept filename[IMP] check_pythonpath removed2.0.0 (2022-08-10)[REF] Partial refactoring for shell scriptsCreditsCopyrightSHS-AV s.r.l. <https://www.shs-av.com/>AuthorsSHS-AV s.r.l.ContributorsAntonio M.Vigliotti
Package: z2n-periodogram
Z2n PeriodogramA package for interative periodograms analysis!Explore the docs »View Demo·Report Bug·Request FeatureTable of ContentsAbout the ProjectBuilt WithGetting StartedPrerequisitesInstallationUsageRoadmapContributingLicenseAbout The ProjectThe Z2n Software was developed by Yohan Alexander as a research project, funded by the CNPq Institution, and it is a Open Source initiative. The program allows the user to calculate periodograms using the Z2n statistics a la Buccheri et al. 1983, which is defined as follows.The standard Z2n statistics calculates the phase of each photon and the sinusoidal functions above for each photon. Be advised that this is very computationally expensive if the number of photons is high, since the algorithm grows at a exponential rate.Built WithThe Z2n Software was built using thePythonopen source language.PythonGetting StartedPrerequisitesThe version of thePythoninterpreter used during the development was the3.7, which can be managed in virtual environments such asAnaconda. Therefore, try to use the same or above versions for the best compatibility.Python>=3.7PIPInstallationThe software is currently hosted at the Python central repositoryPyPI,  to install the software properly use the terminal command:pipinstallz2n-periodogramUsageTo start the software just typez2non the terminal (check if you're under the virtual environment that it is installed).z2nTheCLIof the software is very interactive and it works by triggering the commands available, for more information on the usage typehelp.Z2nSoftware,apackageforinteractiveperiodogramsanalysis.Copyright(C)2020,andMITLicense,byYohanAlexander[UFS].Type"help"formoreinformationor"docs"fordocumentation.(z2n)>>>helpDocumentedcommands(typehelp<topic>):========================================docsgaussplotrunsave

Undocumentedcommands:======================exithelpquit(z2n)>>>For more examples, please refer to theDocumentationRoadmapSee theopen issuesfor a list of proposed features (and known issues).ContributingContributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make aregreatly appreciated.Fork the ProjectCreate your Feature Branch (git checkout -b feature/AmazingFeature)Commit your Changes (git commit -m 'Add some AmazingFeature')Push to the Branch (git push origin feature/AmazingFeature)Open a Pull RequestLicenseAll content © 2020 Yohan Alexander. Distributed under the MIT License. SeeLICENSEfor more information.
Package: z2pack
Z2Pack is a tool that computes topological invariants and illustrates non-trivial features of Berry curvature. It works as a post-processing tool with all major first-principles codes (z2pack.fp), as well as with tight-binding models (z2pack.tb) and explicit Hamiltonian matrices – such as the ones obtained from a k.p model (z2pack.hm).It tracks the charge centers of hybrid Wannier functions - as describedhere- to calculate these topological invariants.The Wannier charge centers are computed from overlap matrices that are obtained either directly (for tb) or via the Wannier90 code package (fp).Documentation:
Package: z3c.appconfig
IntroductionThis package provides a method to configure an application via standard.inifiles. This is convenient for site admins since they are more
likely to be familiar with ini files than with ZCML.Creating config filesThere are two ways to tell a Zope instance which configuration files to
load: zcml statements and the APPCONFIG environment variable. zcml statements
are processed first, making it possible to override standard configuration.The zcml syntax looks like this:<configure xmlns="http://namespaces.zope.org/zope">
  <include package="z3c.appconfig" file="meta.zcml"/>
  <appconfig file="default.ini" />
</configure>This will load the contents ofdefault.iniand merge it into the
application configuration.If an APPCONFIG environment variable is set and points to a file
its contents will be merged into the application configuration. This is done
last, allowing you to override application defined defaults. For example:$ APPCONFIG=etc/mysite.ini bin/instance fgAccessing configurationThe configuration data can be accessed from your code via a IAppConfig utility.
This utility is essentially a standard python dictionary which stores all
configuration data. For example lets use a very simple configuration file:[site]
title = My lovely siteYou can access the title from python with code like this:from zope.component import getUtility
from z3c.appconfig.interfaces import IAppConfig

appconfig=getUtility(IAppConfig)
print "Site title is: %s" % appconfig["site"]["title"]Utility methodsAs a convenience a utility method is provided to convert values from a
configuration file to booleans: thez3c.appconfig.utils.asBoolmethod:from z3c.appconfig.utils import asBool
print "Pants are on: %s" % asBool("true")Changelog1.0 (2011-01-24)Add more trove classifiers.
[wichert]Add aasBoolutility method.
[wichert]1.0b1 (2010-05-17)Initial release.
[wichert]
Package: z3c.boston
Introduction============This skin is a derivative of the zope.app.boston.Boston skin, whichsupports pagelets, forms and javascript forms.Usage:It includes the information needed to configure itself. To add itto your configuration;1.  Add it to your buildout...eggs=...z3c.boston2.  To use the skin, you can use a traversal adapter:http://localhost:8080/++skin++z3c_boston/index.html3.  To configure this as your default skin, add this line to yoursite.zcml file:&lt;includeOverrides package="z3c.boston" file="default_skin.zcml" /&gt;Changelog=========1.0.1dev - Unreleased----------------* Initial release
Package: z3c.celery
z3c.celeryIntegration of Celery 4 with Zope 3.This package is compatible with Python version 2.7, 3.6 and 3.7.Online documentation:http://z3ccelery.rtfd.io/PyPI page:https://pypi.org/project/z3c.celery/Issues:https://github.com/ZeitOnline/z3c.celery/issuesSource code:https://github.com/ZeitOnline/z3c.celeryCurrent change log:https://raw.githubusercontent.com/ZeitOnline/z3c.celery/master/CHANGES.rstChange log for z3c.celery1.6.0 (2022-06-23)Update to celery 5.x, drop Python-2 support1.5.0 (2021-11-15)Provide JsonFormatter if python-json-logger is installed1.4.3 (2021-02-26)Fix logging setup1.4.2 (2019-12-12)Make HandleAfterAbort compatible with celery-4.1.1 serialization changes1.4.1 (2019-11-15)Annotate transaction with principal and task name, like zope.app.publication1.4.0 (2019-10-30)Set the URL of the (fake) zope request (which is used to set the principal) to
the task name1.3.0 (2019-05-22)Added support for Python 3.6 and 3.7.1.2.3 (2018-06-28)Add logging for task retry.1.2.2 (2018-03-23)Ensure ZODB connection can be closed, even if execution is aborted in the
middle of a transaction1.2.1 (2018-02-02)Add bw-compat for persisted tasks that still have a_task_id_parameter1.2.0 (2018-01-23)Support task retry1.1.0 (2017-10-11)Make worker process boot timeout configurable1.0.2 (2017-10-05)Also apply “always endInteration” to HandleAfterAbortAlso apply “retry on ConflictError” to HandleAfterAbort1.0.1 (2017-10-04)Always call endInteraction, even on error during commit or abort,
so we don’t pollute the interaction state for the next task run1.0 (2017-09-29)IntroduceAbortcontrol flow exceptionAllow overriding the principal id the job runs asSupport reading configuration from a filesystem-based (non-importable) python fileDon’t use celery’s deprecated default app mechanismSupport running an actual “celery worker” with the single-process “solo” worker_pool0.1 (2017-02-21)Initial release. Extract from zeit.cms.
Package: z3c.contents
This package provides a contents.html page replacement for Zope3 based on
z3c.form and z3c.table.CHANGES1.0.0 (2015-11-09)Standardize namespace __init__Remove some deprecated ftest dependencies.Claim support for Python 3.41.0.0a2 (2013-02-28)AdjustMANIFEST.into include all templates as well.1.0.0a1 (2013-02-27)Added support for Python 3.3.0.6.0 (2009-11-29)adjust imports, reflect changes in zope packagesFix error in the template whenallowSearchattribute of
the view is set to False and there’s no search form.0.5.0 (2008-04-13)Refactored the search implementation. Now it’s very easy to customize the
search. The offered z3c.table.interfaces.IValue adapter based search allows
us to implement any kind of search patters for any context and table
combination.Merged search branch back to trunkInitial Release
Package: z3c.datagenerator
This package provides a useful set of data generators that can be used in awide variety of applications, like testing and sample data generation.Those generators are extensions to the ones provided in ``z3c.sampledata``.See ``src/z3c/datagenerator/README.txt`` for usage documentation.=======CHANGES=======2.1.1 (2014-04-07)------------------- Bug: FileDataGenerator used the full filename to generate the random seed.That is definitely going to break consistency/tests on someone else's system.2.1.0 (2013-03-15)------------------- Switched code base to use ``random2``, so that Python 2 and 3 have the sameoutput. No need for running different test files now.- Simplified and unified test setup.2.0.1 (2013-02-12)------------------- Updated manifest to include buildout and tox configuration files.- Updated Trove classifiers.- Renamed text files from *.txt to *.rst,s o Github renders them nicely.2.0.0 (2013-02-06)------------------- Feature: Support for Python 3.- Bug: Make sure that all files are closed properly.- Bug: When generating a username, make sure it does not include any specialcharacters passed through by the first or lastname, for example "O'Dorothy".1.0.0 (2013-02-06)------------------- Feature: Added tests for all data generators.- Feature: Added an ID data generator that can generate all sorts of IDs thatcould occur in systems.- Feature: To properly support Windows, ``consistent_hash()`` returns aninteger.- Bug: The IPv4 generator ignored the seed making the generator "unstable".0.0.3 (2008-12-03)------------------- Refined the seed generation further: zlib.crc32() in 32 bit Python cangenerate negative hashes, while 64 bit Python does not.  Enforcedpositive hashes.- Began a test suite.0.0.2 (2008-12-02)------------------- Use the crc32 function to hash random seeds so that thesame random sequences are generated on both 32 bit and 64 bitbuilds of Python.0.0.1 (2008-02-14)------------------- Initial Release
Package: z3c.dav
======WebDAV======The *z3c.dav* package is an implementation of the WebDAV protocol for Zope3.*z3c.dav* supports the *zope.app.folder* content type, within the scope of thecore RFC2518 protocol. *z3c.dav* also contains a number of components thathelp developers support WebDAV in their application. These components includethe ability to handle WebDAV specific errors, to generate multi-statusresponses, and an implementation of all core WebDAV methods exist that usezope component to lookup specific adapters that perform the required action.For example locking parses the request and then looks up a IDAVLockmanageradapter to perform the locking and unlocking of objects. But if the requiredadapter does not exist then a `405 Method Not Allowed` response is returnedto the client.Add-on packages exist to support other standard Zope3 content types andservices. These include:* z3c.davapp.zopeappfileDefines a common WebDAV data model for zope.app.file.file.File, andzope.app.file.file.Image content objects.* z3c.davapp.zopefileDefines a common WebDAV data model for zope.file.file.File content objects.* z3c.davapp.zopelockingImplements wrappers around the zope.locking utility to integrate withz3c.dav.Each of these packages uses an other Zope3 package to provide the underlyingfunctionality.==================Changes in z3c.dav==================1.0b2=====- Be more pedantic in parsing `IF' conditional header. Raise `BadRequest'exception when no conditions are present in the header. Handle conditionwhen there are no state tokens known by the system, here the conditionalrequest should fail.- Improved the handling of `Unauthorized' and `Forbidden' errors during theprocessing of `PROPFIND' requests. Basically we return a `Unauthorized'response requesting the user to log-in when the problem occurs on therequested resource otherwise we render the problem into the `multistatus'response. In the case where we aren't allowed to list a folder we ignorethe contents, unless it is the requested resource.- Register views for the `zope.security.interfaces.Forbidden' exceptions.- Remove all the deprecation warnings.1.0b1=====- Fix bug in COPY / MOVE methods when the destination URL contained quotedcharacters - https://bugs.launchpad.net/z3c.dav/+bug/163150- MKCOL and PROPFIND methods needed to expect a string as a value for thecontent-length header - https://bugs.launchpad.net/z3c.dav/+bug/1631530.9.1=====- Stricter property validation- Some servers pass the `Content-Length` header value as a string
Package: z3c.deadlockdebugger
OverviewThe z3c.deadlockdebugger package provides a thread debugger.Usage:/debug_threads(requires the ‘zope.ManageApplication’ permission)Caution: You should not use this package in production.CreditsThis package was put together by Malthe Borch <mborch@gmail.com>. It’s
based on the Zope 2 productDeadlockDebuggerwritten by Florent
Guillaume.Changelog0.2 (2009-11-28)Added conditional import of BrowserView for compatibility with Zope 2.9.
[davisagli]Added ability to report request path from the Zope 3 publisher.
[Tiberiu Ichim, malthe]0.1 (2008-02-14)Initial release.
[malthe]
Package: z3c.discriminator
Overviewz3c.discriminator provides a formalism for marking adapter specifications as
discriminators in the sense that they will be used only for adapter lookup,
not instantiation.Using z3c.discriminatorTo mark one or more interfaces as discriminators in aprovideAdaptercall,
simply wrap your interface with thediscriminatormethod:>>> from z3c.discriminator import discriminator
>>> provideAdapter(MyAdapter, (IFoo, discriminator(IBar)))To do the same in a Zope configuration file, prefix your dotted path with a
dash like so:<adapter for=”IFoo -IBar” factory=”some.package.YourFactory” />Note that any interface in the declaration can be made a discriminator; they
need not come in any particular order.In your factory definition, simply require only the arguments that correspond
to non-discriminator specifications, e.g.class GetsOnlyFoo(object):def __init__(self, foo):…-or-def gets_only_bar(bar):…ChangelogVersion 0.2  - November 26, 2007Discriminator machinery is now introduced globally by patching the global
adapter registry and the GlobalObject configuration field.Thediscriminatormethod now returns an interface that is in all
aspects equal to the discriminated interface except it’s marked as a
discriminator.Test suite have been expanded by including the entire test suite fromzope.component.
[malthe]Version 0.1  - November 23, 2007First public release
[malthe]
Package: z3c.etree
z3c.etreez3c.etreeprovides some mechanisms (a common interface) for integrating any
ElementTree engine with the Zope component architecture. This allows
applications to look up a engine against this interface. As such this package
does not implement the ElementTree API.z3c.etreealso provides a set of utilities that can be used to make
testing XML output in doctests easier. This functionality can also be called
from a python based unit test via theassertXMLEqualmethod.Developers>>> import z3c.etree
>>> import z3c.etree.testing
>>> engine = z3c.etree.testing.etreeSetup()Here are some examples for how to usez3c.etreewith your own code.To generate a Element object with the tagDAV:getcontenttypeall we have
to do is:>>> etree = z3c.etree.getEngine()
>>> elem = etree.Element("{DAV:}getcontenttype")
>>> elem #doctest:+ELLIPSIS
<Element ...>
>>> z3c.etree.testing.assertXMLEqual(etree.tostring(elem), """
...    <getcontenttype xmlns="DAV:"/>""")Now to add a value this element use just use theelemvariable has the API
suggests.>>> elem.text = "text/plain"
>>> z3c.etree.testing.assertXMLEqual(etree.tostring(elem), """
...    <getcontenttype xmlns="DAV:">text/plain</getcontenttype>""")Tear-down>>> z3c.etree.testing.etreeTearDown()Changes in z3c.etree0.9.2Bug: Fix Python 2.5 support.Bug: Declared z3c as a namespace.Implemented a way of comparing two XML fragments while ignoring the
ordering of elements at the same level.Allow the use of NORMALIZE_WHITESPACE with tag contents.0.9.1fix bug in getting access to the elementree engine0.9Start registering the elmenttree modules directly instead of using some
proxy objects.
Package: z3c.evalexception
z3c.evalexceptionprovides two WSGI middlewares for debugging web
applications running on thezope.publisherobject publishing
framework (e.g. Zope 3).  Both middlewares will intercept an exception
thrown by the application and provide means for debugging.Interactive AJAX debuggerz3c.evalexception.ZopeEvalExceptionlets you interactively debug
exceptions from a browser.  It is a small wrapper around theEvalExceptionmiddleware frompaste.evalexception.  You can
easily refer to it in a PasteDeploy-style configuration file using theajaxentry-point:[filter-app:main]
use = egg:z3c.evalexception#ajax
next = zope

[app:zope]
use = egg:YourApp

[server:main]
use = egg:Paste#http
host = 127.0.0.1
port = 8080Post-mortem pdbz3c.evalexception.PostMortemDebuginvokes pdb’s post-mortem mode
when the application has thrown an exception.  You can refer to it in
a PasteDeploy-style configuration file using thepdbentry-point:[filter-app:main]
use = egg:z3c.evalexception#pdb
next = zope

[app:zope]
use = egg:YourApp

[server:main]
use = egg:Paste#http
host = 127.0.0.1
port = 8080Changes4.0 (2023-12-18)Add support for Python 3.10, 3.11.Drop support for Python 2.7, 3.5, 3.6.3.0 (2021-02-10)Add support for Python 3.5, 3.6, 3.7, 3.8 and 3.9.2.0 (2007-08-23)Add thePostMortemDebug(pdb) middleware.1.0 (2007-06-02)Initial release, featuring the Zope 3-compatible interactive AJAX
debugger from Paste.
Package: z3c.formjsdemo
This package is going to show off the different features of the``z3c.formjs`` package.Install-------To start up the demo, you have to do a few setup steps.$ python bootstrap.py$ ./bin/buildout -Nv$ ./bin/demo fgAnd that's it!=======CHANGES=======Version 0.3.1 (2008-08-26)--------------------------- Restructure: Made links on index page relative to context so you can dobetter virtual hosting.- Restructure: Changed dates to ISO-8601 format.- Restructure: Removed deprecations warnings for ``ISession`` and``ZopeSecurityPlicy``.Version 0.3.0 (2007-10-03)--------------------------- Feature: Tree Editor demo shows solution to having inline formssubmitted via ajax and shows off server to client event propagation.- Feature: Widget Switching demo.  Shows off ajax switching betweendisplay and input widgets.Version 0.2.0 (2007-07-18)-------------------------- Feature: The new chatroom demo implements a simple chat client in HTML andJavascript using the ``z3c.formjs`` package.- Feature: Validation demo showing off on the fly ajax field validation.- Restructure: Code updated to keep up with the changes in the API of``z3c.formjs``.Version 0.1.0 (2007-06-29)-------------------------- Initial Release* Javascript field event demo.* Javascript implementation of the calculator.
Package: z3cform.locationwidget
Widget for graphically select location in to a map, and save cordinates into field
Based in gmaps.js libraryFeaturesGmaps libraryApi Key Google maps definition in control panelCoordinates default point definition in control panelYou can show de coordinates field via checkboxUsageYou need to set the widget to needed fields into your form instance:from z3cform.locationwidget.field import LocationField
from plone.supermodel import model


class IMyModel(model.Schema):
   my_location_field = LocationField(
       title=_(u'Map Location'),
       description=_(u'Set the location mark on the map'),
       required=False,
   )TranslationsThis product has been translated intoCatalanSpanishFrenchInstallationInstall z3cform.locationwidget by adding it to your buildout:[buildout]

...

eggs =
    z3cform.locationwidgetand then runningbin/buildoutContributorsaormazabal,aormazabal@tda.adChangelog1.1.0 (released)Initial release