Saravanan666/pypi-org huggingface dataset:
Package: wikiseriesricardolib
Library to use wikipedia to query tv series episode lists.Documentation:https://wikiseriesricardolib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (25-05-2023)First code creation0.1.0 (25-05-2023)First Release.
Package: wikiseriessjoerdlib
A libary interfacing with Wikipedia to retrieve tv series information.Documentation:https://wikiseriessjoerdlib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (26-04-2023)First code creation0.1.0 (26-04-2023)Initial functionality.0.1.1 (26-04-2023)Fixing main branch and import0.1.2 (26-04-2023)Change file to main module and fix import.
Package: wikiseriessjoerdtoolcli
A cli tool to use wikipedia to retrieve tv series informationDocumentation:https://wikiseriessjoerdtoolcli.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (01-05-2023)First code creation0.1.0 (01-05-2023)Initial Functionality.0.1.1 (01-05-2023)Added help text for CLI arguments.
Package: wikiseriesstijnlib
Library to use wikipedia to query tv series episode lists.Documentation:https://wikiseriesstijnlib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (25-05-2023)First code creation0.1.0 (25-05-2023)first release.0.1.2 (25-05-2023)retry
Package: wikiseriesvincentlib
[a view of series in my last life]Documentation:https://wikiseriesvincentlib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (25-05-2023)First code creation
Package: wikiserieswillemcli
A template to create python librariesDocumentation:https://wikiserieswillemcli.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (01-05-2023)First code creation
Package: wikiserieswillemlib
A library for parsing Wiki seriesDocumentation:https://wikiserieswillemlib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (01-05-2023)First code creation0.1.0 (01-05-2023)Initial code release0.2.0 (01-05-2023)Fix dependencies
Package: wikiservice
WikiServiceLightweight python library for simple MediaWiki-API requests.Example of usagefromwikiserviceimportAPIServices=APIService.WikiAPIService(username='John Doe',password='seceretpass',domain='INC-DOMAIN',api_url='https://wiki-url.org/api.php')s.login()s.createPage(title='Sample page',text='There is a sample text')s.logout()
Package: wikisource
WikiSourcewikisource is a python package to help search theWikisource BooksIt offers a few classes to help find sentences in a book, or in a book collection.For example, to search in a book for a specific stringfrom wikisource import WikiSource

