Saravanan666/pypi-org huggingface dataset:
Package: collective.zestreleaser.aftercheckoutaction
ContentsIntroductionExampleContributorsChangelogIntroductioncollective.zestreleaser.aftercheckoutaction allows to execute any
shell action after a clean tag checkout has been done. The command
is executed in the context of hte checkout directory.
Some variables in the command string can be substituted:name
The package nameversion
The package version of the checkoutCommands can be written into ~/.pypirc, the section name must be
collective.zestreleaser.aftercheckoutaction.
The variable name is used to match the action against a package.
For each variable, this plugin compares the package name against
the variable name. If the variable name matches the beginning
of the package name, the action is executed. If multiple variable
name match, the longest variable name wins.cza is a bit similar to gocept.zestreleaser.customupload.
While gza lets you upload the finished egg to a predefined location,
cza lets you do something with the clean checkout. Cza is intended to
be used if company policy demands that each released version of company
code must be committed to a company versioning system, but where the
actual development happens somewhere else. You should NOT use this
plugin to change something in the checkout, this would result in an
egg release that has different contents than what is in the source
repositoryExampleAdd this to your local~/.pypirc:[collective.zestreleaser.aftercheckoutaction]
collective.zestreleaser.aftercheckoutaction=svn import svn+ssh://do3cc@svn.zope.org/repos/main/Sandbox/do3cc/%(name)s/tags/%(version)s -m "Automatic commit"This would execute an action for the package collective.zestreleaser.aftercheckoutaction.ContributorsWolfgang Schnerring, Christian Zagrodnickauthors of gocept.zestreleaser.customupload, which was liberally
copiedPatrick Gerkenremoved the clean parts of the originalChangelog0.1.0 (2012-09-12)Package created using templer
[]
Package: collective.zfile
collective.zfile is a package for ZODB that allows you to manage files in a distributed
way, using multiple storages.It is still under developmentIt’s main features are the following:Multiple storage managementThe idea is to support a large amount of large files, so it is possible to manage multiple file storages.Revision controlUsing zc.vault it supports revisions, similar to SCM system, revisions are seen as transactions, each transaction you make will end up as a revision in the file system.Lock supportIs is possible to lock files and folders in two ways: exclusive locks and shared locks, you can ask for any of this types of locks on any file, in a directory it can be recursive.Multiple mount pointsYou can mount a zfolder in multiple ZODB mount points, using zc.mountpoint.using zc.mountpoint.Usage:In order to use collective.zfile there are four main objects to interact with:ZStorageManagerZBaseZFile>>> from collective.zfile import ZStorageManager, ZBase
>>> import transactionYou can create a storage this way>>> storage = ZStorageManager()
>>> storage.add_storage('test_storage')
>>> app['storage'] = storageOnce you have at least one physical storage you can create a base, a base is similar to a complete filesystem.>>> base = ZBase(storage)It needs a connection to database so we save it AND commit.>>> app['base'] = base
>>> transaction.commit()We are ready to go, we can now create a new ZRevision and use get our root folder>>> revision = base.new_revision()
>>> root = revision.rootNow we are good to go! we can keep working with this revision or just save it.Let’s just save it for now>>> revision.save_revision()Let’s add a subdirectory called test>>> test = root.newdir('test')
Traceback (most recent call last):
...
FrozenErrorOops!! Error #1, we cannot modify anything after saving a revision.Lets try again>>> revision = base.new_revision()
>>> root = revision.rootRemember always to get the new root object when creating a revision>>> test = root.newdir('test')Newdir gives us a reference to the new created dir, but we could also do:>>> test = root['test']
>>> test1 = test.newdir('test1')And we can work with files as well>>> file = test1.newfile("test.txt")
>>> f = file.open("w")
>>> f.write('Hello world')
>>> f.close()And we can check it is ok!>>> file.mimetype()
'text/plain'
>>> f = file.open('r')
>>> f.read()
'Hello world'
>>> f.close()Let’s try all the process at once.>>> html = test1.newfile("index.html")
>>> f = html.open("w")
>>> f.write("<html><head><title>Test</title><body>Hello Test</body></head></html>")
>>> f.close()>>> html.mimetype()
'text/html'>>> new_file = file.renew()
>>> f = new_file.open('a')
>>> f.write('\nHello newline')
>>> f.close()>>> f = new_file.open('r')
>>> f.read()
'Hello world\nHello newline'
>>> f.close()>>> revision.save_revision()
>>> transaction.commit()TODO: Lock doctestsTODO: Implement mountpoints
Package: collective.zipfiletransport
ZipFileTransport ToolThis tool is used to import and export zip files.InstallationFor full installation instructions see the “INSTALL.txt” file.FeaturesImport of the file system objects (within zipfile) into Plone objectsExport of content objects to a zip file.Adds two action buttons (import/export) to the bottom of folder_contents view.Custom settings for creating your own created content types.RequiresPlone 3.0.0 and greaterZope 2.10.4 and greaterHow to run the tests for this egg (Unix):Plone 3Make sure you are using Python-2.4.*Check the egg trunk out into a directory:svn co https://svn.plone.org/svn/collective/collective.zipfiletransport/trunk collective.zipfiletransportDownload bootstrap.py and run it:wget http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py

