Saravanan666/pypi-org huggingface dataset:
Package: etest
Description===========Framework for testing ebuilds.Using Docker to provide consistent sandboxed environments, etest runs ebuildsthrough several tests (implicitly and explicitly defined).  Every ebuild getsmany containers created to run every testing scenario in isolation.  Testingscenarios are created from combinations of USE flags, features (test or notest), as well as custom commands provided in the hints files.Installation============This package is available in my overlay, alunduil, and can be installed onGentoo quite easily::layman -a alunduilemerge app-portage/etestThis package is also stored in PyPI and can be installed the standard way::pip install etestThe latest release available is:.. image:: https://badge.fury.io/py/etest.png:target: http://badge.fury.io/py/etest``etest`` does require a running docker daemon but does not explicitly list itas a requirement.  It's not explicitly listed since the docker daemon doesn'tnecessarily need to be local.  Non-local docker daemons are not currentlysupported.Using etest===========.. note::etest requires a running docker daemon (either local or remote).  If usinga remote docker instance you must set the DOCKER_HOST environment variablewith the hostname (just like compose).To get started simply run ``etest`` in a directory that contains ebuilds in avalid overlay.Alternatively, while still in a valid overlay directory or subdirectory, a listof ebuilds can be passed to ``etest`` to run tests only against those ebuilds::# Run all etest tests for all ebuild versions.cd /var/lib/layman/alunduiletest app-portage/etest# Run all etest tests for the specified ebuild.cd app-portage/etestetest etest-9999.ebuildMore advanced usage of this package is outlined in the built-in help::etest --helpDeveloping etest================If you would prefer to clone this package directly from git or assist withdevelopment, the URL is https://github.com/alunduil/etest.etest is tested continuously by Travis-CI and running the tests is quitesimple::flake8python setup.py testSystem tests can be run as well but require a working docker daemon as well asapproximately two and half hours::nosetests test_etest/test_systemThe current status of the build is:.. image:: https://secure.travis-ci.org/alunduil/etest.png?branch=master:target: http://travis-ci.org/alunduil/etestKnown Issues============Known issues can be found in the github issue list athttps://github.com/alunduil/etest/issues.Troubleshooting===============If you need to troubleshoot an issue or submit information in a bug report, werecommend obtaining the following pieces of information:* output with verbose output turned on* any relevant stack traces
Package: etesync
EteSync - Secure Data SyncThis is a python client library forEteSyncThis module provides a python API to interact with an EteSync server.
It currently implements AddressBook and Calendar access, and supports two-way
sync (both push and pull) to the server.
It doesn't currently implement pushing raw journal entries which are needed for
people implementing new EteSync journal types which will be implemented soon.To install, please run:pip install etesyncThe module works and the API is tested (seetests/), however there still
may be some oddities, so please report if you encounter any.There is one Authenticator endpoint, and one endpoint for the rest of the API
interactions.The way it works is that you run "sync", which syncs local cache with server.
Afterwards you can either access the journal directly, or if you prefer,
you can access a collection, for example a Calendar, and interact with the
entries themselves, which are already in sync with the journal.Check outexample.pyfor a basic usage example, or the tests
for a more complete example.While this is stable enough for usage, it still may be subject to change, so
please watch out for the changelog when updating version.
Docs are currently missing but are planned.Running the example scriptYou may also need to make sure you have the OpenSSL development package
installed (e.g.openssl-dev).Check out this repository:git clone git@github.com:etesync/pyetesync.git
cd pyetesyncSetup the environment:python3 -m venv venv
source venv/bin/activate
pip install -r requirements.in/requirements-dev.txtRunexample.pyto export your data:python3 example.py <email> <auth password> <encryption password> https://api.etesync.comYou may need to surround your passwords in quotes and you may need to escape special characters with a\.
Please note, that depending on your setup, passing your passwords as command line parameters may not be completely secure,
so it would be better if you manually edit the file.And all of your data will be copied to a local database located at~/.etesync/data.db.Running the testsSome to the tests are unit tests, but some are integration tests who need an actual EteSync service with a few user names set up in order for them to work.You'd need to run your local server:https://github.com/etesync/server-skeleton/And then add two users:test@localhosttest2@localhostPassword for both: SomePasswordThat's it.
Package: etesync-dav
This is a CalDAV and CardDAV front-end forEteSync.This package provides a local CalDAV and CardDAV server that proxies requests
to an EteSync server for use with desktop CalDAV and CardDAV clients.This is essentially a compatibility layer between EteSync and DAV clients.Source code:https://github.com/etesync/etesync-davREADME:https://github.com/etesync/etesync-dav/blob/master/README.mdRelease Information## Version 0.32.1
* Support radicale 3.1.0 for EteSync 1.0 tooFull changelog.
Package: etext
etext is a python module that lets you send text messages using email SMS gateways. Both SMS and MMS are supported.Instalationpip install etextSending SMS messagesfrom etext import send_sms_via_email

