Saravanan666/pypi-org huggingface dataset:
Package: tramline
Tramline is a upload and download accelerator that plugs into Apache,using mod_python. Its aim is to make downloading and uploading large
media to an application server easy and fast, without overloading the
application server with large amounts of binary data.Tramline integrates into Apache using mod_python. The application
server is assumed to sit behind Apache, for instance hooked up using
mod_proxy or mod_rewrite.Tramline takes over uploading and downloading files, handling these
within Apache. Only a small configuration change in Apache should be
necessary to enable tramline.The application server remains in complete control over security, page
and form rendering, and everything else. Minimal changes are necessary
to any application to enable it to work with tramline; in fact it’s
just setting two response headers in a few places in the code.
Package: trampolim
trampolimA modern Python build backend.FeaturesTask system, allowing to run arbitrary Python code during the build processAutomatic version detection from git repos and git archivesEasy to use CLI -- build, publish, check for errors and recommended practices (Planned)UsagetrampolimimplementsPEP 621.
Yourpyproject.tomlshould look something like this:[build-system]build-backend='trampolim'requires=['trampolim~=0.1.0'][project]name='sample_project'version='1.0.0'description='A sample project'readme='README.md'requires-python='>=3.7'license={file='LICENSE'}authors=[{name='Filipe Laíns',email='lains@riseup.net'},]classifiers=['Development Status :: 4 - Beta','Programming Language :: Python',]dependencies=['dependency','some-backport ; python_version < "3.8"',][project.optional-dependencies]test=['pytest','pytest-cov',][project.scripts]sample_entrypoint='sample_project:entrypoint_function'[project.urls]homepage='https://my-sample-project-website.example.com'documentation='https://github.com/some-user/sample-project'repository='https://github.com/some-user/sample-project'changelog='https://github.com/some-user/sample-project/blob/master/CHANGELOG.rst'
Package: tramway
# TRamWAyTheTRamWAylibrary features various tools for the analysis of particle dynamics in Single Molecule Localization Microscopy (SMLM) data.
It can resolve the diffusivity, drift, force and potential energy in space and time.The [original documentation](https://tramway.readthedocs.io) is now on [readthedocs](https://tramway.readthedocs.io).An attempt to rewrite the project documentation is available as a [separate project and web resource](https://tramway-tour.readthedocs.io).## InstallationYou will need Python >= 3.6.### Windows usersPlease favor Conda, as Conda will seamlessly install the HDF5 standard library which is a required dependency.### From PyPI` pip install tramway `pip installwill install some Python dependencies if missing, but you may still need to install the [HDF5 reference library](https://support.hdfgroup.org/downloads/index.html).Note that the HDF5 library can usually be installed using any OS’ package manager.
Only Windows users may have to [manually download and install the HDF5 library](https://tramway.readthedocs.io/en/latest/libhdf5.html), if they do not wish to use Conda instead of pip.Several installation targets are available, includingfull, that install optional dependencies:` pip install tramway[full] `Most of the functionalities and code examples described in the documentation will run without optional dependencies.
It is safe to first installTRamWAywith minimal requirements and thenpip installthe missing dependencies as you hitImportErrorwhile usingTRamWAy.### Using Conda` conda install tramway-cconda-forge`Compared with the bare packagepipinstalls (with no installation targets), thecondapackage specifies some optional dependencies as required, so that the above command installs them.
However, many other optional dependencies are omitted.
Package: tranchitella.adyen
tranchitella.adyenThis package offers a Python interface to the Adyen payment gateway.UsageCreate a newAdyenPaymentGatewayobject:>>> from tranchitella.adyen import AdyenPaymentGateway
>>> obj = AdyenPaymentGateway(
...     url='https://pal-test.adyen.com/pal/servlet/soap/Payment',
...     user='ws@Company.YourCompany', password='YourPassword',
...     merchantAccount='MerchantAccount',
... )Authorise a transaction:>>> obj.authorise('T-1', 100, 'EUR', 'FABIO TRANCHITELLA',
...     '5555444433331111', '12', '2012', '737', ipAddress='127.0.0.1')
{'authCode': ... }Cancel a transaction:>>> print obj.cancel('8112083591854919')
TrueCapture a transaction:>>> print obj.capture('8112083586124880', 100, 'EUR')
TrueRefund a transaction:>>> print obj.refund('8112083586124880', 100, 'EUR')
TrueChanges0.3 (2011-12-13)Added support for the shopperStatement parameter.0.2 (2010-04-19)Relicensed to LGPL version 2 or later.0.1 (2010-02-26)First public release.
Package: tranchitella.recipe.fs
tranchitella.recipe.fsThis recipe creates files and directories in a buildout.UsageThis recipe offers the following entry points:mkdirmkfilemkdirThis is a minimalbuildout.cfgwhich makes use of themkdirrecipe:[buildout]
parts = dirs

[dirs]
recipe = tranchitella.recipe.fs:mkdir
paths =
    ${buildout:directory}/var
    ${buildout:directory}/var/lib
    ${buildout:directory}/var/tmp
    ${buildout:directory}/var/logThis will create the directories specified by thepathsattribute.mkfileThis is a minimalbuildout.cfgwhich makes use of themkfilerecipe:[buildout]
parts = conffiles

[conffiles]
recipe = tranchitella.recipe.fs:mkfile
template = ${buildout:directory}/templates/config
path = ${buildout:directory}/etc/config
mode = 0644
database = postgresThis will create the file specified by thepathattribute using the given
template; the file will be customized using string interpolations of the
options specified in the buildout part (eg.%(database)swill be replaced
with the stringpostgres).0.3 (2010-03-23)Do not consider directory and files as “created” by buildout, otherwise they
will be automatically removed by buildout when the recipe is uninstalled.Added logging0.2 (2010-03-07)Added a new recipe entry pointmkfile.0.1 (2010-02-29)Initial release.
Package: tranchitella.recipe.i18n
tranchitella.recipe.i18nThis buildout recipe creates i18n tools to extract and manage po files.  More
specifically, i18n messages can occur in Python code, in Chameleon (ZPT) page
templates and in ZCML declarations.ScriptsThis recipe provides the following scripts:i18nextract:extract the i18n messages from the Python code, the Chameleon (ZPT) page
templates and the ZCML configuration files;i18nmerge:requires the GNU gettext package to be installed; the command ‘msgmerge’
will be executed for each language;i18nstatus:prints a simple statistics with the status of the translations.UsageAdd to your buildout configuration file the following snippet:[i18n]
recipe = tranchitella.recipe.i18n
package = PACKAGE
zcml = PACKAGE:configure.zcml
expressions =
    first=PACKAGE.expressions:FirstExpression
    last=PACKAGE.expressions:LastExpression
output = locales
domain = DOMAIN
verify_domain = true
exclude =
    tests.py
    ftests.pyReplacePACKAGEwith your Python package name andDOMAINwith your i18n
domain; thezcmlsetting is optional.0.6 (2011-06-20)Do not break if the message extracted from a python file contains utf-8 text.0.5 (2010-06-06)Soft-dependency on quipu.publisher for the correct processing of ZCML files.Avoid useless double new line at the end of the autogenerated POT file.Avoid empty defaaults for zope.i18n’s MessageID instances.0.4 (2010-04-15)Install again on update, otherwise the i18n scripts are not updated unless
they are explicitly removed.0.3 (2010-03-17)Added support for Chameleon expressions using theexpressionsoption in
buildout.cfg or the--expressioncommand line argument.Bug fix: now the po template file is correctly encoded in UTF-8.Bug fix: element’s tail should not be included in the msg id.Bug fix: added support for translated elements contained in other translated
elements and marked with i18n:name.0.2 (2010-03-02)Added a new helper script to recompile the po files.0.1 (2010-02-17)First public release.
Package: tranchitella.recipe.nose
tranchitella.recipe.noseThis recipe creates anosetest runner script.UsageThe recipe supports the following options:eggsThe eggs option specified a list of eggs to test given as one ore more
setuptools requirement strings.  Each string must be given on a separate
line.script-nameThe script option gives the name of the script to generate, in the buildout
bin directory.  Of the option isn’t used, the part name will be used.defaultsThe defaults option lets you specify testrunner default options.extra-pathsOne or more extra paths to include in the generated test script.This is a minimal ‘’buildout.cfg’’ file which creates a test runner:[test]
recipe = tranchitella.recipe.nose
eggs = myapplication
defaults =
    --where src
    --with-coverage
    --cover-package myapplicationChanges0.1 (2010-04-21)First public release.
Package: tranchitella.recipe.testrunner
tranchitella.recipe.testrunnerThis recipe creates azope.testingtest runner script which supports code
coverage analysis using thecoveragepython library.UsageThe recipe supports the following options:eggsThe eggs option specified a list of eggs to test given as one ore more
setuptools requirement strings.  Each string must be given on a separate
line.script-nameThe script option gives the name of the script to generate, in the buildout
bin directory.  Of the option isn’t used, the part name will be used.extra-pathsOne or more extra paths to include in the generated test script.defaultsThe defaults option lets you specify testrunner default options.working-directoryThe working-directory option lets to specify a directory where the tests
will run. The testrunner will change to this directory when run. If the
working directory is the empty string or not specified at all, the recipe
will create a working directory among the parts.environmentA set of environment variables that should be exported before starting the
tests.initializationProvide initialization code to run before running tests.relative-pathsUse egg, test, and working-directory paths relative to the test script.This is a minimal ‘’buildout.cfg’’ file which creates a test runner:[test]
recipe = tranchitella.recipe.testrunner
eggs = myapplication

[test-coverage]
recipe = tranchitella.recipe.testrunner
eggs = myapplication
defaults = ['--coverage-module', 'myapplication', '--coverage-branch']Changes0.4 (2010-08-24)Updated code to depend on zope.testrunner instead of zope.testing.0.3 (2010-06-14)Added a new option (–coverage-html) to run the html coverage command.0.2 (2010-04-22)Added a new option (–coverage-annotate) to run the annotate coverage
command.Added a new option (–coverage-xml) to run the xml_report coverage command.0.1 (2010-04-22)First release, forked from zc.recipe.testrunner.
Package: tranchitella.recipe.wsgi
tranchitella.recipe.wsgiThis recipe creates apaste.deployentry point formod_wsgi.UsageThis is a minimal ‘’buildout.cfg’’ file which creates a WSGI script mod_wsgi
can use:[buildout]
parts = wsgi

[wsgi]
recipe = tranchitella.recipe.wsgi
eggs = myapplication
config-file = ${buildout:directory}/etc/deploy.ini
environ =
    CHAMELEON_CACHE=true
    CHAMELEON_STRICT=trueThis will create a small python script in the bin directory called ‘’wsgi’’
which mod_wsgi can load. You can also use the optional ‘’extra-paths’’ option
to specify extra paths that are added to the python system path.You may also use the ‘’script-name’’ option to specify the name of the
generated script file, if ‘’wsgi’’ is unsuitable.The apache configuration for this buildout looks like this::WSGIScriptAlias /mysite /path/to/buildout/bin/wsgi

<Directory /home/me/buildout>
    Order deny,allow
    Allow from all
</Directory>This recipe does not fully install packages, which means that console scripts
will not be created. If you need console scripts you can add a second buildout
part which useszc.recipe.eggto do a full install.Changes0.4 (2010-04-26)Removed dependency on Chameleon.Defaults to the part name for the script name instead of “wsgi”.Added tests.0.3 (2010-04-09)Add a script-name option to specify the name of the wsgi script to generate.
(Dan Fairs,dan@fezconsulting.com)Fix a bug where ‘None’ would appear in the generated file if no environ was
specified. (Dan Fairs,dan@fezconsulting.com)0.2 (2010-04-06)Install again on update, otherwise the wsgi script is not updated unless it
is explicitly removed.0.1 (2010-02-17)First public release.
Package: tranco
TrancoThis package allows easy access to the Tranco list, published athttps://tranco-list.eu.UsageCreate aTrancoobject, indicating whether you want to cache downloaded lists:fromtrancoimportTrancot=Tranco(cache=True,cache_dir='.tranco')You can then retrieve lists from this object using thelistmethod:latest_list=t.list()date_list=t.list(date='2019-02-25')This method returns aTrancoList, which allows you to retrieve a certain prefix of the list (top),
the list ID (list_id), the list page (list_page) or the rank of a domain (rank):latest_list.top(10000)latest_list.list_idlatest_list.list_pagelatest_list.rank("google.com")latest_list.rank("not.in.ranking")# returns -1You can also generate custom lists.
First, create aTrancoobject with valid credentials
(available from youraccount page):fromtrancoimportTrancot=Tranco(account_email="abc@xyz.eu",api_key="123ABC")Then, pass the configuration (according tothis schema)
of your custom list toconfigure:c=t.configure({'providers':['alexa','umbrella','majestic'],'startDate':'2021-01-01','endDate':'2021-01-30','combinationMethod':'dowdall','listPrefix':'full','filterPLD':'on',})This method returns a tuple: whether the list is already available or is still being generated,
and the ID that has been/will be assigned to the list.You can retrieve metadata for a list throughlist_metadata:m=t.list_metadata(list_id="6P7X")If a list is still being generated, you can use this method to track the progress;
once a list has been generated, this metadata will indicate how the list was configured.
Package: trand
TranD: Transcript DistancesTranD is a collection of tools to facilitate metrics of structural variation for whole genome
transcript annotation files (GTF) that pinpoint structural variation to the nucleotide level.TranD (Transcript Distances) can be used to calculate metrics of structural variation within and
between annotation files (GTF). Structural variation reflects organismal complexity and three
summary metrics for genome level complexity are calculated for every gene in a GTF file:  1) the
number of transcripts per gene; 2) the number of exons per transcript; and 3) the number of
unique exons (exons with unique genomic coordinates) per gene. From each these metrics
distributions a summary statistics such as mean, median, variance, inter-quartile range are
calculated. With 1GTF file input, gene mode can be used to generates these metrics for each gene
and summary statistics and distributions across genes. Distributions are visualized in a series
of plots.  For 1 GTF and 2GTF a pairwise mode calculates distance metrics between 2 transcripts
to the nucleotide.  In 1 GTF this is all possible pairs within the gene and in 2 GTF model this
is all possible pairs among GTF files. The distribution of these metrics across genes are
visualized and summary statistics for structural variations between pairs are calculated and
reported.  Visualizations of the distributions of the frequency of intron retention, alternative
exon usage, donor/acceptor variation and 5', 3' variation in UTR regions are provided as well as
tabular formatted nucleotide level distances for both 1GTF and 2 GTF.InstallationThe easiest way to install TranD is by using conda or mamba.conda install -c bioconda trandIf you already have a suitable environment with bedtools installed and only want to add python
packages runpip install trandin an activated conda or virtualenv environmentIf you clone this repository you can use the source/requirements.txt file to pip install required dependencies withpip install -r source/requirements.txtSee thePyPI TranD pagefor reference.We will add a conda trand package in the near future.
Package: transactions
transactions: Bitcoin for Humanstransactionsis a small python library to easily create and push
transactions to the bitcoin network.Installation$pipinstalltransactionsExamplesAssuming the following cast of characters:>>>alice='mhyCaF2HFk7CVwKmyQ8TahgVdjnHSr1pTv'>>>bob='mqXz83H4LCxjf2ie8hYNsTRByvtfV43Pa7'>>>carol='mtWg6ccLiZWw2Et7E5UqmHsYgrAi5wqiov'Moving10000satoshis fromalicetobob:>>>fromtransactionsimportTransactions>>>transactions=Transactions(testnet=True)>>>tx=transactions.create(alice,(bob,10000))>>>tx_signed=transactions.sign(tx,'alice master secret')>>>transactions.push(tx_signed)Moving600satoshis frombobtocarolwith a customop_return:>>>tx=transactions.create(bob,(carol,600),op_return='HELLOFROMASCRIBE')>>>tx_signed=transactions.sign(tx,'bob master secret')>>>transactions.push(tx_signed)Check it outfbbd6407b8fc73169918b2fce7f07aff6a486a241c253f0f8eeb942937fbb970Withtransactionsall amounts are in satoshi and we currently only supportBIP32wallets (hierarchical deterministic wallets, aka “HD Wallets”).Documentationhttps://transactions.readthedocs.org/ContributingPull requests, feedback, and suggestions are welcome.Issuesandpull requestsare handled
via github.BackgroundThis was developed by ascribe GmbH as part of the overall ascribe technology
stack.https://www.ascribe.ioCopyrightThis code is © 2015 ascribe GmbH.Licensed under the Apache License, Version 2.0.
Package: transbank-sdk
Transbank Python SDKSDK Oficial de TransbankRequisitos:Python 3.4+InstalaciónPuedes instalar el SDK directamentepipinstalltransbank-sdkO puedes instalar el SDK a través de Pipenv, agregando a Pipfile:[packages]transbank-sdk='*'y luego ejecutar:pipenvinstallDocumentaciónPuedes encontrar toda la documentación de cómo usar este SDK en el sitiohttps://www.transbankdevelopers.cl.La documentación relevante para usar este SDK es:Documentación general sobre los productos y sus diferencias:Webpay.Documentación sobreambientes, deberes del comercio, puesta en producción,
etc.Primeros pasos conWebpay.Referencia detallada sobreWebpay.Información para contribuir y desarrollar este SDKRequerimientosPipenvPlugin de editorconfig para tu editor favorito.StandaresPara los commits respetamos las siguientes normas:https://chris.beams.io/posts/git-commit/Usamos ingles, para los mensajes de commit.Se pueden usar tokens como WIP, en el subject de un commit, separando el token con:, por ejemplo:WIP: This is a useful commit messagePara los nombres de ramas también usamos ingles.Se asume, que una rama de feature no mezclada, es un feature no terminado.El nombre de las ramas va en minúsculas.Las palabras se separan con-.Las ramas comienzan con alguno de los short lead tokens definidos, por ejemplo:feat/tokens-configurationShort lead tokensCommitsWIP = Trabajo en progreso.Ramasfeat = Nuevos featureschore = Tareas, que no son visibles al usuario.bug = Resolución de bugs.Todas las mezclas a master se hacen mediante Pull Request.TestPara ejecutar los test localmente debes usar el siguiente comando en una terminal.pipenvruntestsDeploy de una nueva versión.Para generar una nueva versión, se debe crear un PR (con un título "Prepare release X.Y.Z" con los valores que correspondan paraX,YyZ). Se debe seguir el estándar semver para determinar si se incrementa el valor deX(si hay cambios no retrocompatibles),Y(para mejoras retrocompatibles) oZ(si sólo hubo correcciones a bugs).En ese PR deben incluirse los siguientes cambios:Modificar el archivoCHANGELOG.mdpara incluir una nueva entrada (al comienzo) paraX.Y.Zque explique en español los cambiosde cara al usuario del SDK.Modificarversion.pypara que apunte a la nueva versiónX.Y.Z.Luego de obtener aprobación del pull request, debe mezclarse a master e inmediatamente generar un release en GitHub con el tagvX.Y.Z. En la descripción del release debes poner lo mismo que agregaste al changelog.Con eso Travis CI generará automáticamente una nueva versión de la librería y la publicará en PyPI.
Package: transbase
transbase-pythonPython database driver forTransbasebased on Transbase/TCI (Transase C/C++ call interface)implementing Python database api v2.0 (PEP-249)Python3.9Transbase8.xInstallTransbase is available inPyPipip install transbaseExamplefromtransbaseimporttransbase# connect to transbase databaseconnection=transbase.connect("//develop.transaction.de:8324/test","test","test")cursor=connection.cursor()cursor.execute("select no, text, date from test")# use native python data types in fetch result set (bool, int, float, bytes,...)# otherwise all values will be fetched as plain "str"cursor.type_cast=Truerow=cursor.fetchone()print(row)cursor.close()connection.close()DML statements (insert, update, delete) are executed similar.The number of affected rows can be obtained by.rowcountcursor.execute("insert into test ( text ) values ( '... kind regards' )");print(cursor.rowcount)# -> 1Query parameters can be passed as second argument# pass parameters as object matching named parameterscursor.execute("select no, text, date from test where no >= :no and text like :text",{"no":1,"text":"Hello%"})# or as an array for positional parameterscursor.execute("select no, text, date from test where no >= ? and text like insensitive ?",[2,"%kind%"])TroubleshootingTCI SDK not foundIf no prebuild binary wheel could be found on PyPi for your operating system or Python versionyou can simply download it after installation by running the python script(added with installation of this package)install_tciContributionVS-Code Editor with python extension is recommended.Developmentinstall python 3.9 (TODO: -> 3.11)it is recommended to install and use virtualenvpy -m pip install --user virtualenvinstall required dependenciespy -m pip install flake8 coverage requestsdownload tci libpy setup.py get_libTestpy -m unittestor use vs-code test explorerBuildSource distribution and wheel including tci sdkpy setup.py sdist [bdist_wheel]Manual ReleaseLinux wheels need to be renamed matchingPEP-600To publish manually to pypi (or testP) runtwine upload [--repository testpypi] dist/*
Package: transbeta
transliteratemodulePython module written in C++ to convert transliterated representation
of ancient languages to unicode (TLG's beta code and LaTeX cjhebrew
markup)This library converts “transliterated” representations of non-English
languages, like TLG's Beta Code, to unicode. Supported
transliterations are:o The Thesaurus Linguae Graecae’s Beta Code for Polytonic Greek,
Hebrew and Coptic.
o cjhebrew transliteration from the LaTeX package by that nameI don’t know much about Coptic, so the functions for that language
remain untested. The Beta Code representation for Hebrew does not
support vowel and diacritical marks by design, cjhebrew does.I’m only using thecjhebrewimplementation with some earnest. None
of the other codecs see production use here.Function definitions in Python would look like:defbetacode_greek_to_unicode(source,precombined=False,asterisk_syntax=False):"""If `precombined` is True, output unicode codepoints that havediacritical characters in them.If `asterisk_syntax` is used, upper case Greek letters are marked by a “*”,otherwise upper case Latin is mapped to upper case Greek.""""defcjhebrew_to_unicode(source):passdefbetacode_hebrew_to_unicode(source):# Untested!passdefbetacode_coptic_to_unicode(source):# Untested!passIf anyone finds this useful, please let me know your milage!Diedrich Vorbergdiedrich@tux4web.de
Package: transcal
TransCal: Transistor Analyzertranscalpackage include so popular transistor configuration.
It provides analysing transistors indcandacstates.FeaturesI've seperated this project into three main part:BJTAnalysisprovide analysis of bjt type transistors.JFETAnalysisprovide analysis of jfet type transistors.MOSFETAnalysisprovide analysis of mosfet type transistors.Also, there are some different methods for getting easy.Installationpip install transcalLicenseMIT License