Saravanan666/pypi-org huggingface dataset:
Package: cs.auth.twitter
IntroductionA PAS plugin to login into a Plone Site using Twitter. Provides the following features:Log in to a Plone site through Twitter: when a user requests to log in to the Plone site he will be redirected to Twitter so that he provides the credentials there, then he will be redirected back to the Plone site and will be identified there.The user will be a standard Plone user, so Roles or Group membership can be set.Minimal user information is kept in Plone such as full name, screen-name Twitter ID and twitter photo of the user. This is kept to avoid permanent requests to Twitter API. This information is refreshed each time the user logs in to the site.Installation and getting startedAddcs.auth.twitterto your buildout.cfg’s eggs list. It will install all required dependencies.Install the product in the Plone Control Panel. This will create a “Login with
Twitter” action into the personal tools toolbar in Plone.Create a new Twitter app athttps://dev.twitter.com/apps/newand fill in the
required data in the plugin’s control panel form.CreditThis product contains code written for collective.twitter.accounts
by Franco Pellegrini (@frapell) and Hector Velarde (@hvelarde)CompatibilityPlone 4.xChangelog1.1.1 (2017-11-24)fix import [Mikel Larreategi <mlarreategi@codesyntax.com>][Mikel Larreategi <mlarreategi@codesyntax.com>][ci skip] [Mikel Larreategi <mlarreategi@codesyntax.com>]1.1 (2017-05-10)Remove Welcome message1.0.1 (2014-10-10)Fix dependencies includes
[erral]1.0 (2014-10-10)Remove roles plugin implementation
[erral]Fix user search
[erral]Fix to add the plugin through the ZMI
[erral]Use Twitter API directly to get user information
[erral]Fix Access Token Request
[erral]1.0b3 (2012-10-18)Implement IRolePlugin again to grant Member role
[erral]1.0b2 (2012/10/16)Inherit from PloneUser instead of PropertiedUser
[erral]Remove IRolesPlugin implementation
[erral]Add missing oauth2 dependency
[erral]Change user action name not to clash with Plone’s
[erral]1.0b1 (2012/07/13)Initial release
[erral]
Package: cs.autotranslate
cs.autotranslateDo you go mad when creating images and files in Plone that
you want to use through the different languages’ sites?In previous versions of Plone did you create a ‘neutral’
folder and store there your images?Forget everything!!!Just create a folder, apply AutoTranslatable interface using
Sub-Typer menu, and tadaaaaaa! All items created inside that
folder will be translated automatically to all available
languages.Only available for Archetypes based content.Changelog1.1 (2014-10-22)Docs and dependencies
[erral]1.0 (2010/12/17)Initial release
[erral]
Package: cs.behavior.footerhtmlcode
This addon adds a behavior to provide an extra field where you can write any HTML code.This HTML code will be shown in the footer viewlet. The Footer viewlet will look for the nearest Language Root Folder (/en, /de, /es, …) and will render the value of the field present there.This behavior is useful for multilingual sites where you may want to put some language-dependant javascript code editable by the end user.We are using this to provide the cookie message in several languages. We are usingCookie Consentto achieve this.InstallationInstall cs.behavior.footerhtmlcode by adding it to your buildout:[buildout]

...

eggs =
    cs.behavior.footerhtmlcodeand then runningbin/buildoutUseInstall the product in the Plone Control Panel -> Addons. The install process will enable the behavior automatically for Language Root Folders.ContributeIssue Tracker:https://github.com/codesyntax/cs.behavior.footerhtmlcode/issuesSource Code:https://github.com/codesyntax/cs.behavior.footerhtmlcodeSupportIf you are having issues, please let us know using theGitHub issue trackerLicenseThe project is licensed under the GPLv2.ContributorsMikel Larreategi,mlarreategi@codesyntax.comChangelog1.0.1 (2019-11-21)Fix flake8.
