Saravanan666/pypi-org huggingface dataset:
Package: metapensiero.markup.semtext
Author:Lele GaifaxContact:lele@metapensiero.itlicense:GNU General Public License version 3 or laterImplement a minimalistic markup usable in the various descriptions, with just the needed
elements: headings and paragraphs containing plain,boldoritalictext,hyper
<link>and unordered lists.The internal representation is a tree of nodes, and a set of functions to transpose it to/from
a textual format, HTML andQuill Deltaare included.Changes0.28 (2022-12-27)Add compatibility with SLY 0.50.27 (2022-05-20)Do not fail badly on whitespace only outside a text node0.26 (2021-02-02)Suppress warning on unsupported HTML tags0.25 (2020-06-18)As an interim workaround to SemText limitation, represent “bolded links” as plain links0.24 (2020-05-21)Add option toparse_text()to fallback to plain text on parsing errors0.23 (2019-12-02)Ignore spurious orphan headers0.22 (2019-11-08)Ignore non-textual insert operations, such as “image”0.21 (2019-09-20)Explain assertion errors, to avoid meaningless logging messagesSuppress warning on ignored<pre>tags0.20 (2019-09-02)Ignorecode-blockattributes0.19 (2019-07-16)Workaround a degenerated case involving empty hrefs0.18 (2019-07-12)Completely ignore<iframe>and<script>tagsExtract <table> content as plain paragraph, to make them at least readable0.17 (2019-07-03)Ignore text attributes that we are not going to handle0.16 (2019-06-25)Handle HTML created with non-Unix end-of-line convention0.15 (2018-08-23)Ignore<style>tags and degenerated<a>tags0.14 (2018-08-23)Ignore<img>tags, out of scope at least for now0.13 (2018-08-23)Rewritten HTML parser, slightly more robust and versatile0.12 (2018-08-17)Try harder to handle degenerated paragraphs represented with DIVsReplace asserts with a custom exception to signal parsing errors0.11 (2018-08-15)Handle degenerated paragraphs represented with DIVsAdd an option to swallow HTML parsing exceptions and falling back to plain text0.10 (2018-08-01)Handle SPANs inside headings0.9 (2018-07-12)Ignore standalone BRs in the HTML parser0.8 (2018-07-12)Ignore BRs inside headings in the HTML parser0.7 (2018-06-26)Better handling of nested DIVs in the HTML parser0.6 (2018-06-13)Handle implicit list item indexes in SEMPrinter0.5 (2018-04-26)Properly escape also the link’s address0.4 (2018-04-26)Newescapeoption toHTMLPrinterthat by default useshtml.escape(text,
quote=True)to emit safe text spans0.3 (2018-04-20)Support for hyperlinksSupport for headingsNew function to emit a Quill Delta representation of an AST0.2 (2018-03-10)Fix HTML representation of numbered list items without a valueRaise a specific InvalidNestingError exception instead of generic AssertionError0.1 (2018-02-25)Renamed to metapensiero.markup.semtext0.0 (unreleased)Initial effort.
Package: metapensiero.recipe.script
This module implements two simple recipes to execute either ashellscript (actuallybatchscripts under M$-Windows) or a Python script.Both recipes take two options,installandupdate: both are considered as a list of
statements, one per line, that will be written in a temporary file that will be executed
respectively when the recipe is installed or updated. One or the other may be missing, and in
such case nothing will happen for that particular step.When the commands to execute depend on the platform, they can be specified using the optionsinstall-linuxorinstall-win32that have higher priority than the generic form.Shell scriptsThemetapensiero.recipe.script:shellrecipe is implemented by theShellScriptclass,
and can be used in the following way:[config]
recipe = metapensiero.recipe.script:shell
ini = config.ini
install = ${buildout:bin-directory}/soladmin create-config ${:ini}As said, some time the commands to execute depend on the particular platform they are run. In
such cases, you can say:[config]
recipe = metapensiero.recipe.script:shell
ini = config.ini
install = ${buildout:bin-directory}/soladmin create-config ${:ini}
install-win32 =
   ${buildout:bin-directory}/soladmin create-config ${:ini}
   echo Configuration created!
   pausePython scriptsThemetapensiero.recipe.script:pythonrecipe is implemented by thePythonScriptclass. It is somewhat more powerful because it can easily access the whole buildout
