Saravanan666/pypi-org huggingface dataset:
Package: pyramid_chameleon
These are bindings for theChameleon templating systemfor thePyramidweb framework.  Seehttp://docs.pylonsproject.org/projects/pyramid_chameleon/en/latest/for
documentation.0.3 (2014-07-01)Remove dependency onpyramid.interfaces.ITemplateRenderer(which is
deprecated in Pyramid > 1.5).Update Trove classifiers and tests to support Python 3.4.0.2 (2014-02-09)Dropped dependency onnose-selecttests.0.1 (2013-09-07)Initial version
Package: pyramid_chameleon_genshi
pyramid_chameleon_genshiBindings for Chameleon Genshi-style templating support underPyramid.  See theChameleon websiteforchameleon.genshitemplating language
details.Visit thePyramid documentation <http://docs.pylonsproject.org/>for more
information.pyramid_chameleon_genshi0.6 (2001-04-10)Addedtox.inifor testing.Removed dependency onpyramid_zcml.Added dependency on Chameleon<1.999 (Genshi support is not present in
Chameleon 2).0.5 (2011-01-31)Fix documentation bugs; add anincludemefunction so the package can be
included like others.0.4 (2011-01-18)Depend on Pyramid 1.0a10+ (ZCML).0.3 (2011-01-08)Use os.path.normpath instead of os.path.realpath to get a canonical filename
for XInclude fragments. This prevents many lstat(2) calls for every template
use.0.2 (2010-11-16)Bring up to date with Pyramid 1.0a3+template_renderer_factorychanges.0.1 (2010-11-05)Forked from repoze.bfg.chameleon_genshi 0.3.
Package: pyramid-clamav
pyramid_clamavPyramid tween which checks file uploads for viruses using clamav.You need to have a running clamav installation on your system to which
the tween can connect via a unix socket. You can set the socket path in
your config (pyramid_clamav.socket), but the defaults should work on most
systems.If you want to deactivate scanning (i.e. for testing or your local development
environment), you can set pyramid_clamav.debug to a value. Then flash- and
logmessages are generated if there was a file uploadandclamav is not
properly configured.If a virus was found, the file is removed from the request. The field which
was used to upload the file should handle it like no file was uploaded.A flashmessage is presented to the user stating that a file contained a virus
and it has been removed.It should also work for multiple files.This project was conceived by Daniel Havlik (dh@gocept.com).pyramid_clamav0.9 (2022-03-04)Ignore csrf tokens which look like base64 encoded files.0.8 (2021-09-17)Remove Python 2 support.Check application/json requests for viruses.0.7 (2020-01-10)Bugfix:Nonetype object has no attribute get0.6 (2020-01-10)Add compatability to Python 3.Retry connection to clamd if it is busy.0.5 (2013-12-20)When collecting file uploads from the request, check for file-like objects
instead of instances of exact typefile.0.4 (2013-12-19)Fix small issue when the value for pyramid_clamav.debug is not configured.0.3 (2013-12-19)pyramid_clamav.debug can now be set in config. If enabled AND clamav is not
configured, it will generate a flash message when a file upload was found,
but the file will not be touched. Additionally errors are logged at startup
and on file uploads.0.2 (2013-12-17)Fixed setup.py to contain locale directory.0.1 (2013-12-17)Initial release.
Package: pyramid-classy
Pyramid-ClassyPyramid-Classy is an extension that adds class-based views to
Pyramid more simple. Main idea was taken from the Flask-Classy written by
Freedom Dumlao.Documentation:https://github.com/tark-hidden/pyramid_classyChangelog0.4.4No more print if debug=True, now it depends on logging in a Pyramid config file.Fixed too long route_name if class view inherit other class.0.4.2Py3 compatibility support.0.4IndexView is very useful name, but… Now you can handle a root url with any class you want - with route_base = ‘/’.Some weird bugs has been fixed.0.3Fixed a terrible bug, that doesn’t allow to define a few routes for the root.Added debug flag. Now you can see routes and their names if you want.Added @view_defaults support. It’s weird, but it didn’t work properly.0.2Cleaned up code.Now functions in classes accepts only one argument: self. Request variable now is self.request.0.1Initial release.
Package: pyramid_closure
pyramid_closureInstall:` $ git clonehttps://github.com/camptocamp/pyramid_closure.git$ cd pyramid_closure $ make install `Create a project:` $ cd .. $pyramid_closure/.build/venv/bin/pcreate-spyramid_closure ProjectName `Install and build project:` $ cd ProjectName $ make install `Start development server:` $ make serve `0.0Initial version
Package: pyramid-cloudflare-access
IntroductionInstallationJust dopip install pyramid_cloudflare_accessoreasy_install pyramid_cloudflare_accessCompatibilitypyramid_cloudflare_access runs with pyramid>=1.7 and python>=3.6.
Other versions might also work.UsageAdd Cloudfalre config to a production.ini:pyramid_cloudflare_access.policy_audience = "my_audience"
pyramid_cloudflare_access.team = "https://team.cloudfare-access.com"More information can be found athttps://developers.cloudflare.com/cloudflare-one/identity/users/validating-json#python-exampleUsage example for the tween:def main(global_config, **settings):
    config = Configurator(settings=settings)
    config.include('pyramid_cloudflare_access')
    return config.make_wsgi_app()ReleasingUpdate CHANGES.rst.Update pyproject.toml version.Runpoetry check.Runpoetry publish--build.We’re hiring!At Niteo we regularly contribute back to the Open Source community. If you do too, we’d like to invite you tojoin our team!
