Saravanan666/pypi-org huggingface dataset:
Package: bda.blogview
OverviewThis package contains a blog-like view. It allows you to use all Archtypes based
content to be viewed as blog entries, as long as they follow the specs of
bda.contentproxy.If commenting is allowed on an object, the comments are displayed as well. The
view provides commenting controls for the displayed objects directly.To make the blogview work, you have to provide an IBlogItemProvider implementing
object.Example:from zope.interface import implements
from zope.component import getMultiAdapter

from Acquisition import Explicit

from Products.CMFPlone.utils import getToolByName

from bda.blogview.interfaces import IBlogItemProvider
from bda.blogview.interfaces import IBlogItemIterator
from bda.blogview.atiterator import ATBlogItemQuery

class BlogItemProvider(Explicit):

    implements(IBlogItemProvider)

    def __init__(self, context, request):
        self.context = context
        self.request = request

    @property
    def items(self):
        putils = getToolByName(self.context.context, 'plone_utils')
        query = ATBlogItemQuery({
            'portal_type': putils.getUserFriendlyTypes(),
            'sort_on': 'modified',
            'sort_order': 'reverse',
        })
        iterator = getMultiAdapter((self.context, query), IBlogItemIterator)
        return [i for i in iterator]You have to register this implementation as follows:<adapter
  for="zope.interface.Interface
       zope.publisher.interfaces.browser.IBrowserRequest"
  provides="bda.blogview.interfaces.IBlogItemProvider"
  factory=".yourmodule.BlogItemProvider"
  name="blog"
 />Dependenciesplone 3cornerstone.ui.corecornerstone.ui.resultbda.contentproxyInstallationMake the dependent eggs available in your instance,Import extension profiles in your plone instance.CopyrightCopyright 2008, BlueDynamics Alliance, Austria -www.bluedynamics.comCreditsWritten byRobert NiederreiterSquarewave Computing, BlueDynamics Alliance, AustriaLicenceGNU General Public Licence 2.0 or later