python bootstrap.py -c test-plone-3.3.x.cfgRun the buildout:./bin/buildout -vc test-plone-3.3.x.cfgNow run the tests:./bin/test -s collective.zipfiletransportChangelog3.2.3Added .gitignore [blambert555]Removed KSS Support in order to provide support for Plone 4.3.2 [pbauer]Remove old overrides [encolpe]Add dexterity container support [encolpe]Use plone.app.form instead of custom based on formlib [encolpe]3.2.2fixed import deprecation warning [ajung]3.2.1fixed ZCML deprecations [ajung]Updated pot file [blambert555]Updated Spanish translations [blambert555]Updated Brazilian Porteguese translations [blambert555]3.2.0Bumped version number so that current version succeeds older test version 3.1 [blambert]2.2.3Added preference to choose between IDs or titles for filename on
export and added a control panel setting [blambert]Set ID to be the default filename so that internal links in
documents will be preserved in the ZIP export file [blambert]Added metadata.xml to track property changes in GS [blambert]Added Brazilian Portuguese translation [agnogueira]Added Plone 4.1.x compatibility [erico_andrei]Fixed export feature [kiorky]Added a way (marker interface) to hide import/export buttongs on certain contents [kiorky]2.2.2Added unit tests [jcbrand]Fixed a bug causing existing files to always be overridden [jcbrand]Added Plone 4 compatibility [jcbrand]Added default workflows for Image and File [jcbrand]Register the utility via zcml and not via an import step [jcbrand]2.2.1Minor documentation changesRepackaging; bad egg (missing docs folder)2.2.0Added German translationAdded import/export support for handling filenames/content with unicode charactersAdded folder_contents override to show import button in empty folder2.1.3Added French translation2.1.0 - UnreleasedInitial releaseContributorsBrent Lambert [blambert] <brent@enpraxis.net>David RayJon ThomasJC BrandCillian de RoisteMathieu Le Marec - Pasquet (kiorky)Encolpe Degoute (encolpe)
Package: collective.zodbbrowser
IntroductionCollective.ZodbBrowser is a web application to browse, inspect and introspect Zope’s zodb objects. It is inspired on smalltalk’s class browser and zodbbrowsers for zope3.There is a demo video available atYouTube’s menttes channel.Using ZodbBrowser with your buildoutIf you already have a buildout for Plone3 or Plone4 running, edit
buildout.cfg to add collective.zodbbrowser to eggs and zcml sections at buildout
and instance parts respectively.[buildout]
...
eggs = collective.zodbbrowser
...Autoinclude is automatically configured to work in Plone but if you are using
any other systems, make sure to add a zcml slug:...
[instance]
...
zcml = collective.zodbbrowserThen run bin/buildout to make the changes effective.Changelogcollective.zodbbrowser 0.1Changed namespace to avoid conflicts on windows plataforms. Thanks to Laurence Rowe.Added Smartfilter for Plone folders. Thanks to Elizabeth Leddy andAdded annotations listSwitch from View to ViewManagementScreens Permissions. Thanks to Elizabeth Leddy.Added alternate view that starts to filter out objects that are unlikely.
to be navigated. Thanks to Elizabeth Leddy.Rename views to not conflict with certain built in items. Thanks to Elizabeth Leddy.Render sites with broken interfaces. Thanks to Elizabeth Leddy.Bumped the jquery dynatree version, fixed missing dependencies for jq libs. Thanks to Elizabeth Leddy.Fix setup.py so that autoinclude works with plone without zcml. Thanks to Elizabeth Leddy.Make all browser views extend DoomedBrowserView, which makes sure the utility
can’t accidentally commit a transaction. Thanks to David Glick.Remove unused five:registerPackage directive and initialize method. Thanks to David Glick.zope2.zodbbrowser 0.2 experimental versionAdded ui.layout for better layout and resizable panels. Thanks to Quimera.Updated jquery from 1.4.2 to 1.4.4.Added Pretty printing format to show propertie’s values. Thanks to Laurence Rowe and Emanuel Sartor.Added support for older pythons 2.4 , 2.5. Thanks to Laurence Rowe.Included module and file path for source code. Thanks to davidjb.Added z3c.autoinclude.plugin support to remove the zcml entry on buildout. Thanks to aclark.zope2.zodbbrowser 0.1 experimental versionInitial release includes: Class and Ancestors, Properties, Callables and Interfaces provided.Support for Zope 2.13.xSupport for Firefox 3.6 and Chrome 5.0. No support Internet Explorer yet.
Package: collective.zodbdebug
OverviewTools to debug a ZODB.Provide the.core.ZODBInfoclass which is a nice interface to inspect the objects in a ZODB
and the references between them.Thescan_blobsscript scans the blobs directory and prints information about each blob.
It is registered using thezopectl.commandentry-point, so it can be invoked like this:bin/instance scan_blobs.!DANGER!Do not use in production! This project provides debugging tools only. For safety always use it
in a copy of the actual DB.InstallInstall it as an egg of a Zope instance.See alsoThis discussion:Any way to track down the content object a blobstorage asset belongs to? (RelStorage)Changelog0.0.1 (2019-07-03)First version.
Package: collective.zopeconsul
collective.zopeconsulenables asynchronous sending of zope configuration
to consul. It sends the VHM domain information to consul along
with port and ip address of this instance. It can also be used to set key/value
pairs from buildout config options or environment variables.Configurationzopeconsul can be configured by adding the following to your buildout:[instance]eggs=collective.zopeconsulzope-conf-additional=<product-config zopeconsul>consul_url http://localhost:8500consul_prefix zopeconsul_key_somename somevalue</product-config>Any configuration option can be overridden by an environment variable:$ export CONSUL_URL=http://localhost:8500$ export CONSUL_KEY_SOMENAME=somevalueConfiguration optionsconsul_urlUrl of the consul server to connect to.Default: http://localhost:8500consul_prefixWhen setting key/values, this is the base key from which all values are
set.Default: zopeconsul_instancenameGives a name to the instance. Instead of values being placed in<consul_prefix>, they are placed in<consul_prefix>/instances/<instance_name>on the consul server. Useful when there are multiple instances being orchestrated from consul.Default: unsetconsul_key_[name]Allows to set arbitrary key values with any name.Example: ``consul_key_somekey = somevalue``consul_ignoreSkips setting consul key values. Useful if you have multiple instances that
share the same code. You can set this value on specific instances and no
key/values will be set in consul.Changelog0.2 (2021-09-16)Add Python3 compatibility [instification]0.1 (2018-02-01)Initial setup and vhm monkeypatching [djay]Addition of zope-additional-configuration option [instification]Addition of key/value pairs to consul [instification]
Package: collectlicense
collect-licensepipインストールされたパッケージのライセンスファイルを収集するモジュールです。
pip-licensesを使用します。動作確認OSWindows 11 Proインストール方法pip install collectlicense実行方法python -m collectlicense --out .licenses --clear--out：収集したライセンスファイルの保存先ディレクトリ--clear：--outで指定したディレクトリを削除してから収集するソースから実行する方法git clone https://github.com/hamacom2004jp/collect-license.git
cd collect-license
python -m venv .venv
.venv\Scripts\activate
python.exe -m pip install --upgrade pip
pip install -r requirements.txt
python -m collectlicense
deactivatepyplにアップするための準備python setup.py sdist
python setup.py bdist_wheelpyplのユーザー登録【本番】https://pypi.org/account/register/pyplのユーザー登録【テスト】https://test.pypi.org/account/register/それぞれ2要素認証とAPIトークンを登録ホームディレクトリに.pypircを作成[distutils]
index-servers =
  pypi
  testpypi