configuration.Consider the following example:[start_script]
recipe = metapensiero.recipe.script:python
install =
  >>> import sys
  >>> from os.path import join
  >>> basedir = buildout['buildout']['directory']
  >>> bindir = buildout['buildout']['bin-directory']
  >>> script = join(basedir, 'sol.bat' if sys.platform=='win32' else 'sol.sh')
  >>> config = join(basedir, buildout['config']['ini'])
  >>> with open(script, 'w') as f:
  >>>   if sys.platform == 'win32':
  >>>     f.write('@echo off\n')
  >>>   f.write('%s %s\n' % (join(bindir, 'solserver'), config))
  >>> installed = scriptAs you can see, the script can access other section settings thru thebuildoutlocal
variable, a dictionary that contains the whole buildout configuration. Another local variable
isoptions, another dictionary containing the recipe settings.The script may set theinstalledvariable, that can be either a simple scalar string value
or a sequence of strings: it will be used as the result of the recipe, which usually is the
list of the files/directories installed by the recipe itself that will be deleted whenever the
recipe is removed from the configuration.Using eggsIf the Python script uses additional eggs, they can be specified with theeggsoption, like
in the following example:[extjs]
recipe = metapensiero.recipe.script:python
eggs = metapensiero.extjs.desktop
install =
  >>> from metapensiero.extjs.desktop.scripts.extjs_dl import download_and_extract, URL
  >>> download_and_extract(URL)Changes1.2 (2014-03-08)Simple test suiteFix return of installed stuff in Python scripts1.1 (2014-03-08)First release on PyPI1.0 (2014-03-08)Initial version, extracted from SoLista
Package: metapensiero.sphinx.autodoc-sa
author:Lele Gaifaxcontact:lele@metapensiero.itlicense:GNU General Public License version 3 or laterThis is a very simple extension toSphinxthat injects the ability to recognize and pretty
printSQLAlchemystatements into itsautomoduleand autoclass directives.To use it, first of all you must register the extension within the Sphinx environment, adding
the full name of the package to theextensionslist in the fileconf.py, for example:# Add any Sphinx extension module names here, as strings.
extensions = ['metapensiero.sphinx.autodoc_sa']Without further settings it uses the default SQLAlchemystringification strategy, but you
can explicitly choose the rightdialectby settingautodoc_sa_dialectto a string
containing its fully qualified name, for example:autodoc_sa_dialect = 'sqlalchemy.dialects.postgresql.dialect'Otherwise, you can set it using the-Doption of thesphinx-buildcommand, e.g. adding-Dautodoc_sa_dialect=my.own.dialectto theSPHINXOPTSof the Makefile created bysphinx-quickstart.At this point, any documented SQLAlchemy core statement or ORM query, appearing either at the
module level or as a class attribute, will becompiledinto SQL, beautified usingsqlparse.format()and added to the documentation wrapped within acode-block::sqldirective.If you chose a specific SQLAlchemy dialect, by any chance you may want to select the right
Pygmentslexerto adjust the highlighting rules, instead of the defaultsql:autodoc_sa_pygments_lang = 'postgresql'If you are usingPostgreSQL, you may prefer using thepglastSQL prettifier over the
default one based onsqlparse:autodoc_sa_prettifier = 'pglast'Changes2.1 (2019-03-31)Minor tweak for compatibility with recently released Sphinx 2.02.0 (2018-06-16)ImportantGiven that the PostgreSQL-specific prettifier has been renamed frompg_querytopglast, I opted to reflect the fact on the value of theautodoc_sa_prettifieroption: if you were using that tool, you must change
it topglast.Sorry for the inconvenience.1.7 (2018-05-24)Avoid prettification of BindParameters1.6 (2018-05-23)Use Sphinx 1.7+ API to install the extension1.5 (2017-08-10)New optionautodoc_sa_prettifier_optionsto pass arbitrary keyword options to the
prettifier function1.4 (2017-08-09)Replace the dynamic argument placeholders injected by SA with their literal values, leaving
the developer’s explicit bindparams alone1.3 (2017-08-08)Handle also thepglastSQL prettifierNew options,autodoc_sa_prettifierandautodoc_pygments_lang1.2 (2017-03-22)Minor tweak, no externally visible changes1.1 (2017-01-17)First release on PyPI1.0 (unreleased)Polished, tested and extended to support class’ attributes as wellExtracted from metapensiero.sphinx.patchdb
Package: metapensiero.sqlalchemy.asyncio
Theaiopgandaiomysqlprojects allow to operate asynchronously withPostgresQLandMySQL, respectively, even thruSQLAlchemy. Their
approach isn’t ideal, though, because they reimplement a considerable
amount of SA low level stuff with undesirable glitches.TheTwistedbasedAlchimiaway is much lighter and even if maybe
slightly less performant it does not introduce unexpected surprises.UsageBasically the module wraps a minimal set of SA classes (currently justEngine,Connection,TransactionandResultProxy) into
asyncronous counterparts, and you work on them like the following
example:from asyncio import coroutine
from metapensiero.sqlalchemy.asyncio import create_engine