Package: bda.cache
This package is designed to be used by applications which require different
kinds of caching flavour. This is abstracted due to the interfacesICacheProviderandICacheManager. ICacheProvider takes care of the
concrete cache implementation, ICacheManager is the read/write interface.The convention is to adapt a concrete ICacheProvider implementationfrombda.cacheimportICacheManagerfrombda.cacheimportMemcachedprovider=Memcached(['127.0.0.1:11211'])manager=ICacheManager(provider)We can ask the manager for data inside the cachedata=manager.get('somekey',force_reload=False)Ifforce_reloadis set to True, try to delete data with key from cache and
return None.We’re also able to manipulate the cache’s data (some restrictions my result out
of backend not providing them)manager.set('somekey',object())There exist a convenience to use some API’s and cache it’s results all at once.data=manager.getData(func,key,force_reload=False,args=[],kwargs={})First the data forkeyis looked up inside the cache provider. If not found
there or ifforce_reloadis set to True, call givenfunc. The return
value of this function will be stored in the cache provider.argsandkwargsare passed as parameters to given function if it’s call is required.You might ask why all this is done due to 2 seperate interfaces…Some usecase might require different cache providers i.e. for different payload
size. This way you can implement any other cache provider usage as well due to
the cache manager interface.Dependencieszope.interfacezope.componentbda.cache.fscache.FSCacherecommends that availability ofcpicklebda.cache.memcached.Memcachedrequirespython-memcachedNotesIf you’re interessted to contribute; Feel free but keep in mind that this code
is planned to be released under a BSD like licence in future.
Changes
——-1.3.0 (2019-02-05)Python 3 comaptibility [reinhardt]Code style (black/isort) [jensens]1.2.0 (2017-10-19)Change to use libmc or pylibmc when availableAdd option to require with bda.cache[pylibmc] or bda.cache[libmc]1.1.2 (2009-02-10)remove legacy code1.1.1 (2009-02-10)bugfix in zcml configuration.1.1 (2009-02-09)Cache Managers are now adapters.Implement memcached server supportdeprecate the default CacheManagerFix tests for FSCache1.0Initial work
Package: bdacore
What is this?BDA core library of data science and data manipulation functions.How do I install itFirst, make sure you have miniconda or anaconda installed. If not,install it!Then you can install bdacore by running:make installThis will install the main requirements for running the bdacore lib. If you use advanced methods, you may need to
install extra packages.If you want to install all required packages at once, then run:make develop_envYou may want to override the default package name (bdacore) and Python version (3.6). This can be done by overriding theENV_NAMEandENV_PY_VERSIONas follows:make develop_env ENV_NAME=bdacore_py2 ENV_PY_VERSION=2.7Where can I see some examples?Check thedocs. A good entry point is to check thetutorials!
Package: bda.disclaimer
bda.disclaimerCookie based access restriction for Plone sites.InstallationAddbda.disclaimerto installation dependencies and and install product.Provide the Disclaimer TextDisclaimer text is looked up viabda.disclaimer.interfaces.IDisclaimerTextadapter. The default implementation expects an document at Plone Site root with
Iddisclaimer. The Body Text of this Document is used as disclaimer
text.Customizing UITo provide your own disclaimer markup, the browser page nameddisclaimermust be overwritten.Copyright and ContributionsCopyright 2008-2013, Blue Dynamics Alliance -http://bluedynamics.comAuthor: Robert Niederreiter <rnix [at] squarewave [dot] at>
Contributions: Peter Holzer <hpeter [at] agitator [dot] com>Changes1.1Simplification, port to Plone 4.x
[rnix]1.0Initial work
[rnix, hpeter]LicenseCopyright (c) 2008-2013, BlueDynamics Alliance, Austria, Germany, Switzerland
All rights reserved.Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.Neither the name of the BlueDynamics Alliance nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY BlueDynamics AllianceAS ISAND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Package: bda.plone.gtm
=============bda.plone.gtm=============Google Tag Manager Integration.Installation and Configuration==============================- Depend your installation to ``bda.plone.gtm``.- Install ``bda.plone.gtm`` via Plone Add-ons control panel.- Naviagte to "Site Setup" -> "Add-on Configuration" -> "Google Tag Manager Settings".- Set "Enabled" checkbox and enter "Container ID". Optionally edit "Layer Name"to your needs. This integration package handles the layer name properly.Anyway you need to be aware that any 3rd party JS using this package maydepend hardcoded to the default layer name, so be careful with changing thissetting.Providing Data==============``bda.plone.gtm`` by default tracks nothing. To track something useful,``bda.plone.gtm.interfaces.IGTMData`` adapters needs to be provided for therelevant context.The adapter implementation looks like:.. code-block:: pythonfrom a.package.interfaces import IMyContextInterfacefrom bda.plone.gtm.interfaces import IGTMDatafrom zope.component import adapterfrom zope.interface import implementer@implementer(IGTMData)@adapter(IMyContextInterface)class MyContextGTMData(object):def __init__(self, context):self.context = context@propertydef data(self):# data is a dict or a list of dicts.return {'pageTitle': 'Home','visitorType': 'high-value'}Register the data adapter:.. code-block:: xml<configure xmlns="http://namespaces.zope.org/zope"><!-- GTM data adapter --><adapter factory=".data.MyContextGTMData" /></configure>Contributors============- Robert Niederreiter (Author)Changelog=========1.0a1 (2018-06-06)------------------- InitialLicense=======Copyright (c) 2018, BlueDynamics Alliance, AustriaAll rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:* Redistributions of source code must retain the above copyright notice, thislist of conditions and the following disclaimer.* Redistributions in binary form must reproduce the above copyright notice, thislist of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.* Neither the name of the BlueDynamics Alliance nor the names of itscontributors may be used to endorse or promote products derived from thissoftware without specific prior written permission.THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance ``AS IS`` AND ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Package: bda.portlet.sitenavigation
Yet another navigation portlet. This is quite similar tocollective.portlet.sitemap, except that there are slightly different
options. Likecollective.portlet.sitemap, it optionally allows you to
display the navigation tree expanded, like the sitemap does.This portlet is also optimized to work in Lineage sites, as it allows you to
root the navigation portlet from the portal root, the navigation root or the
current context.
Changelog
=========2.1 (2015-12-14)Make cache time configurable and set it to 0 seconds. 0 is no caching. There were some issues, where content changes did not reflect in the menus. A good value might be 10 seconds to avoid unnecessary recalculating.
[thet]2.0 (2015-07-15)Move all memoize-instance cached methods from plone.app.portlet’s navigation
portlet to this implementation to apply ram caching on it. Avoids some more
write-on-reads.
[thet]Get rid of write-on-reads and their conflicts by reducing the number of
instance memoizes.
[jensens]Cache the rendered portlet for an hour with sensible cache keys (portlet_id,
path, user) for maximum 1 hour.
[thet]Makesearch_baserequired, so that at least the first item of the
vocabulary is preselected.
[thet]Changecss_class_mainfrom a TextLine field to a Choice Field, making it
possible to choose from a vocabulary with nice sounding titles instead of
having to fill in CSS classes directly. Overrideable viaoverrides.zcml.
[thet]Switch toz3c.formfor theAddFormandEditForm.
[thet]Remove the browserlayer, which is nowhere used.
[thet]1.0 (2015-03-04)Initial version.
[thet]
Package: bda.resultduplexer
Overviewbda.resultduplexer provides duplexing of search results in plone. The original
intention were the needs to modify the url for proxied contents
(see bda.contentproxy package). This is also the behaviour of the default
duplexer. It looks if the user is authenticated, and if so, leave the object url
as is, otherwise modify the url pointing to the content proxy view of the
object.To implement your own duplexing logic, you have to provide an IResultDuplexer
implementing object. See bda.resultduplexer.interfaces for the API documentation
and bda.resultduplexer.duplexer how such an implementation can look like.To describe duplexed results, brain wrapper objects are used. The default
implementation modifies the URL of an object, if you want to modify
anything else of the result, you have to provide such an IBrainWrapper
implementing object as well.NoteThis module patches ATTopic!. This must be done to make the result duplexer
work on topics by calling:results = IResultDuplexer(self).prepareResults(results)For the common search behaviour, livesearch_reply and queryCatalog are replaced.
To be able to call the duplexer in restricted code, there is a browser view
implementation simply loops the call through:duplexer = context.restrictedTraverse('@@restrictedresultduplexer')
results = duplexer.prepareResults(results)InstallationMake the egg available in your instance,Import the bda.resultduplexer extension profile in your plone instance.Write your own duplexer. Look at bda.contenbtproxyThis Product is tested with Plone 3.0CopyrightCopyright 2008, BlueDynamics Alliance, Austria -
` bluedynamics.com <http://bluedynamics.com>`_CreditsWritten byRobert NiederreiterSquarewave Computing, BlueDynamics Alliance, AustriaRefactorings:Jens KleinBlueDynamics Alliance, Klein & Partner KEG, Innsbruck, AustriaLicenceGNU General Public Licence 2.0 or laterChangelog1.0 beta2[rnix] 2010-03-10resultduplexer depends now on bda.contentproxy.
Package: bdarpack
copula-tabularGenerate tabular synthetic data using Gaussian copulasOverview|Documentation|Contributing|Development notes|Copyright and licenseOverviewAdvancements in synthetic data generation have made it a viable solution for applications in various fields, such as finance, biomedical research, and data science. Synthetic data is generated artificially, yet replicates the joint probability distribution of its real-world counterpart. Its ability to mimic the statistical behaviour of real data makes it a useful tool for testing algorithms, systems, and training machine learning models, and it can be used as an economical substitute for real data when it is not available, is too sensitive to release, or too costly to acquire. Copula-based data generation methods have been demonstrated to produce reliable and accurate tabular data when generating synthetic data.In this package, we present a tool for generating multivariate synthetic data through the implementation of a Gaussian copula. This model incorporates conditional joint distributions into its framework, allowing for the splitting of single variables into multiple component marginal distributions. The conditional enhancements provides greater usability in the synthesis of complex, non-linear sample distributions, allowing for the replication of a wider range of datasets.The tool is designed to work with a data dictionary, or a file describing the metadata of the input dataset. There are additional class-based implementations of data cleaning, visualisation tools, transformation tools, privacy leakage evaluation, and sample wrapper scripts for generating synthetic data from start to finish.Example Result:Figure showing correlation plots of a simulated multivariate dataset, containing non-trivial, non-linear and non-monotonic relationships. The left plot shows the original Pearson correlation between variables, while the middle and right plots show the correlation for synthetic data generated using standard copula and conditional copula respectively.Figure showing superimposed scatterplots of the same simulated multivariate dataset, containing non-trivial, non-linear and non-monotonic relationships. The training, synthetic (standard copula), synthetic (conditional copula) data points are in blue, grey, and red respectively.DocumentationFor installation instructions, getting started guides and tutorials, background information, and API reference summaries, please see thewebsite.ContributingThank you for considering contributing to Synthia. Please follow thislinkfor more details.Development notesPlease visit thewebsitefor more details.Copyright and licenseCopyright 2023 BiomedDAR, BII, A*STAR. Licensed underMIT.
Package: bda.zeopack
bda.zeopackOverviewPacks one or more databases/ storages on one or more ZEO-Servers (Zope Database
Storages on Zope Enterprise Objects Server).CompatibilityTested with eggs releaes of ZODB2 >=3.8 and Zope 2.9, 2.10 (latest) as
tgz-release.InstallationInstall it usingeasy_installorzc.buildout. Example for zc.buildout:[buildout]
parts = zeopack