phone_number = "123-123-1234"
message = "hello world!"
provider = "T-Mobile"

sender_credentials = ("email@gmail.com", "email_password")

send_sms_via_email(
    phone_number, message, provider, sender_credentials, subject="sent using etext"
)number: str- phone number to textmessage: str- message to sendprovider: str- phone provider/carrierclick here to see the supported providers.sender_credentials: tuple- email and password for SMTP serversubject: str = "sent using etext"- subject for the email headersmtp_server: str = "smtp.gmail.com"- smtp server to use (gmail is the default)smtp_port: int = 465- smtp port (465) is the defaultnote the use of the keyword argument 'subject', some SMS gateways need a message to be formatted as an email, this includes the use of a subject in the header. You can try experimenting with the gateway you are using to see if you need to include text in the subject. Otherwise, you can pass in an empty subject like so:subject=""by default the smtp client used to send emails is gmail's smtp server on port 465. However, if you want to use a different smtp server or port you can do that using thesmtp_serverandsmtp_portkeyword arguments like this:send_sms_via_email(
    phone_number,
    message,
    provider,
    sender_credentials,
    smtp_server="some_smtp_server",
    smtp_port="502",
)Sending MMS messagesfrom etext import send_mms_via_email

file_path = "/path/to/file/file.png"

mime_maintype = "image"
mime_subtype = "png"

# note that compared to the first example, this number is formatted differently
# etext removes any characters that are not digits in the number, so feel free
# to format numbers however you want
phone_number = "(123) 123-1234"

message = "hello world!"
provider = "T-Mobile"

sender_credentials = ("email@gmail.com", "email_password")