[erral]1.0 (2019-11-21)Avoid infitine loops.
[erral]1.0a2 (2019-09-12)Do not purge behaviors for LRF
[erral]1.0a1 (2019-09-06)Initial release.
[erral]
Package: cs.board
cs.boardThis products provides an announcement board for
public institution in which they can publish
official announcements.It has a WSDL interface to create automatic publishing
methods from a third-party toolChangelog1.7.2 (2011/12/14)Fix template order [erral]Change some strings [erral]1.7.1 (2011/10/24)Fix documentation markup [erral]1.7 (2011/10/24)Add ‘sender’ field for documents [erral]Populate sender automatically when called from WS [erral]1.6.1 (2011/10/12)Fix Changelog [erral]1.6 (2011/10/12)Metadata [erral]1.5 (2011/03/17)Add the list of private documents to the board view (only viewable holding proper permission) [erral]Add translations [erral]1.4 (2011/03/15)Safely convert to UTF-8 the description and filenames [erral]Store filename in documents added from WS [erral]Set effective and expiration dates correctly [erral]Add sorting to board view [erral]1.3 (2011/01/03)Add some extra css classes for expired documents
[erral]1.2 (unreleased)Add z3c.soap and soaplib dependencies to setup.py and configure.zcml
to avoid adding them to buildout.cfg
[erral]Add auto-translation hook for BoardDocuments too
[erral]1.1.1 (2010/09/20)Brown bag release, remove a pdb…
[erral]1.1 (2010/09/20)WS is only ready to documents in Spanish and Basque. More work
is needed to have automatic detection of languages
[erral]WS description WSDL file created at <board-url>/wsdl
[erral]WS implementation changed to SOAP
[erral]1.0 (2010/09/17)WS implementation using XML-RPC
[erral]Files are translated automatically
[erral]BoardDocuments need to be translated manualy to get correct title translation
[erral]Initial implementation:  Board, BoardDocument and Files.
[erral]
Package: cs.bodysection
After the INavigationRoot fixes in previous versions of Plone, if you install
LinguaPlone 4.x in Plone 4.x you will end having section-es, section-en, and so
on in your site.That’s because LinguaPlone 4.x adds root folder for each language in your site
and sets them INavigationRoot interface.In some projects you need content-based section identifiers for your body to get
them styled property by your designer.That’s what you get with this small products. It just have a browser view with
one method. Add it to your main_template in this way:<body tal:define="isRTL portal_state/is_rtl;
                  sl python:plone_view.have_portlets('plone.leftcolumn', view);
                  sr python:plone_view.have_portlets('plone.rightcolumn', view);
                  root_content context/@@navigation_root_content;
                  body_content_class root_content/section_content_body_class;
                  body_class python:plone_view.bodyClass(template, view) + ' ' + body_content_class;
                  sunburst_view python:context.restrictedTraverse('@@sunburstview')"In this way your body tag will have an extra content-section-your-items-id class
and yet preserve the section-es (or the one for your language).Useful? It is useful for us :)UseAdd it to your buildout:eggs =
     ...
     cs.bodysectionAnd run buildout. No need to install it.Changelog1.3 (2010/12/20)fix to add just first level classname