Package: pyramid_command
pyramid_command===========Console commands manager for Pyramid frameworkusage======install packageWrite your console commands.For example in myproject/console.py:from pyramid_command import Commandclass MyCmd(Command):name = "my_cmd"description = "My usefull command"args = (("echo", {"help":"echo the string you use here"}),(("-f", "--file"), {"help":"file"}),)def run(self, echo='dd', file=None):print self.name, "runs", echo, fileThen configure where to search your commands.For example in development.ini:[app:main]use = egg:myproject......console_commands = myproject.consoleNow run:>>>pcommand development.ini my_cmd echovalCHANGES.txt
Package: pyramid_contextauth
A simple pyramid extension to register contexts based authentication policy.
Introspectables for policies registered are added to configuration and will
appear in debugtoolbar with their associated contexts.frompyramid.securityimportremember,forgetfrompyramid.authenticationimportAuthTktAuthenticationPolicydefincludeme(config):config.include('pyramid_contextauth')config.register_authentication_policy(AuthTktAuthenticationPolicy('secret'),Context1,)config.register_authentication_policy(ContextAuthenticationPolicy(),(Context2,Context3),)classContext1(object):passclassContext2(object):passclassContext3(object):passclassContextAuthenticationPolicy(object):defauthenticated_userid(self,request):returnunauthenticated_userid(request)defunauthenticated_userid(self,request):"A dummy example"returnrequest.POST.get('userid')defeffective_principals(self,request):ifself.unauthenticated_userid(request):return['User']return[]defremember(self,request,prinicpal,**kw):returnremember(request,prinicpal,**kw)defforget(self,request):returnforget(request)Changelog0.7Policy checks on each resource lineage and get the first policy it gets.Add coverall in after_success of travis config.Remove pyramid version constraints.0.6Removing decoratorauthentication_policy: extension should not
instantiate authentication policy class internally.0.5Registering same context to multiple policies raises a configuration error.Unregister old policy when overriding a context with another policy.Change register_authentication_policy and authentication_policy signatures.0.4Add introspectables to config for registered authentication policies.Rename register_context to register_policy0.3Break backward compatibility asContextBasedAuthenticationPolicy.register_contextnow requiresconfiginstance as first argument.Addconfig.register_authentication_policyconfiguration directive which
accepts a list of contexts.Use registry adpaters to register policies rather than a dict.Add a decoratorauthentication_policyto register policies when doing
a config scan.0.2.1Adjust requirements files and dependencies.0.2Update dependencies by adding requirements files.0.1.1Changedregister_contextinterface which breaks compatibility with 0.0.30.0.3Commit configuration before returning from includeme.0.0.2When not provided,authenticated_useridandeffective_principalsfrom
super classCallbackAuthenticationPolicyare used.0.0.1Initial version
Package: pyramid_cron
pyramid_cron - Simple scheduled tasks for PyramidScott Torborg -Cart LogicProvides the ability to register simple tasks (callback functions) for
scheduled execution with a cron-like syntax.Why it’s better than a typical task queue like Celery, Resque, etc:No user permissions to worry about: everything is run inside a web request,
so the task has all the same permissions as your web app.Very simple setup, no additional daemons required.The API follows Pyramid idioms.Why it’s worse:It’s not well suited to long-running tasks: everything is run inside a web
request.It does not distribute jobs across workers.It does not allow for prioritization of jobs, or have any support for
non-synchronous tasks.Documentation ishosted at Read the Docs.Licensepyramid_cron is licensed under an MIT license. Please see the LICENSE file
for more information.
Package: pyramid-crow
pyramid_crowprovides apyramidpackage for integrating withraventhat is both automatic and complies withraven’shttp_contextstandard.UsageIncludepyramid_crowusing either thepyramid.includesconfiguration file setting orconfig.include('pyramid_crow')Include a DSN in your config file asraven.dsnNo special handling or explicit invocation is required, even if using an exception view.pyramid_crowautomatically employsraven’s password sanitization to strip sensitive values from submitted data.
Theravenclient is accessible asrequest.raven.
Any configuration file values starting withraven.will be provided as keyword arguments when creating the client.
No automatic type conversion is performed; if any of the values you want to provide should be anything other than a string, you should convert them appropriately.Ignoring ExceptionsNot every exception needs to be captured byraven.
Some – likepyramid.httpexceptions– indicate exceptional but expected conditions.pyramid_crowalways ignorespyramid.httpexceptions.
You can ignore other exceptions as well by providing a list of importable dotted names aspyramid_crow.ignorein your configuration.For example:pyramid_crow.ignore =
  yourpackage.YourException
  yourpackage.YourOtherException