@coroutine
def do_something(db_url):
    engine = create_engine(db_url)
    with (yield from engine.connect()) as conn:
        with (yield from conn.begin()) as trans:
            yield from conn.execute(users.insert()
                                    .values(id=42, name="Async",))

        res = yield from conn.execute(users.select()
                                      .where(users.c.id == 42))
        rows = yield from res.fetchall()

        res = yield from conn.execute(users.delete()
                                      .where(users.c.id == 42))
        assert res.rowcount == 1If you are using Python 3.5 or better, the above should be written as:from metapensiero.sqlalchemy.asyncio import create_engine

async def do_something(db_url):
    engine = create_engine(db_url)
    async with await engine.connect() as conn:
        async with await conn.begin() as trans:
            await conn.execute(users.insert()
                               .values(id=42, name="Async",))

        res = await conn.execute(users.select()
                                 .where(users.c.id == 42))
        rows = await res.fetchall()

        res = await conn.execute(users.delete()
                                 .where(users.c.id == 42))
        assert res.rowcount == 1TestsTo run the unit tests, you should:create a Python virtual environment and install this package in
development mode:python3 -m venv env
source env/bin/activate
python setup.py developinstallpytest,pytest-asyncioand eitherpsycopg2-binaryorpymysql:pip install pytest pytest-asyncio psycopg2-binary pymysqlcreate a test database, for example withcreatedb testdbexecute thepy.testrunner with an environment variable with
the SA URL of the db:TEST_DB_URL="postgresql://localhost/testdb" py.test tests
TEST_DB_URL="mysql+pymysql://localhost/testdb" py.test testsChanges1.0 (2018-07-01)Renamed to metapensiero.sqlalchemy.asyncio0.4 (2015-09-25)Packaging tweaks0.3 (2015-09-23)Support Python 3.5 asynchronous context managers0.2 (2015-09-09)First (usable) distribution on PyPI0.1 (private)Works reasonably well!0.0 (private)Initial effort.
Package: metapensiero.tool.bump_version
author:Lele Gaifaxcontact:lele@metapensiero.itlicense:GNU General Public License version 3 or laterThis is a very simple tool that I use to automatize the management of theversion.txtfile
I usually put in my Python packages. There are tons of equivalent tools around, but none of
them fullfilled my needs.It uses the packageVersioto handle different versioning schemas, with an additionalsimple2scheme for versions composed simply bymajor.minornumbers.Examples:$ echo "0.0" > version.txt
$ bump_version --dry-run
Old version: 0.0
New version: 0.1

$ bump_version -n --field major
Old version: 0.0
New version: 1.0

$ echo "0.0.0.0" > version.txt
$ bump_version -f minor --scheme simple4
$ cat version.txt
0.1.0.0

$ echo "0.9" > version.txt
$ bump_version -n -f release --index 1 -s pep440
Old version: 0.9
New version: 0.10