[erral]1.2 (2010/12/01)remove the method to check if the context is the default
page of a INavigationRoot element. This product is not the
place for that
[erral]1.1 (2010/11/25)added a new method to the view to check whether
the current context item is a INavigationRoot item
or a default-page of a INavigationRoot item
[erral]1.0.1 (2010/11/09)fix documentation
[erral]1.0 (2010/11/08)Initial release
[erral]
Package: csboilerplate
console script boilerplatesome boilerplate stuff for console scripts. inspired by now unmaintainedpyCLI.decorate your main function and register it in yoursetup.pyasconsole_scriptsentry_point [1]. the function will receive an app object as argument.you get:pythonsArgumentParserKeyboardInterruptis catchedSIGTERMis handled, so that context managers will exit properlylogging helperexit_handlerandsigterm_handlermay be customized.[1]https://setuptools.readthedocs.io/en/latest/setuptools.html#automatic-script-creationexamplefromcsboilerplateimportcli_app@cli_app(name=__name__)defmain(app):app.logging_config(log_level=app.args.debug)# do your stuffmain.argparser.add_argument('-d','--debug',action='count',default=0,help='lower logging threshold, may be used twice')dev envcheckout git and:virtualenv .env -p python3
. .env/bin/activate
pip install -e .[dev]
Package: csbschema
csbschemacsbschemadefines a JSON Schema and validator (implemented in Pyhon) forIHO B-12 Crowdsourced Bathymetrymetadata and data.InstallationTo install from PyPi, first create a virtual environment for your project, then:pipinstallcsbschemaClone or download this repository, then run:$pipinstall.UsageConvention GeoJSON CSB 3.1JSON files conforming toGeoJSON CSB 3.0.0 metadatacan be validated using the 3.1.0-2023-03schema(e.g., convention 'GeoJSON CSB 3.1'):$csbschemavalidate-fdocs/IHO/b12_v3_1_0_example.json
CSBdatafile'docs/IHO/b12_v3_1_0_example.json'successfullyvalidatedagainstschema'3.1.0-2023-03'.Validating an invalid document will show where in the document errors were be found:$csbschemavalidate-fdocs/IHO/b12_v3_1_0_example-invalid.jsonValidationofdocs/IHO/b12_v3_1_0_example-invalid.jsonagainstschema3.1.0-2023-03failedduetothefollowingerrors:Path:/properties/trustedNode/convention,error:'GeoJSON CSB 3.0'isnotoneof['GeoJSON CSB 3.1']Path:/features/1/properties,error:'depth'isarequiredproperty
Path:/features/3/properties,error:'time'isarequiredproperty
Path:/features/4/properties/time,error:'2016-03-03 18:41:49Z'doesnotmatch'^([0-9]+)-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])[Tt]([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9]|60)([.][0-9]+)?[Zz]$'Path:/properties/platform/IDNumber,error:IDNumberIMO3699580isnotvalidforIDTypeMMSI.
Path:/properties/platform/dataProcessed,error:dataProcessedflagis'false',but'processing'propertieswerefound.
Path:/properties/platform/uniqueID,error:uniqueID:SEAID-45f5c322-10f2-4946-802e-d5992ad36727doesnotmatch/properties/trustedNode/uniqueVesselID:SEAID-e8c469f8-df38-11e5-b86d-9a79f06e9478Conventions GeoJSON CSB 3.0 and XYZ CSB 3.0A schema for the provisional JSON encoding of B12 3.0.0 data and metadata (e.g., convention 'GeoJSON CSB 3.0') is
available under the schema name '3.0.0-2023-03':$csbschemavalidate-fdocs/NOAA/example_csb_geojson_file.geojson--version3.0.0-2023-03Similarly, a metadata-only schema (e.g., convention 'XYZ CSB 3.0') is available under the schema name
'XYZ-3.0.0-2023-03':$csbschemavalidate-fdocs/NOAA/noaa_b12_v3_0_0_xyz_required.json--versionXYZ-3.0.0-2023-03The metadata-only 'XYZ schema' is meant to be used for JSON metadata supplied alongside CSB data in CSV or another
format.Convention GeoJSON CSB 3.2A schema for a beta JSON encoding of B12 3.0.0 (e.g., convention 'GeoJSON CSB 3.2') is available under the schema
name '3.2.0-BETA':$csbschemavalidate-fdocs/IHO/b12_v3_2_0-BETA_example.json--version3.2.0-BETA
CSBdatafile'docs/IHO/b12_v3_2_0-BETA_example.json'successfullyvalidatedagainstschema'3.2.0-BETA'.Runcsbschema validate --helpfor more information about validating against different versions of the schema.TestingFirst, install test dependencies:$pipinstall-rrequirements-test.txtThen run unit tests:$pytesttests/unit/test_*.pyRun integration tests, which tests running thecsbschema validatecommand line tool for many of the example
CSB documents found in thecsbschemarepository:$bashtests/integration/validate_cmd.sh
Package: csbuilder
csbuilderThe framework supports you to build complex Client-Server applications.How to buildOur library is only supported by Python 3. Now we test it only on Python 3.7.1. If you meet any problems, even if with other versions, you couldcreate an issueto notify us. We will solve them as quickly as possible.Create Virtual Environment (optional but IMPORTANT)If you had your virtual environment, you can ignore this step.You ought to create a virtual environment to avoid conflicting with other applications on your machine when installing our module. The virtual environment must be installed withPython 3.I highly recommend you to useAnacondabecause of its utilities. The command of creating a virtual environment in Anaconda is:$condacreate-nyour_venv_name
$condaactivateyour_venv_name(your_venv_name)$_Or usePython venv:$python-mvenvpath/to/your/venv
$path/to/your/venv/Scripts/activate.bat(your_venv_name)$_Method 1: Install the PyPI version (not completed yet)(your_venv_name)$pipinstallcsbuilderMethod 2: Install the newest version (recommendation)(your_venv_name)$gitclonehttps://github.com/huykingsofm/csbuilder.git(your_venv_name)$cdcsbuilder(your_venv_name)csbuilder$pipinstall-e.How to useJust useimportstatement and enjoy it. We will write documentation and tutorials as soon as possible so that you can understand our library easier.fromcsbuilder.listenerimportListenerfromcsbuilder.clientimportClientResponserExampleSee the librarysftsupporting file transfer usingcsbuilder.Change logVersion 0.0.2Fix the error inwait_resultof Session.Remove ActiveSession and PassiveSession. Now csbuilder allows to create the protocol which has both active activation and passive activation.Change size of elements in cspacket.Add role toCSPacket. Now aSessionManagercan contain multiple roles of a protocol.Remove theCSPacketUtils. Instead, addfrom_bytestoCSPacketto extract the packet.Version 0.0.1Hello world.
Package: csc
csc-  Execute python scripts cell by cellInstall withpipinstallcscUsageConsider the following training script#: parameters...#: setup...#: train...#: save...To run the the script cell by cell, use:script=csc.Script("experiment.py")script.run("parameters")script.run("setup")script.run("train")script.run("save")Splicing scriptsDifferent scripts can be "spliced" together by specifying multiple scripts. The
first script acts as the base script and defines the available cells. Subsequent
scripts, or spliced scripts, can extend the cells of the base script. All
scripts share a single scope. For each cell, first the code of the base script
is executed and then the code of the spliced scripts.# file: parameters.py#: parametersbatch_size=...scripts=csc.Script(["experiment.py","parameters.py"])# executes first the 'parameters' cell of 'experiment.py', then the# 'parameters' cell of 'parameters.py'scripts.run("parameters")Command line usagecscinclude a command line script splice and execute scripts. Usage:$python-mcscbase_script.pyspliced_script_1.pyspliced_script_2.pyTo splice in parameters,cscoffers a shortcut: arguments specified via-p STATEMENTare concatenated into a script with a single 'parameters' cell that
executes the given statements.# this call$python-mcscbase_script.py-pbatch_size=100-plearning_rate=3e-4# is equivalent to$python-mcscbase_script.pyparameters.py
$catparameters.py#: parametersbatch_size=100learning_rate=3e-4API Referencecsc.Script(base_script: Union[str, pathlib.Path, FileSource, InlineSource], /, *spliced_scripts, cell_marker: str = '#:', register: bool = False)A Python script that can be executed cell by cellCells are defined via comments (per default '#: {CELL_NAME}').csc.Script.list(self) -> list[str]List all cells of the scriptOnly cells of the base script are considered.csc.Script.run(self, *cell_names) -> NoneRun cells of the script by namecsc.Script.eval(self, expr: str) -> AnyEvaluate an expression the scope of the scriptcsc.FileSource(path: pathlib.Path, *, cell_marker: str)Define a script via a filecsc.InlineSource(text: str, *, cell_marker: str)Define a script via its sourceLicenseThis package is licensed under the MIT License. SeeLICENSEfor details.
Package: csc-docker-pool
# CSC Docker toolsCSC Docker is a simple CLI tool to manage relay and staking node in
CSC network.
There are many common scenarios in CSC node management and this tool
makes them easy.## RequirenmentDockerPython## Getting startpip install csc-docker-tool
genz-docker-cetd relay init –name main
genz-docker-cetd relay run –name maingenz-docker-cetd staking init –name main-staking
genz-docker-cetd staking run –name main-staking
Package: csci.feedback
.. contents::.. Note!-----Update the following URLs to point to your:- code repository- bug tracker- questions/comments feedback mail(do not set a real mail, to avoid spams)Or remove it if not used.- Code repository: http://svn.somewhere.com/...- Questions and comments to somemailing_list- Report bugs at http://bug.somewhere.com/..Change history**************Changelog=========1.0 (xxxx-xx-xx)----------------- Created recipe with ZopeSkel[Peter Dyson]Detailed Documentation**********************Introduction============This is a full-blown functional test. The emphasis here is on testing whatthe user may input and see, and the system is largely tested as a black box.We use PloneTestCase to set up this test as well, so we have a full Plone siteto play with. We *can* inspect the state of the portal, e.g. usingself.portal and self.folder, but it is often frowned upon since you are nottreating the system as a black box. Also, if you, for example, log in or setroles using calls like self.setRoles(), these are not reflected in the testbrowser, which runs as a separate session.Being a doctest, we can tell a story here.First, we must perform some setup. We use the testbrowser that is shippedwith Five, as this provides proper Zope 2 integration. Most of thedocumentation, though, is in the underlying zope.testbrower package.>>> from Products.Five.testbrowser import Browser>>> browser = Browser()>>> portal_url = self.portal.absolute_url()The following is useful when writing and debugging testbrowser tests. It letsus see all error messages in the error_log.>>> self.portal.error_log._ignored_exceptions = ()With that in place, we can go to the portal front page and log in. We willdo this using the default user from PloneTestCase:>>> from Products.PloneTestCase.setup import portal_owner, default_password>>> browser.open(portal_url)We have the login portlet, so let's use that.>>> browser.getControl(name='__ac_name').value = portal_owner>>> browser.getControl(name='__ac_password').value = default_password>>> browser.getControl(name='submit').click()Here, we set the value of the fields on the login form and then simulate asubmit click.We then test that we are still on the portal front page:>>> browser.url == portal_urlTrueAnd we ensure that we get the friendly logged-in message:>>> "You are now logged in" in browser.contentsTrue-*- extra stuff goes here -*-Contributors************Peter Dyson, AuthorDownload********
Package: csci.images
.. contents::.. Note!-----Update the following URLs to point to your:- code repository- bug tracker- questions/comments feedback mail(do not set a real mail, to avoid spams)Or remove it if not used.- Code repository: http://svn.somewhere.com/...- Questions and comments to somemailing_list- Report bugs at http://bug.somewhere.com/..Change history**************Changelog=========1.0 (xxxx-xx-xx)----------------- Created recipe with ZopeSkel[Peter Dyson]Detailed Documentation**********************Introduction============This is a full-blown functional test. The emphasis here is on testing whatthe user may input and see, and the system is largely tested as a black box.We use PloneTestCase to set up this test as well, so we have a full Plone siteto play with. We *can* inspect the state of the portal, e.g. usingself.portal and self.folder, but it is often frowned upon since you are nottreating the system as a black box. Also, if you, for example, log in or setroles using calls like self.setRoles(), these are not reflected in the testbrowser, which runs as a separate session.Being a doctest, we can tell a story here.First, we must perform some setup. We use the testbrowser that is shippedwith Five, as this provides proper Zope 2 integration. Most of thedocumentation, though, is in the underlying zope.testbrower package.>>> from Products.Five.testbrowser import Browser>>> browser = Browser()>>> portal_url = self.portal.absolute_url()The following is useful when writing and debugging testbrowser tests. It letsus see all error messages in the error_log.>>> self.portal.error_log._ignored_exceptions = ()With that in place, we can go to the portal front page and log in. We willdo this using the default user from PloneTestCase:>>> from Products.PloneTestCase.setup import portal_owner, default_password>>> browser.open(portal_url)We have the login portlet, so let's use that.>>> browser.getControl(name='__ac_name').value = portal_owner>>> browser.getControl(name='__ac_password').value = default_password>>> browser.getControl(name='submit').click()Here, we set the value of the fields on the login form and then simulate asubmit click.We then test that we are still on the portal front page:>>> browser.url == portal_urlTrueAnd we ensure that we get the friendly logged-in message:>>> "You are now logged in" in browser.contentsTrue-*- extra stuff goes here -*-Contributors************Peter Dyson, AuthorDownload********
Package: csclib
csclib秘密分散に基づく秘匿計算ライブラリ環境3台のPCで計算を行います（1台でも可）．それぞれを server, party_1, party_2 とします．
server は入力データを平文で受け取って，それをシェアに変換し，party 1, 2 に送ります．また，相関乱数を生成し party 1, 2 に送ります．
現状では，server では答え合わせ用に全ての計算を平文で行っています．
party_１ と party_2 は相互に通信を行いながら計算をします．コンパイルC言語またはC++で #include "share.h" して使います．(LOUDSを使う場合は #include "LOUDS.h")
party の番号を -1 として実行すると，全ての計算を1台で（平文で）行います．アルゴリズムの確認や，MPCによる速度低下を評価する際に使えます．実行config.txt に3台のPCのIPアドレスとポートを設定します．127.0.0.1 9800 # server
127.0.0.1 9810 # party 1
127.0.0.1 9820 # party 2各行がPCのIPアドレスと使用するポートですが，ポートはここに書かれた値から3つ分を使います．
（この例ではサーバの場合，9800, 9801, 9802 を使います）
1台のPCで実行する場合，全てのIPアドレスを localhost (127.0.0.1) にします．ポート番号は全てが異なるようにします．
複数台ある場合にはそれぞれのIPアドレスを指定します．なお，他のPCと通信を行う場合にはPCのファイアーウォールの設定を変える必要があります．実行ファイル名を share.out とすると，3台のPC（ターミナル）それぞれで実行します．@server:$ ./share.out 0
@party_1:$ ./share.out 1
@party_2:$ ./share.out 2Pythonコンパイルと実行方法．@server:$ python3 -m venv env
@server:$ source env/bin/activate
@server:$ cd python/csclib
@server:$ python3 setup.py build
@server:$ pip3 install .PyPIからのインストール@server:$ sudo apt install gcc python3.10-dev python3.10-venv python3-pip
@server:$ python3 -m venv env
@server:$ source env/bin/activate
(env) @server:$ pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ csclibpythonのソース内ではfrom csclib import *とする．