[zeopack]
recipe = repoze.recipe.egg:scripts
eggs = bda.zeopackIf youre using Zope with a version below 2.11 (like 2.10 or 2.9) the buildout
gets a bit more complex:[buildout]
parts = zope zeopack

[zope]
recipe = plone.recipe.zope2install
url = http://www.zope.org/Products/Zope/2.9.11/Zope-2.9.11-final.tgz
# url = http://www.zope.org/Products/Zope/2.10.9/Zope-2.10.9-final.tgz
fake-zope-eggs = true
additional-fake-eggs = ZEO

[zeopack]
recipe = repoze.recipe.egg:scripts
eggs = bda.zeopack
initialization = sys.path.append('${zope:location}/lib/python')UsageCreate a configuration file. If no location is given as first argument
bda.zeopack consider the file at/etc/zeopack.cfg.The format of the file follows Python ConfigParser format. It looks like:[MY.DOMAIN.TLD_OR_IP_ADDRESS:PORT]
day = NUMBER_OF_DAYS_TO_KEEP
storages =
    STORAGENAME
    STORAGENAMEExample:[127.0.0.1:8100]
days = 1
storages =
    storage1
    storage2
    storage4

[127.0.0.1:8200]
days = 7
storages =
    project1
    project2

[storage.bluedynamics.com:8100]
days = 1
storages =
    root1
    mountr1m1
    mountr1m2
    root2
    mountr2m1
 ...Todo:better parsing of argvsupport authenticationpipe file via stdin instead of filenameCreditsCopyright 2008-2010, BlueDynamics Alliance AustriaConcept and code