Package: pyramid_crud
This software is a framework with the attempt to replicate a behavior similar
to Django’sGeneric ViewsandAdmin Pages.It aims to provide a simple yet configurable interface to get a CRUD (Create,
Read, Update, Delete) interface on persisted data.This library is anunofficialextension to Pyramid. This is not likely to
change unless the libraries dependencies are decoupled as described inA Word on Dependencies.NoteThis library is in an early phase and contributions are welcome that
fix bugs or add missing features. Just please make sure to keep it as clean
as possible. Also always take a look at how Django achieves the desired
functionality (if present), because they have some good ideas on keeping
the code clean and readable.LinksDocumentationSource CodePackage on PyPI
Package: pyramid-csrf-multi-scheme
This package enables two separate cookie tokens on each request, bound to the scheme:a SECURE HTTPS only cookiea mixed-use insecure http token (which is also available on https).If the current scheme isHTTPS:only the SECURE HTTPS token will be consideredHOWEVER calls to generate a new token will reset both the SECURE HTTPS and the
insecure http tokens.If the current scheme isinsecure http:the SECURE HTTPS tokens are ignored as they are not even available, and only the
insecure http token is considered.Python VersionsThis package is currently supported under Python2.7 and 3.8; other 3.x versions may work.This package should work on Pyramid1.x and 2.xWhy?If an application supports bothHTTPandHTTPSendpoints, this package simplifies
isolating the CSRF data from both.Is this necessary?I’m not sure, but have decided to err on the side of caution.HTTP traffic is sent in plaintext and capable of being intercepted by a
man-in-the-middle or network packet sniffing.It seems plausible that someone might read a csrf token via HTTP and use that
in attempts to compromise HTTPS endpoints in a mixed use environment.A better option is to only use HTTPS tokens and forms - but that is not
always an option.debugtoolbar support!just add to yourENVIRONMENT.inifile, or similar application configuration.debugtoolbar.includes=pyramid_csrf_multi_scheme.debugtoolbarTthe debugtoolbar will now have aCSRFMultiSchemepanel that has the following info:configuration info on the cookie namesincoming request csrf valuesoutgoing response csrf valuesLicenseMost of this is just code lightly edited from Pyramid, and
therefore available under Pyramid’s licensing terms.
Package: pyramid-cubicweb
pyramid_cubicwebis one specific way of integratingCubicWebwith aPyramidweb application.Featuresprovides a default route that let a cubicweb instance handle the request.UsageTo use, installpyramid_cubicwebin your python environment, and
thenincludethe package:config.include('pyramid_cubicweb')ConfigurationRequires the followingINI setting / environment variable:cubicweb.instance/CW_INSTANCE: the cubicweb instance nameAuthentication cookiesWhen using thepyramid_cubicweb.auth(CubicWeb AuthTkt
authentication policy), which is the default in most cases, you may
have to configure the behaviour of these authentication policies using
standard’s Pyramid configuration. You may want to configure in yourpyramid.ini:Session Authentication:This is aAuthTktAuthenticationPolicyso you may overwrite default
configuration values by adding configuration entries using the prefixcubicweb.auth.authtkt.session. Default values are:cubicweb.auth.authtkt.session.hashalg = sha512
cubicweb.auth.authtkt.session.cookie_name = auth_tkt
cubicweb.auth.authtkt.session.timeout = 1200
cubicweb.auth.authtkt.session.reissue_time = 120
cubicweb.auth.authtkt.session.http_only = True
cubicweb.auth.authtkt.session.secure = TruePersistent Authentication:This is also aAuthTktAuthenticationPolicy. It is used when persistent
sessions are activated (typically when using thecubicweb-remembermecube). You may overwrite default configuration values by adding
configuration entries using the prefixcubicweb.auth.authtkt.persistent. Default values are:cubicweb.auth.authtkt.persistent.hashalg = sha512
cubicweb.auth.authtkt.persistent.cookie_name = pauth_tkt
cubicweb.auth.authtkt.persistent.max_age = 3600*24*30
cubicweb.auth.authtkt.persistent.reissue_time = 3600*24
cubicweb.auth.authtkt.persistent.http_only = True
cubicweb.auth.authtkt.persistent.secure = TrueWarningLegacy timeout values from the instance’sall-in-one.confarenotused at all (``
http-session-time`` andcleanup-session-time)Please refer to thedocumentationfor more details (available in thedocsdirectory of the source code).
Package: pyramid_datadog
pyramid_datadogDatadog integration for Pyramid.
This library allows you to create graphs in datadog to keep track of number of requests and requests durations.Installationpipinstallpyramid_datadogUsagefromdatadogimportstatsddefmain(global_config,**settings):# pyramid initializationconfig.include("pyramid_datadog")config.configure_metrics(statsd)returnconfig.make_wsgi_app()What pyramid_datadog will measure for youUsing pyramid.events pyramid_datadog will log the following metrics in datadog:Metrictagspyramid.request.duration.route_matchpyramid.request.duration.traversalpyramid.request.duration.viewroutepyramid.request.duration.template_renderroutepyramid.request.duration.totalroute, status_code, status_typePlease refer to the following link for information on the chronological order of events during a pyramid requesthttp://docs.pylonsproject.org/projects/pyramid/en/latest/narr/router.htmlRelease Notes0.1.0 (2016-08-04)First release of pyramid_datadog with 100% coverage in tests
Package: pyramid_debugauth
Debug Authentication Policy for Pyramid. Provide a simple and standard way to
define the pyramid principals from the HTTP client.Warning: This pyramid is totally unsafe for production and should be
restricted to debug usage / development phase.PyPI:https://pypi.python.org/pypi/pyramid_debugauthCode:https://github.com/pior/pyramid_debugauthInstallationInstall using setuptools, e.g. (within a virtualenv):$ pip install pyramid_debugauthSetupOncepyramid_debugauthis installed, you can define a authentication policy
withconfig.set_authentication_policy.In your Pyramid project:frompyramid.authorizationimportACLAuthorizationPolicyfrompyramid_debugauthimportDebugAuthenticationPolicyconfig=Configurator(.....)config.set_authentication_policy(DebugAuthenticationPolicy())config.set_authorization_policy(ACLAuthorizationPolicy())UsageThe DebugAuthenticationPolicy allows a client to impersonate any user and
specify any number of principals desired using the standardAuthorizationhttp header and a non-standard auth-schemeDebug(RFC 7235):Authorization: Debug user_id [principal_1] [principal_2] ...With common http clients:$curlhttp://localhost:6543-H'Authorization: Debug bob admin'$httphttp://localhost:6543'Authorization: Debug bob admin'Or using a non-standardauthorizationquery parameter:http://localhost:6543/protected?authorization=debug%20user_id%20principal_1With common http clients:$curlhttp://localhost:6543?authorization=debug%20bob%20admin$httphttp://localhost:6543?authorization=debug\bob\adminDevelopmentRunning tests:$ virtualenv venv
$ . venv/bin/activate
(venv)$ pip install -e .[dev]
(venv)$ nosetestsChangelog0.2.0 (2018-02-09)Switch to GithubSwitch to setuptools (from d2to1)Fix crash in tests with recent versions of Pyramid0.1.2 (2014-12-03)Permit setting a custom callback.0.1.1 (2014-09-09)Add ability to authenticate via Query String0.0.2 (2014-09-08)Minimal feature setFirst release on PyPI
Package: pyramid-debugtoolbar-ajax
pyramid_debugtoolbar_ajaxBuild Status:This package adds an "Ajax" panel to thepyramid_debugtoolbar.The "Ajax" panel contains buttons and forms which can be used to replay the
request in a new browser window -- allowing you to spawn a debugger window for
errors encountered on background ajax requests, or form submissions.How to use:Ensure these lines are in your pyramid config file:pyramid.includes = pyramid_debugtoolbar
debugtoolbar.includes = pyramid_debugtoolbar_ajax
Package: pyramid-debugtoolbar-api-performance
pyramid_debugtoolbar_api_performance.. image::https://github.com/jvanasco/pyramid_debugtoolbar_api_performance/workflows/Python%20package/badge.svg:alt: Build Statuspyramid_debugtoolbar_api_performanceextends the existingpyramid_debugtoolbarPerformance Panel to support downloadable CSV files of profiling data.This package does not replace the default panel, and requires it to be active.This package is designed for application profile and to be a useful part of test
suites, allowing developers to run a series of tests and log the Performance
performance.The package exposes two routes for CSV data:timingfunction_callsBoth correlate to the official Performance panel data.The urls are generated in a machine-friendly format, so you can regex therequest_idoff a page and pull it from the API.  This is explained below...NOTES:This packages requires pyramid_debugtoolbar 4.0 or newerHow to use this packageUpdate your ENVIRONMENT.ini file.. code-block:: pythondebugtoolbar.includes = pyramid_debugtoolbar_api_performanceYou MUST be usingpyramid_debugtoolbarwith the Performance panel enabled.
This package simply piggybacks on the existing module's work to log queries.You MUST usedebugtoolbar.includes.  This will not work properly viapyramid.includesYou can access a csv of the Profiling report via the following url hack:.. code-block:: pythonurl_html = '/_debug_toolbar/{request_id}'
url_api =  '/_debug_toolbar/api-performance/timing-{request_id}.csv'
url_api =  '/_debug_toolbar/api-performance/function_calls-{request_id}.csv'The file will be downloaded and offer a content-disposition as:.. code-block:: shellperformance-{request_id}.csvConfigurationBy default, this package writes CSV files using "UTF-8" encoding.To change this, use the environment variablepyramid_debugtoolbar_api_performance_encoding.. code-block:: shellexport pyramid_debugtoolbar_api_performance_encoding=ascii
Package: pyramid-debugtoolbar-api-sqlalchemy
pyramid_debugtoolbar_api_sqlalchemypyramid_debugtoolbar_api_sqlalchemyextends the existingpyramid_debugtoolbarSQLAlchemy Panel to support downloadable CSV files of profiling data.This package does not replace the default panel, and requires it to be active.This package is designed for application profile and to be a useful part of test
suites, allowing developers to run a series of tests and log the SQLAlchemy
performance.If you are using the debugtoolbar directly:If SQLAlchemy queries exist on the request, a “SQLAlchemy CSV” tab will appear.
That will prompt you for queries.If you are scripting:The urls are generated in a machine-friendly format, so you can regex therequest_idoff a page and pull it from the API.  this is explained below:NOTES:This packages requires pyramid_debugtoolbar 4.0 or newerHow to use this packageUpdate your ENVIRONMENT.ini filedebugtoolbar.includes=pyramid_debugtoolbar_api_sqlalchemyYou MUST be usingpyramid_debugtoolbarwith the SQLAlchemy panel enabled.
This just piggybacks on the existing module’s work to log queries.You MUST usedebugtoolbar.includes.  This will not work properly viapyramid.includesYou can access a csv of the SQLAlchemy report via the following url hack:url_html='/_debug_toolbar/{request_id}'url_api='/_debug_toolbar/api-sqlalchemy/sqlalchemy-{request_id}.csv'The file will be downloaded and offer a content-disposition as:sqlalchemy-{request_id}.csvThe CSV columns are:execution timingSQLAlchemy queryquery params (json encoded)ConfigurationBy default, this package writes CSV files using “UTF-8” encoding.To change this, use the environment variablepyramid_debugtoolbar_api_sqlalchemy_encodingexportpyramid_debugtoolbar_api_sqlalchemy_encoding=ascii