send_mms_via_email(
    phone_number,
    message,
    file_path,
    mime_maintype,
    mime_subtype,
    provider,
    sender_credentials,
)This method has all of the same parameters as the SMS method but adds three more parameters.file_path:str- the file path of the file to send in the messagemime_maintype:str- the mime main typemime_subtype:str- the mime sub typehere is a resource containing common mime typesthe format corresponds like this:mime_maintype/mime_subtype. As an example, to send a pdf file via MMS, which has the following MIME type:application/pdf, we could use these main and subtypes:mime_maintype = "application"
mime_subtype = "pdf"MoreIf you are using etext with Gmail, you should set up an app password for use with etext. You can do that by clickinghere.
Package: etextedit
# eTextEdit
Extensible Text Editor; built with prompt toolkitOriginally a simple text editor created by Jonathan Slenders
Source:https://github.com/prompt-toolkit/python-prompt-toolkit/blob/master/examples/full-screen/text-editor.pyModified and Enhanced by Eliran Wong:
* added file and clipboard utilities
* added regex search & replace feature
* added key bindings
* added handling of unasaved changes
* added dark theme and lexer style
* support stdin, e.g. echo “Hello world!” | python3 eTextEdit.py
* support file argument, e.g. python3 eTextEdit.py <filename>
* support plugins (forthcoming)eTextEdit repository:https://github.com/eliranwong/eTextEdit# Screenshots![search_replace](https://github.com/eliranwong/eTextEdit/assets/25262722/c7a564ce-2e3c-4913-8210-52e259545044?raw=True)![menu](https://github.com/eliranwong/eTextEdit/assets/25262722/7703f138-e56e-4c6f-84fc-4abe768f161a?raw=True)# Download> pip install –upgrade etextedit# UsageTo launch eTextEdit:> etexteditTo open a text file, e.g. test.txt:> etextedit test.txtTo pipe in a text string, e.g. “Hello World!”:> echo “Hello World!” | etexteditTo append a file, e.g. test.txt, with a text string, e.g. “Hello World!”:> echo “Hello World!” | etextedit test.txt# Key Bindingsescape + m: toggle menucontrol + k: helpcontrol + q: quitcontrol + a: select allescape + a: deselect allcontrol + c: copycontrol + v: pastecontrol + x: cutcontrol + z: undocontrol + i: insert spacescontrol + f: findescape + f: clear i-search highlightscontrol + r: find & replacecontrol + l: go to linecontrol + d: deletecontrol + n: new filecontrol + o: open filecontrol + s: save filecontrol + w: save as file## Navigationescape + a: go to beginning of documentescape + z: go to end of documentescape + b: go to beginning of current lineescape + e: go to end of current line
Package: eth2fastspec
eth2fastspecEth2fastspec is an extension toeth2spec, utilizing the same types, configuration and dependencies, but optimized for transition speed.UsageA few new objects are introduced for precomputed data, speeding up the transition:ShufflingEpoch: Committee shuffling information for a single epochEpochsContext: A collection of contextual information to re-use during an epoch, and rotating precomputed data of the next epoch into the current epoch. This includes shuffling, but also proposer information is available.epochs_ctx.load_state(state)precomputes the data for the given state.sync_pubkeys()checks the precomputed data against a state, and then adds missing  pubkeys (strictly append-only however, not meant to fork this information)copy()if a fork occurs, the context will have to be copied. To avoid copying the immutable parts, thecopy()implements a specialized copy routine.rotate_epochs()to re-use information, such as the shuffling of the next epoch, after transitioning into a new epoch, therotate_epochs()is called. The transition function takes care of epoch-context data rotation.FlatValidator: A copy of the regularValidator, but in a simple object instead of a tree-representation. For intermediate computation the remerkleable representation slows things down, so a regular object is used instead.AttesterStatus: During the epoch transition, additional data is precomputed to avoid traversing any state a second time. Attestations are a big part of this, and each validator has an "status" to represent its precomputed participation.EpochProcess: TheAttesterStatus(andFlatValidatorunderstatus.validator) objects andEpochStakeSummaryare tracked in theEpochProcessand made available as additional context in the epoch transition.prepare_epoch_process_state(epochs_ctx, state)computes this data.Method signatures in the spec changed to utilize precomputed data:state_transition,process_slots,process_slot,process_epoch, every epoch sub-process,process_block, every block sub-process, andverify_block_signatureall have an additionalepochs_ctx(EpochsContext) argument.every epoch sub-process has an additionalprocess(EpochProcess) argument.The argument order is generally:epochs_ctx,proces,state, remaining args.frometh2spec.config.config_utilimportprepare_config# Example: load a config, loading it in `eth2spec` as well as `eth2fastspec`, before loading the spec modules.prepare_config("./lighthouse","config")importeth2fastspecasspecstate:spec.BeaconState=...# BeaconState.deserialize(stream, size), or some other source.block:spec.SignedBeaconBlock=...epochs_ctx=spec.EpochsContext()epochs_ctx.load_state(state)spec.state_transition(epochs_ctx,state,block)print(state.hash_tree_root().hex())LicenseMIT, seeLICENSEfile.
Package: eth2spec
Ethereum Proof-of-Stake Consensus SpecificationsTo learn more about proof-of-stake and sharding, see thePoS FAQ,sharding FAQand theresearch compendium.This repository hosts the current Ethereum proof-of-stake specifications. Discussions about design rationale and proposed changes can be brought up and discussed as issues. Solidified, agreed-upon changes to the spec can be made through pull requests.SpecsCore specifications for Ethereum proof-of-stake clients can be found inspecs. These are divided into features.
Features are researched and developed in parallel, and then consolidated into sequential upgrades when ready.The current features are:Phase 0The Beacon ChainBeacon Chain Fork ChoiceDeposit ContractHonest ValidatorP2P NetworkingWeak SubjectivityAltairBeacon chain changesAltair forkLight client sync protocolHonest Validator guide changesP2P NetworkingBellatrix (also known as The Merge)The Bellatrix protocol upgrade is still actively in development. The exact specification has not been formally accepted as final and details are still subject to change.Background material:Anethresear.chpostdescribing the basic mechanism of the CL+EL mergeethereum.orghigh-level description of the CL+EL mergehereSpecifications:Beacon Chain changesBellatrix forkFork Choice changesValidator additionsP2P NetworkingShardingSharding follows Bellatrix, and is divided into three parts:Sharding base functionality - In early engineering phaseBeacon Chain changesP2P Network changesCustody Game - Ready, dependent on shardingBeacon Chain changesValidator custody workData Availability Sampling - In active R&DTechnical detailshere.Core types and functionsP2P NetworkingFork ChoiceSampling processAccompanying documents can be found inspecsand include:SimpleSerialize (SSZ) specMerkle proof formatsGeneral test formatAdditional specifications for client implementersAdditional specifications and standards outside of requisite client functionality can be found in the following repos:Beacon APIsBeacon MetricsDesign goalsThe following are the broad design goals for the Ethereum proof-of-stake consensus specifications:to minimize complexity, even at the cost of some losses in efficiencyto remain live through major network partitions and when very large portions of nodes go offlineto select all components such that they are either quantum secure or can be easily swapped out for quantum secure counterparts when availableto utilize crypto and design techniques that allow for a large participation of validators in total and per unit timeto allow for a typical consumer laptop withO(C)resources to process/validateO(1)shards (including any system level validation such as the beacon chain)Useful external resourcesDesign RationalePhase 0 Onboarding DocumentCombining GHOST and Casper paperFor spec contributorsDocumentation on the different components used during spec writing can be found here:YAML Test GeneratorsExecutable Python Spec, with Py-testsConsensus spec testsConformance tests built from the executable python spec are available in theEthereum Proof-of-Stake Consensus Spec Testsrepo. Compressed tarballs are available inreleases.
Package: eth-abi
Ethereum Contract Interface (ABI) UtilityPython utilities for working with Ethereum ABI definitions, especially encoding and decodingRead more in thedocumentation on ReadTheDocs.View the change log.Quickstartpython-mpipinstalleth-abiDeveloper SetupIf you would like to hack on eth-abi, please check out theSnake Charmers
Tactical Manualfor information on how we do:TestingPull RequestsDocumentationWe usepre-committo maintain consistent code style. Once
installed, it will run automatically with every commit. You can also run it manually
withmake lint. If you need to make a commit that skips thepre-commitchecks, you
can do so withgit commit --no-verify.Development Environment SetupYou can set up your dev environment with:gitclonegit@github.com:ethereum/eth-abi.gitcdeth-abi
virtualenv-ppython3venv
.venv/bin/activate
python-mpipinstall-e".[dev]"pre-commitinstallRelease setupTo release a new version:makereleasebump=$$VERSION_PART_TO_BUMP$$How to bumpversionThe version format for this repo is{major}.{minor}.{patch}for stable, and{major}.{minor}.{patch}-{stage}.{devnum}for unstable (stagecan be alpha or beta).To issue the next version in line, specify which part to bump,
likemake release bump=minorormake release bump=devnum. This is typically done from the
main branch, except when releasing a beta (in which case the beta is released from main,
and the previous stable branch is released from said branch).If you are in a beta version,make release bump=stagewill switch to a stable.To issue an unstable version when the current version is stable, specify the
new version explicitly, likemake release bump="--new-version 4.0.0-alpha.1 devnum"
Package: eth-abi-parser
Ethereum ABI Parser UtilitySummaryThis package provides a way to parseHuman Readable ABIintroduced byethers.jsto the Python world. It's still pretty much a WIP. The goal is to be fully compatible withethers.jsandethers-rs.$pipinstallhuman-abifrometh_abi_parserimportHumanReadableParserparser=HumanReadableParser('event TestEvent(uint indexed id, (string, uint16, (uint8, uint8)) value)')print(parser.take_event())# {'type': 'event', 'name': 'TestEvent', 'anonymous': False, 'inputs': [{'type': 'uint', 'name': 'id', 'indexed': True}, {'type': 'tuple', 'name': 'value', 'indexed': False, 'components': [{'type': 'string'}, {'type': 'uint16'}, {'type': 'tuple', 'components': [{'type': 'uint8'}, {'type': 'uint8'}]}]}]}WIPThis library is still a work-in-progress. Features are being implemented as needed. But if you find it lacks what you need, feel free to submit a pull request!LICENSEApache License 2.0
Package: eth-abi-qtum
Ethereum Contract Interface (ABI) UtilityPython utilities for working with Ethereum ABI definitions, especially encoding and decodingRead more in thedocumentation on ReadTheDocs.View the change log.Quickstartpipinstalleth-abi-qtumDeveloper SetupIf you would like to hack on eth-abi, please check out theSnake Charmers
Tactical Manualfor information on how we do:TestingPull RequestsCode StyleDocumentationDevelopment Environment SetupYou can set up your dev environment with:gitclonegit@github.com:qtumproject/eth-abi.gitcdeth-abi
virtualenv-ppython3venv
.venv/bin/activate
pipinstall-e.[dev]Testing SetupDuring development, you might like to have tests run on every file save.Show flake8 errors on file change:# Test flake8when-changed-v-s-r-1eth_abi/tests/-c"clear; flake8 eth_abi tests && echo 'flake8 success' || echo 'error'"Run multi-process tests in one command, but without color:# in the project root:pytest--numprocesses=4--looponfail--maxfail=1# the same thing, succinctly:pytest-n4-f--maxfail=1Run in one thread, with color and desktop notifications:cdvenv
ptw--onfail"notify-send -t 5000 'Test failure ⚠⚠⚠⚠⚠' 'python 3 test on eth-abi failed'"../tests../eth_abiRelease setupFor Debian-like systems:apt install pandocTo release a new version:makereleasebump=$$VERSION_PART_TO_BUMP$$How to bumpversionThe version format for this repo is{major}.{minor}.{patch}for stable, and{major}.{minor}.{patch}-{stage}.{devnum}for unstable (stagecan be alpha or beta).To issue the next version in line, specify which part to bump,
likemake release bump=minorormake release bump=devnum. This is typically done from the
master branch, except when releasing a beta (in which case the beta is released from master,
and the previous stable branch is released from said branch).If you are in a beta version,make release bump=stagewill switch to a stable.To issue an unstable version when the current version is stable, specify the
new version explicitly, likemake release bump="--new-version 4.0.0-alpha.1 devnum"
Package: eth-abi-tool
eth-abi-toolEthereum Contract ABI UtilityUse blockchain explorer API (currently only etherscan) to query ABI data for a verified contract.A CLI interface is provided as well as a python object.Includes rate-limiting for use with the various Etherscan account types.Free software: MIT licenseDocumentation:https://eth-abi-tool.readthedocs.io.CreditsThis package was created with Cookiecutter andrstms/cookiecutter-python-cli, a fork of theaudreyr/cookiecutter-pypackageproject template.audreyr/cookiecutteraudreyr/cookiecutter-pypackagerstms/cookiecutter-python-cliCLI
Package: eth-account
eth-accountSign Ethereum transactions and messages with local private keysRead more in thedocumentation on ReadTheDocs.View the change log.Quickstartpython-mpipinstalleth-accountDeveloper SetupIf you would like to hack on eth-account, please check out theSnake Charmers
Tactical Manualfor information on how we do:TestingPull RequestsDocumentationWe usepre-committo maintain consistent code style. Once
installed, it will run automatically with every commit. You can also run it manually
withmake lint. If you need to make a commit that skips thepre-commitchecks, you
can do so withgit commit --no-verify.Development Environment SetupYou can set up your dev environment with:gitclonegit@github.com:ethereum/eth-account.gitcdeth-account
virtualenv-ppython3venv
.venv/bin/activate
python-mpipinstall-e".[dev]"pre-commitinstallTo run the integration test cases, you need to install node and the custom cli tool as follows:apt-getinstall-ynodejs# As sudo./tests/integration/js-scripts/setup_node_v20.sh# As sudocdtests/integration/js-scripts
npminstall-g.# As sudoRelease setupTo release a new version:makereleasebump=$$VERSION_PART_TO_BUMP$$How to bumpversionThe version format for this repo is{major}.{minor}.{patch}for stable, and{major}.{minor}.{patch}-{stage}.{devnum}for unstable (stagecan be alpha or beta).To issue the next version in line, specify which part to bump,
likemake release bump=minorormake release bump=devnum. This is typically done from the
main branch, except when releasing a beta (in which case the beta is released from main,
and the previous stable branch is released from said branch).If you are in a beta version,make release bump=stagewill switch to a stable.To issue an unstable version when the current version is stable, specify the
new version explicitly, likemake release bump="--new-version 4.0.0-alpha.1 devnum"