book = WikiSource("https://fr.wikisource.org/wiki/Discours_de_la_m%C3%A9thode_(%C3%A9d._Cousin)"
book.search("bon sens")To search in a collection of books, you can use:from wikisource import Collection, WikiSource

books = Collection([WikiSource("https://fr.wikisource.org/wiki/Discours_de_la_m%C3%A9thode_(%C3%A9d._Cousin)"),
                    WikiSource("https://fr.wikisource.org/wiki/Les_Confessions_(Rousseau)"),
                    WikiSource("https://fr.wikisource.org/wiki/L%E2%80%99Origine_de_la_Trag%C3%A9die")])

books.search("bon sens")The first search takes longer due to the fact that every chapter of the book needs to be downloaded locally. The next searches are faster.
Package: wikitable
Takes a wikipedia URL with a table in the webpage and returns a dataframe or list of dataframes if there are multiple tables in the webpage.Installationpip install wikitableOr from source:python setup.py installFunctionswikitable(url, to_csv=False, table_number=[None], overwrite = False, names = None)
This function will scrape every table in the wikipedia URL if no table_numbers are specified.Parametersurl: (Required) URL of the wikipedia webpage as a string.to_csv: boolean value that saves each table to a CSV if changed to True. Default is False.table_number: int of list of ints. The table number you want to scrape. Defaults to scrape all tables.overwrite: boolean value that will overwrite a CSV if there is one with the same name. Default is False.names: string or list of strings for what the CSV(s) will be named. Default names for the CSV(s) are table1.csv, table2.csv, etc…ReturnsReturns a Pandas Dataframe or a list of Pandas Dataframes if multiple tables are scraped.Examplefrom wikitable import wikitableurl = ‘https://en.wikipedia.org/wiki/List_of_countries_by_literacy_rate’df = wikitable(url, to_csv=True, overwrite=True, table_number=2)
Package: wikitablewrapper
wikitablewrapperInstall virtual ennvironment of python3sudoapt-getinstallcurl
sudoaptinstallpython3-pip
sudoaptinstallvirtualenv
virtualenvenv--python=python3cdenv&&sourcebin/activateInstall dependenciespip3installsimplejson
pip3installxmltodictInstall locally DBpedia SpotlightUbuntusudosnapinstalldockeror Debianwgethttps://download.docker.com/linux/debian/dists/jessie/pool/stable/amd64/docker-ce_17.03.0~ce-0~debian-jessie_amd64.deb
sudodpkg-idocker-ce_17.03.0~ce-0~debian-jessie_amd64.debSee if you have the image already in your computersudodockerimagelsif you don't have it, then runsudodockerpulldbpedia/spotlight-english
sudodockerrun-d-p2222:80dbpedia/spotlight-englishspotlight.shIf you have to stop it, see the CONTAINER ID, and then do itsudodockercontainerls
sudodockerstopCONTAINER_IDtest itcurlhttp://localhost:2222/rest/annotate-H "Accept: application/json"   --data-urlencode "text=Brazilian state-run giant oil company Petrobras signed a three-year technology and research cooperation agreement with oil service provider Halliburton."   --data "confidence=0.3"   --data "support=20"To install this package, just run:pip3install-ihttps://test.pypi.org/simple/wikitablewrapperHow use it?wt=WikitableWrapper(20)wt.createHtmlFile=Truewt.includeBabelfy=Truewt.includeTagme=Truewt.includeFremeNer=Truewt.includeDBpediaSpotlightLocal=True# you can do, eitherwt.outputFolder="1Out"# Optionalwt.processJson("1Tablas/1003231_2.json")# orwt.ProcessFolderOfJson("100Tablas","100Out")See below an example of how use the Benchamrk classwb=WikitableBenchmark()dSys={"Babelfy":"_babelfy","TagME":"_tagme","FremeNER":"_fremener","DBpedia Spotlight":"_dbpst"}wb.MeasureF1_and_Summarize("100Tablas","100Out",dSys,"100Benchmark")
Package: wiki-template
wikiis is a rewrite of django-simplewiki,
a project from 2009 that aimed to be a base system for a wiki.Template Plugin[NEED TO TRANSLATE]模板插件类似于 MediaWiki 的模板，通过定义模板可在多个文章中使用。Installpip installwiki-templateand create your django project.SettingsInsert “wiki_template” toINSTALLED_APPSbefore “wiki.plugins.*”:INSTALLED_APPS = (
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    'django.contrib.sites',
    'django.contrib.humanize',
    'sekizai',
    'sorl.thumbnail',
    'django_nyt',
    'wiki',
    'wiki.plugins.macros',
    'wiki.plugins.help',
    'wiki.plugins.links',
    'wiki.plugins.images',
    'wiki.plugins.attachments',
    'wiki.plugins.notifications',
    'wiki_template',
    'mptt',
)[NEED TO TRANSLATE]设置WIKI_MARKDOWN_KWARGS配置项的 “safe_mode” 键为False，这样可以在文章和模板中使用html标签:WIKI_MARKDOWN_KWARGS = {
    #'extensions': [
    #    ....
    #],
    "safe_mode": False,
}Bug reportAny issues report toGithub.
Package: wiki_terminal
Install:you can install it by: python install setup.pyor simply: pip install wiki_terminalHelp:use help for helpsummary arg to get summary about the argsearch arg to search arg on wikirandom s(summary)to get a random tittle (you can get summary about it if you want.)geosearch latitude longitude (radius) Do a wikipedia geo search for latitude and longitude using.Version:Version 1.0.0 basic function builtVersion 1.0.1 the geosearch function is addedVersion 1.1.0 the keyword-highlight function is addedversion 1.1.1 the search function bug fixed and history function addedversion 1.2.0 rewrite wiki_terminal by using prompt-toolkit
Package: wikitext-asymptote
Wikitext AsymptoteCustom wikitext parser to produce html, plain text fields and relevant links from wikipedia page source code.Get startedTo install thewikitext_asymptotepackage, simply runpip install wikitext_asymptoteYou can then use the package as follows:import wikitext_asymptote as wa

# Raw wikitext goes here
page = """..."""

# Parse it
parsed_page = wa.parse_page(page)

# parsed_page contains fields for html, plain text or links
print(parsed_page)

# parsed_page = {
#     'html': '...',
#     'text': '...',
#     'opening_text': '...',
#     'auxiliary_text': [...],
#     'heading': [...],
#     'links': [...]
# }AboutThis package was created to fulfill the precise needs for parsing wikitext in the context of theEPFL Graphproject, which are a bit more involved than the defaults frommwparserfromhell.However, the task of parsing wikitext taking into account all its syntax is gigantic. Already deciding, not even implementing, the parsing of each template in the myriad that's available, with all its variations, is virtually unfeasible.Hence, the approach we have decided to commit to is that ofapproximation(henceAsymptote). We try to parse a number of templates, tags and other entities as correctly as possible, in a way thatmostcases are covered. In addition, we also have defaults, which may or may not be adequate for some cases. This implies that the parsed output is not perfect, and that is by design. From that point on, we work on a case-by-case basis to include parsing for new templates, tags or other entities, should the need arise.AcknowledgementsWikitext asymptote is built on top of themwparserfromhellpackage, so we acknowledge and are grateful for the work of their creators.
Package: wikitexthtml
wikitexthtmlwikitexthtml is a library that renders HTML from WikiText.DependenciesPython3.8 or higher.python-slugify(viasetup.py), for slugs in anchorsply(viasetup.py), to implement{{#ifexpr}}and{{#expr}}wikitextparser(viasetup.py), to make sense of wikitextInstallationpipinstallwikitexthtmlOr for development work:python3-mvenv.env
.env/bin/pipinstall-e.UsageExtendPageby implementing the missing functions as seen inprototype.py.
This way you can customize where files are read from (from disk, from a database, etc) and how to sanitize titles and URLs.
In thetestsfolder examples of this can be found.Now you can instantiate this new class and callrender()on it.
The result will be available inhtml. For example:classWikiPage(Page):...print(WikiPage("Main Page").render().html)