Search results

wildcard.fixmissing-1.0-1.lbn19.noarch

This package allows you to fix problems with missing classes when packages do not properly uninstall. To define which classes or interfaces need to be fixed, you need to specify them as environment variables in your buildout file. The format for replacement classes is MISSING_<Class Name> <module name> For instance: [instance] recipe = plone.recipe.zope2instance ... environment-vars = MISSING_ICatalog zc.relation.interfaces MISSING_IQueue collective.pdfpeek.async MISSING_Queue collective.pdfpeek.async MISSING_IPDFpeekLayer collective.pdfpeek.browser.interfaces ... You can also define a replacement module to use instead of having wildcard.fixmissing automatically create it for you. Example: [instance] recipe = plone.recipe.zope2instance ... environment-vars = MISSING_ICatalog zc.relation.interfaces=my.module.interfaces ...

wildcard.fixpersistentutilities-1.1b7-2.lbn19.noarch

Introduction This product was created to help you remove nasty local persistent utilities that won't go away and can destroy your instance when you try to remove a product that registered one. Features * remove adapters * remove subscribers * remove provided interfaces * remove provided interfaces across the entire site - useful for removing collective.flowplayer Just append '/@@fix-persistent-utilities' onto your plone site root or the root of zope(for gsm) and browse through all your registered utilities on your site and remove things at will. By default, the tools prevents you from removing certain registrations; however, you can enter "expert mode" and remove whatever you want. WARNING!!! You can really screw up things if you do this wrong so use with extreme care and backup your instance before you use it. I will not take responsibility if you misuse this tool... Advice Do not include this product as part of your normal set of products. Only install this product on debug zope clients. This product should allow you to remove things from products that are no longer installed on the system; although, if you experience problems removing things, make sure to add those eggs to the system again.

wildcard.foldercontents-2.0b4-1.lbn19.noarch

Since version 2, this package aims to be a backport of the Plone 5 folder contents implementation. Features better drag and drop implementation Shortcuts to move items to the top or bottom of folder Multi-file upload shift-click selection drag drop files from desktop to upload change workflow change tags properties rename add menu

Products.BastionAnalyst-4.0.7-2.lbn19.noarch

Research/Analyst/polling products

Products.TextIndexNG-3.4.14-1.lbn25.noarch

Features: * DocumentConverters * StemmerSupport for 13 languages * SimilaritySearch for english text (based on the Levenshtein distance) * NearSearch, * PluggableParsers * extended StopWords support * full integration in ZCatalog * TestFunctionality through ZMI * ExtensibleArchitecture * being MoreEfficient than the current !TextIndex * full globbing support (wildcard search) * NormalizationSupport (e.g. reducing accented characters to their base form) * full UnicodeAwareness * Relevance ranking of search results added. Searches are now ranked using an extended cosine measure. The cosine measure is based on a vector model and calculates the document "score" based on the frequency of the query terms inside the document result set. * Much faster phrase/near search: the old implementation of TextIndexNG had to perform a very expensive job at query time when phrase/near search was performed. Re-using the !WidCode module of !ZCTextIndex made this operation less expensive. * Left-truncation added: TextIndexNG can be configured creation-time time to support left-truncation (means you can search for "*suffix") Left-truncation is an option because this feature requires a second reverted index inside the lexicion and much more memory! * optional auto-expansion support: This optional feature allows you to get better search results when some of the query terms could not be found. The index expands a query term "foo" to "foo*" if there was no hit for "foo". This expansion is currently global for the index. This feature will be available on a per-query basis in a later version. (Auto-expansion will be extended in a later version to search for similiar terms) * improved HTML converter: now using Chris Withers "Strip-o-Gram" module instead of the Strip-Tag-Parser * added converter for text/sgml * Similarity search (soundex, metaphone, doublemetaphone) dropped and replace with a more general approach and language indepedant approach using the Levenshtein distance. * range searches like "Fi..Foo" * substring searches "substring"

python-linkedin-0.1.5-2.lbn19.noarch

from linkedin import * *Get an authorization url for your user* l = LinkedinAPI(api_key='*your app key*', api_secret='*your app secret*', callback_url='http://www.example.com/callback/', permissions=["r_network"]) auth_props = l.get_authentication_tokens() auth_url = auth_props['auth_url'] oauth_token_secret = auth_props['oauth_token_secret'] print 'Connect with LinkedIn via: %s' % auth_url If you leave callback_url blank, you can get the oauth_verifier from the web browser. It is a five-digit integer. The permissions parameter is optional. It can be a list or string. The [list of permissions](https://developer.linkedin.com/documents/authentication) is in the LinkedIn API documentation. Once you click "Allow" be sure that there is a URL set up to handle getting finalized tokens and possibly adding them to your database to use their information at a later date. \n\n' oauth_token = *Grab oauth token from URL* oauth_verifier = *Grab oauth verifier from URL* l = LinkedinAPI(api_key='*your app key*', api_secret='*your app secret*', oauth_token=oauth_token, oauth_token_secret=session['linkedin_session_keys']['oauth_token_secret']) authorized_tokens = l.get_access_token(oauth_verifier) final_oauth_token = authorized_tokens['oauth_token'] final_oauth_token_secret = authorized_tokens['oauth_token_secret'] l = LinkedinAPI(api_key = '*your app key*', api_secret = '*your app secret*', oauth_token=final_tokens['oauth_token'], oauth_token_secret=final_tokens['oauth_token_secret']) profile = l.get('people/~', fields='first-name,last-name') print profile search = l.get('people-search', params={'keywords':'Hacker'}) print search feed = l.get('people/~/network/updates') print feed share_content = { "comment": "Posting from the API using JSON", "content": { "title": "A title for your share", "submitted-url": "http://www.linkedin.com", "submitted-image-url": "http://lnkd.in/Vjc5ec" }, "visibility": { "code": "anyone" } } share_update = l.post('people/~/shares', params=share_content) print share_update

python2-boto3-1.4.0-1.lbn19.noarch

Boto3 is the Amazon Web Services (AWS) Software Development Kit (SDK) for Python, which allows Python developers to write software that makes use of services like Amazon S3 and Amazon EC2.

python2-botocore-1.4.49-1.lbn19.noarch

A low-level interface to a growing number of Amazon Web Services. The botocore package is the foundation for the AWS CLI as well as boto3.

zope-DocumentTemplate-2.13.4-1.lbn25.x86_64

This package implements the original Document Templating Markup Language (DTML). It uses custom SGML tags to implement simple programmatic features, such as variable replacement, conditional logic and loops. Inside Zope environments page templates and TAL have superseded DTML for most use cases.

python2-zope.untrustedpython-4.0.0-1.lbn19.noarch

Untrusted python libraryCHANGES 4.0.0 (2013-02-12) - Test coverage at 100%.- Package extracted from zope.security, preserving revision history