$ bump_version -f release -i 1 -s pep440
$ cat version.txt
0.10

$ bump_version -n -f pre -i 1 -s pep440
Old version: 0.10
New version: 0.10a1

$ bump_version -n -f post -i 1 -s pep440
Old version: 0.10
New version: 0.10.post1

$ bump_version -f post -i 1 -s pep440
$ bump_version -n -f dev -i 1 -s pep440
Old version: 0.10.post1
New version: 0.10.post1.dev1The version scheme is by default automatically determined from current version (justsimpleversions though):$ echo "1.0" > version.txt
$ bump_version -n
Old version: 1.0
New version: 1.1

$ echo "1.0.0" > version.txt
$ bump_version -n
Old version: 1.0.0
New version: 1.0.1

$ echo "1.0.0.0" > version.txt
$ bump_version -n
Old version: 1.0.0.0
New version: 1.0.0.1The current version may not exist yet, but obviously you must specify the right schema:$ rm -f version.txt
$ bump_version -n -s simple2
Old version: 0.0
New version: 0.1

$ bump_version -s simple3
$ cat version.txt
0.0.1Changes1.3 (2017-03-22)Minor adjustments to take off the dust1.2 (2016-03-23)New option to automatically select the versioning schema, when one existsNew simple test suite1.1 (2015-09-09)Properly include needed sources in the distribution1.0 (2015-08-09)Reimport from metapensiero.extjs.desktop
Package: metapho
metaphoA keyboard-driven app for tagging and organizing large numbers of photos efficiently.This arose out of myPhoimage viewer (Pho on GitHub).
It started to get unwieldy adding ever more tagging features to what
was intended as just a fast, light image viewer.Metapho is intended as a lightweight, flexible way of organizing
large numbers of photos. It uses text files, not a proprietary database,
so you're not locked down to one app or a proprietary database,
and you can view your tags databases at any time, or edit them in a
text editor if you should ever want to.Metapho can be driven entirely from the keyboard: you should be able
to do everything you need without moving your hands to the mouse,
though you can use the mouse if you find that easier.It depends on PyGTK, but not on gnome or any other desktop services.It includes a program called "notags" that you can run to examine
the current directory recursively and tell you about files and
directories that still need to be tagged. Run it at the root of
an image directory that might have untagged subdirectories.Metapho is available on PyPi,
so you can install it aspip install metapho.Read theMetapho Documentationfor more information on both the app and the API of the classes
inside it.
Package: metaphor-connectors
Metaphor ConnectorsThis repository contains a collection of Python-based "connectors" that extract metadata from various sources to ingest into theMetaphorplatform.InstallationThis package requires Python 3.8+ installed. You can verify the version on your system by running the following command,python-V# or python3 on some systemsOnce verified, you can install the package usingpip,pipinstall"metaphor-connectors[all]"# or pip3 on some systemsThis will install all the connectors and required dependencies. You can also choose to install only a subset of the dependencies by installing the specificextra, e.g.pipinstall"metaphor-connectors[snowflake]"Similarly, you can also install the package usingrequirements.txtorpyproject.toml.DockerWe automatically push adocker imageto Docker Hub as part of the CI/CD. Seethis pagefor more details.GitHub ActionYou can also run the connectors in your CI/CD pipeline using theMetaphor ConnectorsGitHub Action.ConnectorsEach connector is placed under its own directory undermetaphorand extends themetaphor.common.BaseExtractorclass.Connector NameMetadataazure_data_factoryLineage, PipelinebigquerySchema, description, statistics, queriesbigquery.lineageLineagebigquery.profileData profilecustom.data_qualityData qualitycustom.governanceOwnership, tags, descriptioncustom.lineageLineagecustom.metadataCustom metadatacustom.query_attributionsQuery attritutionsdatahubDescription, tag, ownershipdbtdbt model, test, lineagedbt.clouddbt model, test, lineagefivetranLineage, PipelineglueSchema, descriptionlookerLooker view, explore, dashboard, lineagekafkaSchema, descriptionmetabaseDashboard, lineagemonte_carloData monitormssqlSchemamysqlSchema, descriptionnotionDocument embeddingspostgresqlSchema, description, statisticspostgresql.profileData profilepostgresql.usageUsagepower_biDashboard, lineageredshiftSchema, description, statistics, queriesredshift.lineageLineageredshift.profileData profilesnowflakeSchema, description, statistics, queriessnowflake.lineageLineagesnowflake.profileData profilesynapseSchema, queriestableauDashboard, lineagethought_spotDashboard, lineagetrinoSchema, description, queriesunity_catalogSchema, descriptionunity_catalog.profileStatisticsDevelopmentSeeDevelopment Environmentfor more instructions on how to set up your local development environment.Custom ConnectorsSeeAdding a Custom Connectorfor instructions and a full example of creating your custom connectors.
Package: metapic
metapicCommand line tool for modifying picture metadata from file/folder names and config.Featuresmetapicis a single file Python projectInstallYou can installmetapicusingpipwithpip3installmetapicor you can simply downloadmetapic.pyand then run it usingpython3withpython3metapic.pyHistory0.1.0 (2020-08-07)Created usingcookiecutter-pyscriptCreditsMain developer is luphordluphord@protonmail.com.cookiecutter-pyscriptis used as project template.History0.1.0 (2020-08-07)Initial release.
Package: metaplanet-room-chat
Metaplanet房间聊天客户端使用说明frommetaplanet_room_chat.clientimportdoConnectfrommetaplanet_room_chat.handlersimportencodePacket,Cmdsdefon_receive(packet,wsapp,config):print(f"收到报文:{packet}")data={"roomId":75800,"content":"我是python bot, 大家好"}sendPack=encodePacket(Cmds["ROOM_MSG_SEND_C"],data=data)wsapp.send(sendPack)doConnect(ws="ws://assets.tpulse.cn/metacat/api/websocket/chat-proxy",token="eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiI3NDcwMCIsImF1ZCI6IkNoYXQgUHJveHkiLCJuYmYiOjE2ODk2NDIwNDUsImlzcyI6Imh0dHBzOi8vdHBsYW5ldC5ydWl4aS1zaC5jb20vIiwiZXhwIjoxNjkyMjM0MDQ1LCJlbnYiOiJmYXQiLCJpYXQiOjE2ODk2NDIwNDUsImp0aSI6IjIzYmRjY2VlLTM1OTMtNGUxYS1iMjM5LTQ0MjY4OWNjMTlhZCJ9.MLjUHZdz7ANQ5jYlH-uFPJ3N3pkBWulQUPwlPxcl7iU",roomId=75800,uid=74700,on_receive=on_receive)
Package: metaprocessor
MetaProcessorMetaProcessor, all-in-one data pipeline for MbientLab MetaWear series sensors!GuideFor documentations about seting up, running, developing MetaProcessor, please visit our documentation site athttps://metaprocessor.org.LicenseGenerated byPowered byProject ofISS LabandBateman Horne Center.© 2023MetaProcessor contributors.Licensed under theMIT License.
Package: metaproject
MetaprojectScaffold new projects from Jinja2 templates, *e.g., running...metaprojectinitwenkokke/metaproject-haskell\--project=my-project\--github_username=wenkokke\--github_repository=my-project... creates ...test
├── .github
│   ├── workflows
│   │   └── ci.yml
│   └── dependabot.yml
├── dist-newstyle
│   └── cache
├── src
│   └── Test.hs
├── test
│   └── Spec.hs.jinja2
├── .python-version
├── ChangeLog.md
├── README.md
├── bumpver.toml
├── cabal.project
├── hie.yaml
├── pre-commit-config.yaml
├── requirements-dev.txt
└── test.cabal
Package: metapy-toolbox
pacotepypiExample of PyPI package.Getting StartedDependenciesYou need Python 3.7 or later to usepacotepypi. You can find it atpython.org.
You also need setuptools, wheel and twine packages, which is available fromPyPI. If you have pip, just run:pip install setuptools
pip install wheel
pip install twineInstallationClone this repo to your local machine using:git clone https://github.com/caiocarneloz/pacotepypi.gitFeaturesFile structure for PyPI packagesSetup with package informationsLicense example
Package: metaq
#介绍淘宝开源MQ–[metaq](https://github.com/killme2008/Metamorphosis)的python客户端，目前只支持发送消息功能。#安装python setup.py install#使用使用很简单:from metaq.producer import Message,MessageProducer,SendResult
p=MessageProducer(“avos-fetch-tasks”)
message=Message(“avos-fetch-tasks”,”http://www.taobao.com”)
print p.send(message)
p.close()如果你的zookeeper不是`localhost:2181`，可设置zk_servers属性:p=MessageProducer(“avos-fetch-tasks”,zk_servers=”192.168.1.100:2191,192.168.1.101:2181”)更多信息参考metamorphosis.py#协议
[The MIT License](http://www.opensource.org/licenses/mit-license.html)
Package: metaqueue
metaqueueGoalEfficiently run tasks concurrently and write metadata to a repository and write metainformation in a PostgresSQL database.How to install itpip install metaqueueHow to use itCreate tasks with any signature you like but this function has to fulfill two requirements, one is that you have to pass ametadataengineinto the task and the other is that you have to declare it as async.In order to push metadata to the metadataengine, you can use the following:metadataengine.publish_to_topic(Metadata(data,name,location,context))The metadata is associated to a topic which defines what kind of metadata is collected by the metadataengine. Metadata consists of 4 attributes, the data itself, the name, the location and a context.
Note that a metadataengine is defined asMetadataEngine(topic,queue)where topic is an enum element and queue is a metaqueue. A metaqueue is like a queue but with extra functionality. You don't have to worry about it but it is useful to know how a metaqueue is defined.MetaQueue(buffer_size=3,dtype=int)You can provide abuffer_sizewhich is the maximum capacity of the queue anddtypespecifies which kind of data can be stored in it.
3. Now, you are ready to kickstart theTaskRunnerwhich is running the defined tasks concurrently. You can use it in the following wayawaitTaskRunner.run(async_funcs=[task1,task2],args=[task1_args,task2_args])where the arguments are given as tuples into the listargs. In this step, the tasks are not only run concurrently but also the metadata are collected via the metadataengine.
4. Afterwards, we can define a Metabroker which will then push the metadata to a repository and push the information associated to the metadata into the PostgreSQL database.connector=StoreToLocalhost(path="./log.txt")metastore=MetaStore(**db_info)metabroker=MetaBroker(metadataengines=[engines[0],engines[1]],metastore=metastore,connector=connector)metabroker.run(timeout=10)Up until now, only one connector is supported and that is a local file where the metadata gets written to. Since the MetaStore is using PostgreSQL as a database, you have to provide a running instance of that database. The easiest way is to spin up a docker container and pass the connection information to the MetaStore asdb_info.db_infois a dict which contains the following keys: host, database, user, password, port. On the run method of the metabroker you can define atimeout. This should prevent running the metabroker for too long.
5. View the result, inside of your PostgreSQL database you should find your database with a tablemetadatain which you can find all the information associated to your metadata. Also, the log file should be created and contain all the metadata in a format which resembles the OpenMetrics format.
Package: metar
Metar is a python package for interpreting METAR and SPECI weather reports.METAR is an international format for reporting weather observations.
The standard specification for the METAR and SPECI codes is given
in the WMO Manual on Codes, vol I.1, Part A (WMO-306 I.i.A).  US
conventions for METAR/SPECI reports are described in chapter 12 of
the Federal Meteorological Handbook No.1. (FMC-H1-2017), issued by
NOAA.  Seehttp://www.ofcm.gov/publications/fmh/FMH1/FMH1.pdfThis module extracts the data recorded in the main-body groups of
reports that follow the WMO spec or the US conventions, except for
the runway state and trend groups, which are parsed but ignored.
The most useful remark groups defined in the US spec are parsed,
as well, such as the cumulative precipitation, min/max temperature,
peak wind and sea-level pressure groups.  No other regional conventions
are formally supported, but a large number of variant formats found
in international reports are accepted.