[pypi]
repository: https://upload.pypi.org/legacy/
username: __token__
password: 本番環境のAPIトークン

[testpypi]
repository: https://test.pypi.org/legacy/
username: __token__
password: テスト環境のAPIトークンテスト環境にアップロード.pyplrcを作っていない場合はコマンド実行時にusernameとpasswordを要求される
成功するとURLが返ってくる。twine upload --repository testpypi dist/*pipコマンドのテストpip install -i https://test.pypi.org/simple/ collectlicense本番環境にアップロードtwine upload --repository pypi dist/*
Package: collector-mq-queue
#+TITLE: RabbitMQ data managerProvee una clase para enviar/leer datos utilizando una cola AMQP derabbitMQ.Primero instalar *poetry*#+begin_src bashpip install poetry#+end_srcLuego instalar el módulo, debería instalar las dependencias.#+begin_src bashpoetry buildpoetry install#+end_src
Package: collector-ring-buffer
Este módulo entrega un objeto de tipo ringbuffer para
controlar una ventana de tiempo de un stream de datos en el parámetro de la latencia, es decir la diferencia de tiempo en que se genera el dato y se recibe.Se instala en modo de desarrollopipinstall-e.En modo producciónpipinstall.Para correr los test.python3 -m unittest discover tests
Package: collectors-channel-cli
collectors-channel-cliBuilt with ❤️ usingTyperHow to use itCreate a properties file at$HOME/.collectors/my.propertiesusing this as an example:# MongoDB
MONGO_URL=mongodb+srv://user:password@url/databaseOr pass--propsto the CLI with the file location.Check out the project at GitLab:https://gitlab.com/collectors-channel.
Package: collect-pack
# Collect_framework
### Installation
To use in your project just use your dependency manager to install it, with pip is like this:pip install collect-pkg### Short explanation
Program takes string or file(high priority if string too transferred) and return amount and characters which ar uniquecall it from command line with this commandpython -m collect_pack –string <your string> –file <your file>The package has 4 functions
- amount_of_unique_chartakes string and return tuple amount of unique char in input string and list with them
- format_returnformat the result of previous func
- cliadd two arguments –file and –string and return parser with them
- work_with_argsparse arguments from command line and detect a priority if hand over two arguments### How it works :new_moon_with_face:
Here a some examples` from collect_pack import amount_of_unique_charprint(amount_of_unique_char('qwerrr'))# result(3,['q','w','e'])`` from collect_pack import format_return, amount_of_unique_charprint(format_return('qwerrr'))# before format format the result it call amount_of_unique_char in his body """ result "qwerrr" => 3 q,w,e are present once. """ `` from collect_pack import work_with_argsprint(work_with_args(file="",string="qwerr"))# result 'qwerr'print(work_with_args(file="text.txt",string="qwerr"))# result 'text from file like one string ' argument file has a higher priority `
Package: collectr
More and more, we find ourselves storing our static website files - CSS,
Javascript, images and more - onAmazon S3. Some
of us do it because we use services likeHerokuand
don’t want to force the static files through our web dynos. Others of us do it
to avoid huge bandwidth costs associated with hosting these on our own servers.
Still others do it to take advantage of the scale and distributed nature of S3.However, managing our S3 files can be a pain. Each time we change them we have
to minify and reupload them. We also need to set all the metadata we want:
things like Cache-Control headers. This can be boring and error-prone. collectr
aims to help with that.Using collectrcollectr is a collection of functions built on top of thebotolibrary. This allows you to plug
collectr into any of your Python code however you see fit. For those who want a
‘just works’ solution, however, collectr also comes with an example script that
is perfect for using with any Django project.If you want simple, you can use collectr like this:import collectr
collectr.update('path/to/static/files', 'bucket-name')collectr will scan the directory, minify anything that can be minified using
whatever tools you have on your system, and upload all your files to the
specified S3 bucket. Anything that already existed on S3 will have all of its
metadata persisted.Of course, you can have quite a bit more control than that.import collectr
statics = collectr.StaticDir('path/to/static/files')
statics.input_directory = 'path/to/other/dir'
statics.minifier = 'yuicompressor -o {out_name} {in_name}'
statics.force_update = True
statics.ignore = ['.*\.jpg', '.*\.json']
statics.metadata = {'Cache-Control': 'max-age=3600'}
statics.update('bucket-name')Before you do anything, though, make sure you have your environment variables
set up. You’ll need AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY set to
the correct values.FeaturesStatic file minification.Ignore filters.Multiple directory management.Metadata management.InstallationTo install collectr:$ pip install collectrIf you don’t havepipand can’t install it, you should complain to your
sysadmin, and then do:$ easy_install collectrContributingcollectr welcomes contributions, both bug fixes and new features. Any feature
request should strongly consider the implications for the API. API clarity
is valued above new features, so any feature that complicates the API must add
significant value to the library to be accepted.If you want to contribute, do the following:Check that your idea hasn’t already been proposed. Check both openand
closedissues on GitHub.Fork the repository on GitHub and make your changes.Where possible, write a test that can reproduce the bug, or that will test
the new feature.Send a Pull Request. Don’t forget to add yourself to the AUTHORS file.History0.0.5 (2013-03-07)More detailed metadata handling.Only update if needed or forced.0.0.4 (2013-03-03)Fix key names including the whole path.Add groundwork for defaulting the minifier dict.The update() helper method now takes an optional input directory.Add an example collect_static script.Sets the S3 ACL to allow public read access.
Package: collectstupid
# Collect Stupid - A Faster, Smarter, and Stupider Collect Static for DjangoWhen usingcollectstaticwith remote file systems like Amazon S3 it can often
slow down because up to 3 remote operations are needed for each file.Determine file time stampDelete file if oldCopy the new filecollectstupid speeds up your static file deploy with two tricksThe Stupid One: Never checks remote file timestamps and never deletes the
old file. It just overwrites the file blindly. This saves two remote
operations.The Smart One: Stores a list of deployed file md5sums on the remote file
system. This keeps track of what files need to be deployed and md5sums are
only computed at the source for speed. This can be faster than other
collectstatic libraries which a lot of times use local cache and thus other
developers don’t benefit from the last deploy. Also the deployment tracking
is more permanent and not subject to cache clearing unless you explicitly
need to clear it.## Installation and Usagepip install collectstupidAddcollectstupidtoINSTALLED_APPSRun:python manage.py collectstupid## Storage MixinSome storage implementations execute anexistsanddeleteon the storage
class even when usingcollectstupid. You can add thecollectstupid.storage.StupidStorageMixinto your storage class to skip
those requests.## Personal Example Where CollectStupid Improved Deployment SpeedFor a project, whenever we deployed, a huge amount of memory (+13GB) was used
and the whole process took more than 30 minutes on a fast Mac and over 2 hours
on a virtual machine. Through investigation, we found that every check of
whether a file existed caused the bucket to do a full file list because of a
very inefficient S3 storage implementation. We implementedcollectstupidand
after the initial deploy of large files, subsequent deploys went down to less
than 5 minutes. This also cut down memory usage to almost nothing when compared
to 13GB.## SettingsSTUPID_DEPLOY_CACHE: File where md5sums are stored on the remote filesystemDefault: collectstupid-cache.json## Feature requestsFeel free to open an issue
Package: collect-unexported
Collect files omitted from the release tarballs[Home|GitLab|PyPI]OverviewSome projects explicitly exclude some development files from
their release tarballs.
Sometimes, when packaging those projects, it may be useful to have
these files around, e.g. for running tests.Thecollect-unexportedutility examines the control files within
a Debian source package, clones its upstream repository, and then
creates an additional source file archive containing some of
the files that have explicitly been omitted from the upstream archive.
This allows a Debian package to e.g. run some source tests that use
scripts and data files that the upstream authors exclude from
the distributed source archive.
Thecollect-unexportedtool creates an additional (component) original
tarball (.orig-unexported.tar.gz) and places it in the directory where
the Debian packaging tools expect to find the original source tarball
(the.orig.tar.gzone).Please note that thecollect-unexportedtool is limited in
its functionality; it is meant to handle several specific cases, and
it may fail in others.ExamplesUse thecollect-unexported.tomlfile in the current directory,
create an additional source tarball, display some diagnostic information
in the process:collect-unexported-vUse a file with a different name, do not overwrite the source tarball:collect-unexported-cunexported.toml-NThe configuration fileTo figure out which files it needs to repack from the upstream repository,
thecollect-unexportedtool reads a TOML file,collect-unexported.tomlby default.
That file must currently contain two sections:[format.version]: a table containing two fields,majorandminor,
describing the format of the configuration file itself.
The only version currently supported version is "0.1".[files]: a table that describes the files that need to be included:include: a list of strings, each specifying the relative path from
the top of the source repository to a single file or directory to be
included in the component archiveNote that all the paths specified in thefiles.includelist must be
excluded in the upstream project's.gitattributesfile using
theexport-ignoreattribute.An example configuration file for packing the contents of thetestsandtest_datasubdirectories may look like this:[format.version]major=0minor=1[files]include=["test_data","tests",]ContactThecollect-unexportedtool is developed ina GitLab repositoryand is hostedat Ringlet.
A Python package may be downloaded fromthe Python package index.The author, Peter Pentchev, may be contactedvia e-mail.