Saravanan666/pypi-org huggingface dataset:
Package: ztfy.sendit
ContentsIntroductionHISTORY0.1.200.1.190.1.180.1.170.1.160.1.150.1.140.1.130.1.120.1.110.1.100.1.90.1.80.1.70.1.60.1.50.1.40.1.30.1.20.1.10.1.0Introductionztfy.sendit is a small package which provides an application which authenticated users can
use to send files to remote contacts, like in SendIt web site.It’s main use case is for principals from inside an organization who want to share documents
with their remote contacts; contacts selection can be done via any registered authentication
plug-in.You can customize your application so that external users registration is opened or made only
by organization’s inner principals.Thierry Florac <tflorac@ulthar.net> - AuthorHISTORY0.1.20added packet backup time option of 8 weeks0.1.19force packet registration in outbox displayforce unicode in packet history attributes0.1.18small correction in XML-RPC API to add check on packet description0.1.17added views to allow registered users to receive a new profile activation messageadded minified resources0.1.16make user login case insensitive0.1.15added “trusted_redirects” attribute in security configuration interface to allow usage of
application behind an application firewall using another protocol (HTTP / HTTPS)0.1.14use all file content instead of 4Kb sample to extract MIME type to prevent
errors when checking MS-Office files0.1.13use (I)I18nBaseContent classes from “ztfy.i18n” packageadd tests to correctly handle admin account in dev-mode0.1.12user new “getMagicContentType()” function from ztfy.extfile package0.1.11add missing permissions to application administrator role0.1.10use unicode when defining default user’s profile company name0.1.9use last ZTFY.base and ZTFY.skin interfaces and classes0.1.8added new ztfy.appskin IApplicationResources interface adapter0.1.7french translation update0.1.6corrected handling of non-unicode inputs in XML-RPC servicescorrected display condition of dashboard legendremoved unnecessary output from scheduler tasks0.1.5added XML-RPC services with client module0.1.4apply empty string instead of null value in principals description to allow
plug-ins search methods to operate without errorupdated quota usage progress indicator image for quota usage greater than 100%0.1.3removed unneeded check about “open registration” setting in registration
confirmation formadded quota usage gauge in dashboard and outboxadded external users domain name in recipients search widgetsmall change in packet reject messagecorrectly handle null values in MIME type filter plug-in0.1.2updated login form to prevent storage of bad credentials in session0.1.1modifications in login formCSS classes updates0.1.0first release
Package: ztfy.sequence
ContentsIntroductionSequence utilityContributorsChangelog0.1.10.1.0IntroductionZTFY.sequence is a small package used to set sequential identifiers on selected persistent
contents.The SequentialIntIds utility is based on zope.intid.IntIds utility, but overrides a few methods
to be able to define these sequential IDs.Classes for which we want to get these sequential IDs have to implement the ISequentialIntIdTarget
marker interface. They can also implement two attributes, which allows to define the name of
the sequence to use and a prefix.This prefix, which can also be defined on the utility, is used to define an ID in hexadecimal
form, as for example ‘LIB-IMG-000012ae7c’, based on the ‘main’ numeric ID.Sequence utilitySequences are handled by a utility implementing ISequentialIntIds interface and registered for
that interface.You can set two optional parameters on this utility, to define the first hexadecimal ID prefix
as well as the length of hexadecimal ID (not including prefix).ContributorsThierry Florac <tflorac@ulthar.net>, AuthorChangelog0.1.1force unicode on hexadecimal OID valueadded TAL “sequence:” namespace package0.1.0package created using templer
[Thierry Florac]
Package: ztfy.workflow
ContentsWhat is ztfy.workflow ?How to use ztfy.workflow ?Changelog0.2.90.2.80.2.70.2.60.2.50.2.40.2.30.2.20.2.10.20.1.10.1.0What is ztfy.workflow ?ztfy.workflow is an extension to hurry.workflow package. It provides a small set of
base content classes, utilities and viewlets to handle basic workflow management.How to use ztfy.workflow ?See doctests in ztfy/workflow/doctests/README.txt to have a full description of ztfy.workflow usage.Changelog0.2.9move default “workflow.manager” viewlets manager to ZTFY.skin package to remove unneeded dependency
with ZTFY.workflow0.2.8updated translation0.2.7added “:published” and “:visible” to “wf:” TALES path adaptersadded “wf_name” index in WorfklowCatalogmodify “++wf++” namespace so that when an InvalidTransactionError is raised, we look
for a registered error view before raising a TraversalError0.2.6changed package source layout0.2.5removed unused package dependency0.2.4changed ISite interface import in database upgrade code0.2.3updated database automatic upgrade code0.2.2updated database automatic upgrade code0.2.1remove “zope.app” package dependencies0.2switched to ZTK-1.1.2 and hurry.workflow-0.11add ITransition interface to transitionsadd ITransitionTarget interface to handle transitions viewlet links0.1.1update database upgrade code used when creating a site manager0.1.0initial release
Package: ztfy.zmi
ContentsWhat is ztfy.zmi ?How to use ztfy.zmi ?Changelog0.3.10.3.00.2.110.2.100.2.90.2.80.2.70.2.60.2.50.2.40.2.30.2.20.2.10.20.1.20.1.10.1What is ztfy.zmi ?ztfy.zmi is a small package which just provides a new skin called ZMI.
This skin is done to include standard ZMI views with ZTFY.blog management skin.How to use ztfy.zmi ?This skin is mainly done for site-level management tasks, such as handling
site-level utilities ; so it’s mainly targeted to site system administrators.Changelog0.3.1strange bug workaround where a translated string can’t be integrated into template… :-(0.3.0use ZTFY.skin data API0.2.11move login form to ZTFY.skin packageupdated forms and views templates0.2.10modified ZMI access menu to handle virtual hosts correctly0.2.9added menu to access management console from back-officeremoved useless test0.2.8modified templates to match new ZTFY.skin packageadded weight on several viewlets0.2.7changed package source layout0.2.6refactoring to follow release 0.3.0 or ztfy.skin package0.2.5changed viewlets order value0.2.4modified login form to be used as “normal” page as well as IUnauthorized
exception’s default view0.2.3modified ‘@@SelectedManagementView.html’ for redirects to work better in a
virtual host environment with custom startup script0.2.2updated ZMI breadcrumbs to facilitate navigation in site’s management folder0.2.1modified login process to allow authentication on global PrincipalRegistrymigrated resources management from zc.resourcelibrary to fanstatic0.2switch to ZTK-1.1added access to login page on IUnauthorized exception0.1.2changed breadcrumbs handling to correctly get IBreadcrumbInfo multi-adapterchanged viewlet layer to IZMILayer instead of IZTFYBlogBackLayer0.1.1fixed bug related to naming of several divs in form macros0.1initial release
Package: ztfy.zmq
ContentsIntroductionHISTORY0.1.40.1.30.1.20.1.10.1.0IntroductionZTFY.zmq is a small ZTFY integration of ZeroMQ library.It provides two main classes which are:ZMQProcess, which is a ZMQ listening process, based on multiprocessing package.ZMQMessageHandler, which is a simple ZMQ messages handler which delegates it’s functionality
to a ZMQ agnostic handling class.When creating a new ZMQProcess instance, you only have to specify it’s listening address and it’s messages
handler.Default ZMQ process is based on request/response (REQ/REP) messages, but this can easily be overriden in
custom subclasses.Most of this package main concepts are based onStefan Scherfkework. Thanks to him!Thierry Florac <tflorac@ulthar.net> - AuthorHISTORY0.1.4added “socket” module with utility functions0.1.3updated package dependenciesupdated Buildout’s bootstrap0.1.2handle TERM signal to be sure parent processes can terminate ZMQ processes0.1.1added ZMQ process exit callback function, to be registered on application
exit for any created process. This is required when using WSGI servers to
end ZMQ processes in a clean way.0.1.0first release
Package: zthreadpool
线程池, 固定指定数量的线程来执行任务, 避免重复创建和销毁线程时的资源消耗注意:如果任务数量超过线程数量, 超出的任务会等待有正在执行的任务执行完毕后, 在有空闲线程时才会执行测试代码:if __name__ == '__main__':import timeimport threadingp = ThreadPool(2)@p.task()def fun(a, c):print(a, '开始', time.strftime('  %H:%M:%S', time.localtime()))for i in range(c):time.sleep(0.01)print(a, '  结束', time.strftime('  %H:%M:%S', time.localtime()))fun('aa', 100)fun('bb', 100)fun('cc', 100)fun('dd', 100)p.close()p.join()print('--end--')
Package: ztimer
计时器池管理器作用:将多个计时器挂在到计时器管理器中, 用一个线程来统一管理, 减少资源消耗别的多线程计时器在线程切换时会造成额外资源消耗管理线程会根据在创建第一个计时器时自动启动, 关闭最后一个计时器后自动关闭注意:尽量不要调用Timer_Manager()中的close(), add_timer(), remove_timer()函数, 除非你真的完全了解这个模块在计时器回调函数中调用close(), add_timer(), remove_timer()函数会造成死锁测试代码:if __name__ == '__main__':def fun1(t: Timer):print('回调', t.meta, t.callback_count, time.strftime('  %H:%M:%S', time.localtime()))def fun_de(t: Timer):print(t.meta, '关闭')import timet1 = Timer(fun1, 1, 5, close_callback=fun_de, meta='计时器1   ')t1.start()time.sleep(0.5)t2 = Timer(fun1, 1, 2, meta='  计时器2 ')t2.start()print('等待计时器1结束')t1.join()print('结束')
Package: ztm
Fetch data from ZTM APIFeaturesFetch GPS position and append to CSV fileQuickstartInstall and run ZTM api wrapper:$ curl https://raw.githubusercontent.com/mitsuhiko/pipsi/master/get-pipsi.py | python
$ pipsi install ztm
$ ztm --apikey <APIKEY> fetch --line 150 --line 250
$ cat ztm.csvRunning TestsDoes the code actually work?:$ git clone https://github.com/wooyek/ztm.git
$ cd ztm
$ curl https://raw.githubusercontent.com/mitsuhiko/pipsi/master/get-pipsi.py | python
$ pipsi install pew
$ pew new -p python3 -a $(pwd) $(pwd | xargs basename)
$ pip install -r requirements/development.txt
$ pipsi install tox
$ toxWe recommend usingpipsifor installingpewandtoxbut a legacy approach to creating virtualenv and installing requirements should also work.
Please installrequirements/development.txtto setup virtual env for testing and development.CreditsThis package was created withCookiecutterand thewooyek/cookiecutter-pylibproject template.History0.1.0 (2019-01-01)First release on PyPI.
Package: ztm-buses
ZTM Buses PackageCurrent FeaturesThe package consists of three main functionalities:ZTMFetcherBusStatisticianVisualizerZTMFetcherTheZTMFetchermodule allows acquiring information from the Warsaw API.Import the module:fromztm_busesimportZTMFetcherInitialize with multiple API keys (may be beneficial when handling a substantial number of requests.):fetcher=ZTMFetcher(['your_apikey1','your_apikey2'])API keys can be obtained onhttps://api.um.warszawa.pl/.Fetch Bus Location:location=fetcher.fetch_bus_location()Fetch Bus Location Period:hour_location=fetcher.fetch_bus_location_period(period,"filename_to_save_json.json")Fetch Bus Stop Coordinates and Routes:fetcher.fetch_busstop_coordinates("filename_to_save_json.json")fetcher.fetch_routes("filename_to_save_json.json")For all methods, if a filename was not given, the data will be automatically saved with the date to avoid overwriting issues.Fetch Lines for Bus Stop:list_of_lines=fetcher.fetch_lines_for_busstop(bus_stop_complex_id,bus_stop_id)Fetch Whole Timetable:fetcher.read_the_whole_schedule("filename_to_save_json.json")Beware that fetching the whole timetable requires sending about 28,000 requests and may take from 20 to 50 minutes depending on the server load.BusStatisticianTheBusStatisticianmodule allows obtaining information about the speed and punctuality of buses.Import the module:fromztm_busesimportBusStatisticianInitialize:statistician=BusStatistician(bus_coordinates_file,timetable_file,routes_file,bus_stops_file)Get Speed Statistics:speed_data_frame=statistician.get_speed_statistics()Get Punctuality Statistics:punctuality_data_frame=statistician.get_punctuality_statistics()Thespeed_data_framecontains the columns: 'speed', 'lon', 'lat', 'vehicle_number', 'line_number'. Thepunctuality_data_framecontains 'Bus_num', 'Line', 'Busstop_id', 'Busstop_name', 'Lon', 'Lat', 'Arrived', 'Expected', 'Delay [min]'.Due to the complicated structure of bus routes and imperfections of the data, the punctuality data is prone to some larger errors.VisualizerTheVisualizermodule takes the dataframes from theBusStatisticianand plots them on the Warsaw map.Import the module:fromztm_busesimportVisualizerInitialize:vis=Visualizer()Heat Map of Speeds:vis.heat_map_speeds(speed_data_frame,html_file_to_save)Scatter Map of Speeds:vis.scatter_map_speeds(speed_data_frame,html_file_to_save)For speed maps output html file is optional and if not given the result
will not be savedMap of Punctuality:vis.map_punctuality(punctuality_data_frame,html_file_to_save)For punctuality map the html file is required parameterIt is worth noting that before visualizing the data, it has to be cleaned up as the API sometimes responds with nonrealistic data (time traveling, hypersonic buses).Installationpipinstallztm_buses
Package: ztools
ToolBox for Python, Easy to Use.概述ztools模块封装了使用Python语言编写的工具。工程主页:https://github.com/zoumingzhe/ztools下载地址:https://pypi.python.org/pypi/ztools法律许可: MITlicense, (C) 2018-2020ZouMingzhe<zoumingzhe@qq.com>安装通过pip命令安装ztools模块：pip install ztools如果已经安装ztools模块，可以通过pip命令更新：pip install--upgradeztools更多安装信息请查阅安装文档。工具timeout:https://github.com/zoumingzhe/ztools/blob/master/ztools/ztools/tool/timeout.py超时，提供超时判断。progressbar:https://github.com/zoumingzhe/ztools/blob/master/ztools/ztools/tool/progressbar.py进度条，提供进度条显示。plot:https://github.com/zoumingzhe/ztools/blob/master/ztools/ztools/GUI/plot.py绘图，提供基于matplotlib的绘图功能。filebase:https://github.com/zoumingzhe/ztools/blob/master/ztools/ztools/file/filebase.py文件，提供文件访问与相关操作。xls:https://github.com/zoumingzhe/ztools/blob/master/ztools/ztools/file/xls.pyExcle，提供对.xls文件访问与相关操作。MySQL:https://github.com/zoumingzhe/ztools/blob/master/ztools/ztools/db/MySQL.pyMySQL数据库，提供基于pymysql的MySQL数据库访问。文档API（应用程序接口）文档、用法和例程可查阅documentation目录下的文档。.rst后缀文件可以在任何文本编辑器中查看或者使用Sphinx转换成HTML或PDF格式例程例程存放在工程文件的examples目录下。测试单元测试存放在工程文件的test目录下。支持本项目由ZouMingzhe<zoumingzhe@qq.com> 创建并维护。为了完善ztools模块的功能，欢迎您贡献代码至:https://github.com/zoumingzhe/ztools语言简体中文English
Package: ztpserver
Quick OverviewZTPServer provides a bootstrap environment for Arista EOS based products.  ZTPserver interacts with the  ZeroTouch Provisioning (ZTP) mode of Arista EOS. The default ZTP start up mode triggers an unprovisioned Arista EOS nodes to enter a bootstrap readdy state if a valid configuration file is not already present on the internal flash storage.ZTPServer provides a number of configurable bootstrap operation workflows that extend beyond simply loading an configuration and boot image. It provides the ability to define the target node through the introduction of definitions and templates that call pre-built actions and statically defined or dynamically generated attributes. The attributes and actions can also be extended to provide custom functionality that are specific to a given implementation. ZTPServer also provides a topology validation engine with a simple syntax to express LLDP neighbor adjacencies. It is written mostly in Python and leverages standard protocols like DHCP and DHCP options for boot functions, HTTP for bi-directional transport, and XMPP and syslog for logging. Most of the files that the user interacts with are YAML based.ZTPServer FeaturesAutomated configuration file generation and applicationImage and file system validation and standardizationConnectivity validation and topology based auto-provisioningConfig and device templates with resource allocation for dynamic deploymentsZero touch replacement and upgrade capabilitiesUser extensible actionsEmail, XMPP, syslog based logging and accounting of all processesDocsZTPServer official documentationis built and hosted at (http://ReadTheDocs.org/).ContributingPlease see theCONTRIBUTING.mdfile for additional information.SupportMailing Listeosplus-dev@arista.comIRC: irc.freenode.net#aristaDependenciesServerPython 3.6 or later (https://www.python.org/downloads)routes 2.5 or later (https://pypi.python.org/pypi/Routes)webob 1.8 or later (http://webob.org/)PyYaml 6.0 or later (http://pyyaml.org/)ClientArista EOS 4.12.0 or laterLicenseBSD-3, See LICENSE file
Package: ztransforms
语言:
    🇨🇳🇺🇸«ZTransforms»是一个图像数据增强代码库基于pytorch/vision实现架构，添加albumentations后端输入图像格式：numpy ndarray数据类型：uint8通道排列顺序：rgb关键依赖版本：pytorch/vision:  c1f85d34761d86db21b6b9323102390834267c9balbumentations-team/albumentations: v0.5.2内容列表内容列表背景安装使用主要维护人员致谢参与贡献方式许可证背景PyTorch提供了官方数据增强实现：transforms。该模块基于PIL进行数据增强操作，其优缺点如下：优点：简洁清晰的数据架构简单易懂的数据处理流完善的文档介绍缺点：基于PIL后端，提供的图像增强功能有限基于PIL后端，相较于其他库的执行速度慢针对于执行速度问题，torchvision也意识到了这一点，从0.8.0开始进行了改进Prior to v0.8.0, transforms in torchvision have traditionally been PIL-centric and presented multiple limitations due to that. Now, since v0.8.0, transforms implementations are Tensor and PIL compatible and we can achieve the following new features:

transform multi-band torch tensor images (with more than 3-4 channels)
torchscript transforms together with your model for deployment
support for GPU acceleration
batched transformation such as for videos
read and decode data directly as torch tensor with torchscript support (for PNG and JPEG image formats)一方面通过新的后端Pillow-SIMD来提高PIL的执行速度；另一方面添加PyTorch后端来实现GPU加速在网上找到两个数据增强库，除了分类数据增强外还提供了检测/分割数据增强：imgaug：其实现了更多的数据增强操作；albumentations：其在不同的后端（pytorch/imgaug/opencv）中找出各自最快的增强函数（参考Benchmarking results）上述两个数据增强库均实现了类似于transforms的数据流操作方式。不过相对而言，个人还是最喜欢官方的实现和使用方式，所以新建这个代码库，基于transforms，在原有功能中添加albumentation后端实现，同时添加新的数据增强操作（如果albumentation未实现，就使用imgaug实现）安装$ pip install ztransforms使用# import torchvision.transforms as transforms
import ztransforms.cls as transforms
...
...主要维护人员zhujian -Initial work-zjykzj致谢pytorch/visionalbumentations-team/albumentationsaleju/imgaugopencv/opencv@Article{info11020125,
    AUTHOR = {Buslaev, Alexander and Iglovikov, Vladimir I. and Khvedchenya, Eugene and Parinov, Alex and Druzhinin, Mikhail and Kalinin, Alexandr A.},
    TITLE = {Albumentations: Fast and Flexible Image Augmentations},
    JOURNAL = {Information},
    VOLUME = {11},
    YEAR = {2020},
    NUMBER = {2},
    ARTICLE-NUMBER = {125},
    URL = {https://www.mdpi.com/2078-2489/11/2/125},
    ISSN = {2078-2489},
    DOI = {10.3390/info11020125}
}

@misc{imgaug,
  author = {Jung, Alexander B.
            and Wada, Kentaro
            and Crall, Jon
            and Tanaka, Satoshi
            and Graving, Jake
            and Reinders, Christoph
            and Yadav, Sarthak
            and Banerjee, Joy
            and Vecsei, Gábor
            and Kraft, Adam
            and Rui, Zheng
            and Borovec, Jirka
            and Vallentin, Christian
            and Zhydenko, Semen
            and Pfeiffer, Kilian
            and Cook, Ben
            and Fernández, Ismael
            and De Rainville, François-Michel
            and Weng, Chi-Hung
            and Ayala-Acevedo, Abner
            and Meudec, Raphael
            and Laporte, Matias
            and others},
  title = {{imgaug}},
  howpublished = {\url{https://github.com/aleju/imgaug}},
  year = {2020},
  note = {Online; accessed 01-Feb-2020}
}参与贡献方式欢迎任何人的参与！打开issue或提交合并请求。注意:GIT提交，请遵守Conventional Commits规范语义版本化，请遵守Semantic Versioning 2.0.0规范README编写，请遵守standard-readme规范许可证Apache License 2.0© 2021 zjykzj
Package: ztranslator
ztranslatorSimples tradutor de linha de comando. Você pode configurar uma combinação de teclas de atalho para que execute o ztranslator, para isso basta passar --notify como parametro de linha comando, que o ztranslator se encarrega de pegar a última entrada na área de transferência e exibir o texto traduzido em um simpático balãozinho na sua Área de Trabalho.Instalação:$pipinstallztranslatorExemplos de uso:Na linha de comando:$ztranslator--text"Hello World"--source-langen--target-langpt--source-apigoogle

$ztranslator--help$python-mtranslator--helpNo seu código python:In[1]:fromtranslatorimportTranslatorIn[2]:t=Translator(source_lang="pt",target_lang='en',source_api="google")In[3]:t.translate("Type copyright, credits or license for more information")Out[3]:'Digite copyright, créditos ou licença para mais informações'Configuração para Desenvolvimento$gitclonehttps://github.com/andreztz/ztranslator.git
$cdztranslator
$virtualenvvenv
$sourcevenv/bin/activate
$pipinstall-e.Histórico de lançamento1.0.0 - Altera interface da API e linha de comando.0.1.0 - Adiciona acesso a api do google translate via googletrans.0.0.7 - O primeiro lançamento adequado.Trabalho em andamentoAndré Santos –@ztzandre–andreztz@gmail.comhttps://github.com/andreztz/ztranslatorContribuaFork it (https://github.com/andreztz/ztranslator/fork)Create your feature branch (git checkout -b feature/fooBar)Commit your changes (git commit -am 'Add some fooBar')Push to the branch (git push origin feature/fooBar)Create a new Pull Request
Package: ztreamy
ztreamy: a framework for publishing semantic events on the Webhttp://www.ztreamy.org/ztreamy is a prototype implementation of a framework for publishing
streams of events through on the Web, built on top of the Tornado Web
server. The framework provides services that are specific to events
described with RDF, although any other kinds of events can be
transported as well.The platform provides scalability through replication: streams can be
repeated from other servers. Streams can also be aggregated and
filtered.A python library for consuming events at the client side is already
provided. For consuming events from programs written in other
languages, the client can use an HTTP client library and parse the
events itself. Support for other languages is planned to be added in
the future.This is an alpha version of the framework. There is no guarantee that
the main programming interfaces will no change in the near future.Basic documentation for installing and testing the framework is
available at:http://www.ztreamy.org/doc/This documentation is still work in progress.A thorough description and evaluation of Ztreamy has been published at
the Journal of Web Semantics. If you want to cite Ztreamy from a
research publication or report, please use the following bibliographic
reference:Jesus Arias Fisteus, Norberto Fernandez Garcia, Luis Sanchez
Fernandez, Damaris Fuentes-Lorenzo, “Ztreamy: a middleware for
publishing semantic streams on the Web”. Journal of Web Semantics
(2013).  doi:10.1016/j.websem.2013.11.002.