* Jens W. Klein <jens@bluedynamics.com>, Klein & Partner KGLicenseCopyright (c) 2008-2010, BlueDynamics Alliance, Austria
All rights reserved.Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.Neither the name of the BlueDynamics Alliance nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance ‘’AS IS’’ AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Package: bdbcontrib
# bdbcontribA set of utilities for bayesdb.## InstallingThe software in bdbcontrib requires:[bayeslite >=0.1.2](http://probcomp.csail.mit.edu/bayesdb/)[ipython notebook >=3](http://ipython.org/notebook.html)[markdown2](https://pypi.python.org/pypi/markdown2)[matplotlib](http://matplotlib.org/)[numpy](http://www.numpy.org/)[pandas](http://pandas.pydata.org/)[scikit-learn](http://scikit-learn.org/)[seaborn >=6](http://stanford.edu/~mwaskom/software/seaborn/)[tornado >=4](http://www.tornadoweb.org/en/stable/)The tests require:[mock](https://pypi.python.org/pypi/mock)[pillow](https://python-pillow.github.io/)[pytest](http://pytest.org/)The documentation requires:[numpydoc](https://pypi.python.org/pypi/numpydoc)[sphinx](sphinx-doc.org)Individual parts of bdbcontrib may have slimmer dependencies, if you
want to pull them out for more limited purposes.## TestTo run the paltry automatic tests:` $ ./check.sh `## InstallTo install system-wide, or into the current virtual environment:` $ python setup.py build $ python setup.py install `## DocumentationThe python documentation is built using [sphinx](http://sphinx-doc.org/) and
[numpydoc](https://pypi.python.org/pypi/numpydoc).` $ make doc `## UseIf you want the Python API,import bdbcontrib.plot_utils, &c.If you are using the bayeslite shell, load the bayeslite shell
commands with:` .hook /path/to/bdbcontrib/hooks/hook_plotting.py `
Package: bdbdatastore
bdbdatastore is an alternate datastore backend for App Engine apps. It’s far more robust and scalable than the one the development server uses, but not as big and hard to install as HBase and HyperTable based backends. bdbdatastore is intended primarially for use by people who want to host their own App Engine apps, and don’t expect datastore load for a single app to exceed what a single server can handle. In the event your app gets too big for bdbdatastore, the migration path to an alternate backend is smooth.
Package: bdbomdiff
BDBOMDIFFBlackduck BOM Diff to excel for AOSD importDescriptionThis is intended for finding new OSS component to be imported into AOSDGetting StartedDependenciesBlackduckimportlib-resourcesopenpyxlInstallingpip install bdbomdiffExecuting programHow to run the program<!-- on the folder it is running place this blackduck config file for blackduck library-->
.restconfig.json
{
    <!-- make sure Blackduck_url should not end with slash -->
  "baseurl": "Blackduck_url",
  "api_token": "API_KEY",
  "insecure": true,
  "debug": false
}

bdbomdiff PROJECT_NAME NEW_VERSION OLD_VERSION -o OUTPUT_DIRHelpAny advise for common problems or issues.>bdbomdiff -h
usage: Retreive BOM component info for the given project and version [-h] -o O [-l LIMIT | -u | -r] [-v] [-c] project_name version oldversion

positional arguments:
  project_name
  version
  oldversion

options:
  -h, --help            show this help message and exit
  -o O                  Output directory
  -l LIMIT, --limit LIMIT
                        Set limit on number of components to retrieve
  -u, --unreviewed
  -r, --reviewed
  -v, --vulnerabilities
                        Get the vulnerability info for each of the components
  -c, --custom_fields   Get the custom field info for each of the componentsAuthorsDinesh RaviVersion History0.3.0get license, homepage url, description, copyright and files info,0.2.0Documentation update0.1.0Initial ReleaseLicenseThis project is licensed under the MIT License - see theMITfile for detailsAcknowledgmentsopenpyxlBlackduckimportlib-resources