Saravanan666/pypi-org huggingface dataset:
Package: getpack
Declarative resources with implicit deploymentThis package provide classes that allow to setup external resources
(utilities, python packages, executables etc.) that will be deployed as
they are used. In most cases data should be on the web and it will be
deployed and cached locally on only first usage.There are several examples intest/folder andgetpack.librarymodule
already defined and useable. But main intention is to provide framework for
declarative setup of any resource and work with it without care of deployment.fromgetpack.resourceimportWebResourceclassExample(WebResource):version='0.1'archive_url='https://example.com/example-0.1.zip'then it would be used:importsubprocesssubprocess.call(Example()().path/'example.exe')Second round braces required to actually make an effect from resource
and first round braces used to initialize resource class, that would produce
resource descriptions on the fly like follows:Example(version='0.2',archive_url='https://Example.com/example-0.2.zip')You may experiment with following working snippet and try to changePySide2version:python-c"import getpack.library;getpack.library.PySide2(version='5.14.1')(); import PySide2.QtWidgets; app=PySide2.QtWidgets.QApplication(); w=PySide2.QtWidgets.QPushButton(PySide2.__version__); w.clicked.connect(w.close); w.show(); app.exec_()"TODOUtilizerequirements.txtto reproduce both development and production
environments.TestingsFor linux testing with Docker, run:docker build -t test . && docker run -it --rm test pytest .
Package: getpaid.discount
This package provides product discount functionality for the getpaid framework.CHANGES0.11 (2010-09-02)Remove dependency on five.formlib [larubbio]0.10 (2010-09-01)Fix dependencies and stray i18n files [larubbio]0.9 (2010-07-29)Allow users to enter multiple discount codesDo not truncate discount printout in cart0.8.3 (2009-05-24)Fix a bug introduced in 0.8.2 [larubio]0.8.2 (2009-05-24)Make discount code case insensitiveAdd help text in cart viewlet0.8.1 (2009-05-12)trim whitespace from the discount code [larubbio]0.8 (2009-05-12)added discount code.  There is a known bug were the discount total is not updated if a user adds an item into their cart, adds the code, then adds a second of that item. [larubbio]created a browser layer to suppress viewlets when product is not installed [larubbio]0.7.1 (2008-01-28)added discount details on thank you page (belowcartthankyou) [flejard]0.7 (2008-12-30)added the listing of the discount below the cart resume
[lucielejard]0.6 (2008-10-09)fixed a bug that happens in Plone 3.1. If you have getpaid.discount in your products, you can’t add an item to your cart.0.5 (2008-08-29)Added buildout files and general text documents to project root.removed setup.cfgupdated the readme since we are no more using the zcml slugs into the buildout0.4 (2008-08-21)Eggified packageDetailed DocumentationTested withPlone 3.0.6PloneGetPaid 0.6.0Not fully working with Plone 2.5.5, see the note at the bottomSteps to installuncomment the getpaid.discount egg into buildout.cfgrun bin/buildoutstart your instancego to portal_setup and run the steps for the profile getpaid.discountActionAfter running the steps, on each payable product, you will have an available action to make the product “discountable” or “buy x get y free”.TabOnce you make a product discountable, you will have a new tab “Discountable” available to you, for you to edit/update your discount.PortletsWhen you make a product discountable, it will automatically show the Discounted Product portlet instead of the default PGP one.ViewletsWhen there are some discounted items in your cart, a viewlet with the list of discounts will show up automatically on the cart listing.NoteWhen you use Plone2.5, you can’t uncomment the zcml slugs for the getpaid.discount egg into buildout.cfg because it creates an error when you start your instance. I haven’t found a fix for that yet. The consequences are that the portlet for the Discounted Product details won’t show up. You can probably put the overriding into your own product, and use what I’ve put into the overrides.zcml as a model.Developped by Six Feet Up. Contact: lucie AT sixfeetup DOT com, or lucielejard on irc.Download
Package: getpaid.emailcheckout
Why do I want to use this package?In our shop shipping to different countries is possible but shipping costs vary for different items
and destination countries.
(the ups plugin is bound to ups service which is not that common and quite expensive in our region)Writing a custom shipment plugin that handles all these cases seemed to be too much work for the start.We have a small website with shop functionality (no dedicated webshop) and expect few orders (about 0-10 per week).That’s why we decided to let our staff calculate shipping costs and handle the payment
(via credit card, bank transfer, cash on delivery, etc) and fulfillment part
of the shopping process offline.What this package doesgetpaid.emailcheckoutcustomize the CheckoutReviewAndPay step so users need not supply
credit card information.currently orders stay in CHARGING state. getpaid’s order interface does not
offer the possibility to set the state to charged atm.RequirementsThis package has been developed for and tested withPlone 4.0.X (older plone versions should work though)Products.PloneGetPaid >= 0.10.1Questions - FeedbackJust drop me an email: harald (at) webmeisterei dot comCHANGES0.1 (2011-02-14)initial release (used >6 months in production)
Package: getpaid.luottokunta
IntroductionLuottokunta is Finnish major organization which provides credit card processors.
This package implements Luottokunta payment processor toProducts.PloneGetPaidpackage.Changelog0.4.1 (2010-07-02)Changed base_url in LuottokuntaOrderInfo class.Updated Japanese translations.Tested with Plone-4.0b5.0.4.0 (2010-06-01)Added conditional imports to order.py for Plone 4 compatibility.Tested with Plone-4.0b3.0.3.3 (2009-09-11)Fixed bug when query string does not hold order id in thanks page.0.3.2 (2009-09-09)Fixed rounding of total price.Declined and canceled templates are now separated.Tested with Card_Details_Transmit value = “0”Tested with Plone-3.3.0.2.2 (2009-08-07)Bug fixed when luottokunta authentication declined.0.2.1 (2009-08-01)Fixes done for payment processor without getpaid.paymentprocessors installed.0.2.0 (2009-07-31)Updated for getpaid.paymentprocessors package.0.1.3 (2009-06-02)When returned query string from Luottokunta gives order id error and if incremental order id is selected, order id increases its value by one.0.0.11 (2009-05-16)Initial releaseInstallationIf you are using zc.buildout and the plone.recipe.zope2instance
recipe to manage your project, just do this:Addgetpaid.luottokuntato the list of eggs to install, e.g.:[buildout]…eggs =getpaid.luottokuntaTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]…zcml =getpaid.luottokuntagetpaid.luottokunta-overrides # Comment out this if getpaid.paymentprocessors is installed.Re-run buildout, e.g. with:$ ./bin/buildoutCreditsTranslationsFinnish - Ilja Everila
Package: getpaid.nullpayment
This package contains null payment process functionality for the getpaid
framework for testing purposes.CHANGES0.5.0 (2010-05-18)Mark the processor as one that supports recurring payments, so that it
can be used in tests of the UI for recurring payments.
[davisagli]0.4.0 (2010-04-07)Updated for compatibility with Zope 2.12 / Plone 4.  Plone 2.5 is no
longer supported.0.3.1 (2008-11-24)Persisted processor transaction id and last-4 digits of credit card to
ZODB.  Also, modified order-summary.pt to present these two fields.
[ctxlken]0.3 (2008-08-29)Eggified packageAdded buildout files and general text documents to project root.removed setup.cfgupdated the classifiersDetailed DocumentationNull Payment ProcessorThis is a payment processor for getpaid, which doesn’t actually
process any payments. Its sole purpose is for testing other parts
of getpaid, without the hassle of setting up a merchant/dev account
with one of getpaid’s supported payment processors.
Package: getpaid.ogone
This package contains ogone payment processor functionality for the
getpaid framework.CHANGES0.3 (2009-03-13)fix options location [jefroche]pass layout properties to ogone [jefroche]pep8 [jefroche]Add buildout files and general text documents to project root [fairwinds.dp]Updated proper licensing for package [fairwinds.dp]0.2 (2008-08-23)Eggified packageAdded buildout files and general text documents to project root.Detailed DocumentationThis package requires:zc.table [installed in lib/python] (svn://svn.zope.org/repos/main/zc.table/tags/zc.table-0.5.1/src/zc/table)zc.resourcelibrary [installed in lib/python] (svn://svn.zope.org/repos/main/zc.resourcelibrary/tags/zc.resourcelibrary-0.5/src/zc/resourcelibrary)Five 1.4.2 [installed in Products] (svn://svn.zope.org/repos/main/Products.Five/tags/1.4.2/)CMFOnFive [installed in Products] (http://codespeak.net/svn/z3/CMFonFive/trunk)five.intid [installed in lib/python] (https://svn.plone.org/svn/collective/five.intid/trunk/five)Plone 2.5hurry.workflow [installed in lib/python] (http://getpaid.googlecode.com/svn/trunk/vendor/hurry.workflow/branches/0.9/src/hurry/workflow)ore.member [installed in lib/python] (https://svn.objectrealms.net/svn/public/ore.member/trunk/src/ore/member)ore.viewlet [installed in lib/python] (https://svn.objectrealms.net/svn/public/ore.viewlet/trunk/src/ore/viewlet)getpaid.core [installed in lib/python] (http://getpaid.googlecode.com/svn/trunk/getpaid.core/src/getpaid/core)yoma.layout [installed in lib/python] (http://getpaid.googlecode.com/svn/trunk/vendor/yoma.layout/)yoma.batching [installed in lib/python] (http://getpaid.googlecode.com/svn/trunk/vendor/yoma.batching)PloneGetPaid [installed in Products] (http://getpaid.googlecode.com/svn/trunk/products/PloneGetPaid)This package must be installed in $YourZopeInstance/lib/python/getpaid with the name ogoneDownload
Package: getpaid.pagseguro
GetPaid PagSeguroGetPaidPagSegurois used to do payments using PagSeguro, a brazilian
PayPal like service.IntroductionConfigure in the buildout[buildout]
parts =
...
getpaid

eggs =
...
${getpaid:eggs}
getpaid.pagseguro

zcml =
...
getpaid.pagseguro
getpaid.pagseguro-overrides

[getpaid]
recipe = getpaid.recipe.release
addpackages=
getpaid.pagseguroSetup this as your payment processor in getpaid admin interface (Payment Options) :3. Last step is to enter your pagseguro email and your TOKEN info in Payment Processor
Settings :Enjoy!Changelog0.2 - 2009-08-28Fixes a bug when rendering the PagSeguro button [lucmult]0.1 - 2009-04-20Initial release0.1 - Created over the code of getpaid.paypal, making the needed modifications to work with Brazilian’s PagSeguro
Package: getpaid.payflowpro
This package provides paypal payflowpro payment processor functionality for the getpaid framework.It uses python-payflowpro for the underlying access to paypal (http://code.google.com/p/python-payflowpro/&http://pypi.python.org/pypi/python-payflowpro/)What is Paypal PayFlowProFor more information seehttps://www.paypal.com/cgi-bin/webscr?cmd=_payflow-pro-overview-outsideCreate PayFlowPro test accountTo create a test paypal payproflow account all you need to do is go tohttps://www.paypal.com/cgi-bin/webscr?cmd=_payflow-gateway-overview-outsideand go through the registration flow.  When it asks you for your credit card information, just drop out (close browser) and a test account will be created.This is only for US accounts.FYI, you can use the same account for both testing and live transactions at the same time, so if you are going to activate the account, create the login id accordingly.After completing that step you will receive an email with login instructions.After logging in you should create a seperate user account for getpaid.payflowpro to use.Plone Setupgetpaid.payflowpro setupEnter Plone Site Setup -> GetPaid SetupUnder ‘Payment Options’ select Paypal PayFlowProUnder Payment Processor Settings enter the login credentials for your PayFlowPro account.  (See Create PayFlowPro test account above if you do not have one)Dependenciesgetpaid.payflowpro requires the following:GetPaid (http://www.plonegetpaid.com/)A PayFlowPro accountTODOThe login information should be encrypted (or minimally obfuscated) and not redisplayed to the user after it is entered.Test refund. It’s imlemented, but I haven’t tested it since I can’t figure out how to refund an order in the UI.  Plus who really want’s to give money back? ;)CHANGES1.1 (2009-08-19)Store the processor id returned by payflowpro1.0 (2009-07-22)Handle expiration date as a string.1.0b1 (2009-01-28)Update README to include some information about PayFlowProremove bootstrap and buildout since this is not functional without GetPaidRemove incorrect copyright.  Only copyright message is in LICENSEUpdate version to 1.0b1Implement (but didn’t test) refundsRemove IPaypalPayFlowProwProcessor since it didn’t add anything [larubbio]Detailed DocumentationYou will need to set this as your payment processor in the getpaid admin
interface (Payment Options)Last step is to enter your payflowpro account information (vendor, partner, username and password).Enjoy!Download
Package: getpaid.paypal
This package provides paypal payment processor functionality for the getpaid
framework.CHANGES0.4.4 (2009-08-19)Set the shopping cart on the order before the order created workflow transition is fired [larubbio]0.4.3 (2009-05-15)Added Finnish translations. Updated pot files. [ilja.everila]0.4.2 (2009-03-13)Add check for spoofed IPN to IPN handler code [james4765]0.4.1 (2008-12-31)plonify the paypal redirect page. [james4765]Add some more verbose logging, so we can track why some IPNs
are not being recognized by the codeChanged the response method from Paypal to POST so you don’t
have a huge, ugly URL coming back.Override /@@getpaid-thank-you so we can extract the order
number from the paypal POST response.clean up overrides - remove unneeded override code for the
cart actions viewlet, since we are overriding the entire
cart wizard view.fill in order data for shipping address, email, and name from
the data returned from PaypalInitial IPN functionality working with paypal sandbox - need
to wire it into the paypal purchase button to complete
round-trippingAdd cart saving capabilityAdd capability to choose currency in shopping cart code, and
enable round-tripping back from paypalAllow TTW configuration of Paypal merchant ID and selection
of sandbox or production site target0.4 (2008-10-24)getting ready to upload to pypi0.2 (2008-08-23)Eggified packageAdded buildout files and general text documents to project root.Detailed DocumentationYou will need to set this as your payment processor in the getpaid admin
interface (Payment Options)Last step is to enter your paypal account info in Payment Processor
Settings.Enjoy!Download
Package: getpaid.pxpay
This package contains pxpay for getpaid.CHANGES0.5 (2010-05-07)fixed bug with timeout setting on ssl connection string0.4 (2009-10-30)add an explicit certs.pem and add known CAs that paymentexpress are
using.0.3 (2008-12-31)put order id into TxnData1 so that exported DPS reports have
an order id we can cross check against orders in getpaid order
manager [matt.halstead]0.2 (2008-08-29)Added buildout files and general text documents to project root.removed setup.cfgDetailed DocumentationThis is a Payment Processor for the PaymentExpress PXPay hosted Payments solution
SEE:http://www.paymentexpress.com/technical_resources/ecommerce_hosted/pxpay.htmlInstallationYou need to load both the package zcml and the overrides.zcmlIn buildout, make sure you have the egg getpaid.pxpay installed, in
the zope instance configuration, add the following:eggs = getpaid.pxpayMechanicsWe hook into the last checkout and payment step of the checkout so
that the user is redirected to the pxpay web interface to fill out
their credit card details and the redirected back to our site where we
handle success or failure status of the transaction.Deferred payment, repeating payments, authorisations, etc, are not yet
implemented, but the PXPay interface supports them, so there’s no
reason they can’t be added.Orders and Finance workflowAn orders persistence and workflow is managed entirely by this payment
processor. Since we hook into the last step of the checkout, we are
responsible for creating the order, storing it in the manager, and
handling the finance workflow.When a user selects “make payment”an order is created and stored in the order manager (i.e. it is now
persistent in the zodb)finance workflow:  None  –>  REVIEWINGthe order is authorized - which means a payment request is made to
pxpay.If pxpay returns saying this is ok and here is the url to redirect to,
then we update the finance workflow: REVIEWING –> CHARGEABLE –>
CHARGING (note: CHARGEABLE –> CHARGING is an automatic transition.The user is redirected to the pxpay web interface to enter credit card
details. The site then redirects them back to our callback and we
negotiate a response message. This tells us whether the payment was
successful or not.If the payment was successful, then we update the finance workflow:
CHARGING –> CHARGEDIf the payment was unsuccessful, then we update the finance workflow:
CHARGING –> PAYMENT_DECLINEDIf there is an error in the communication with pxpay, then we update
the finance workflow: * –> CANCELLED_BY_PROCESSOR with a comment
that this was a communication error. We don’t destroy the cart though
so the user can try again.The error handler for a communications error is a utility so that it
can be overriden easily, for example to redirect the user to another
view.RequirementsA developer account with PaymentExpressGetPaid corezc.sslelementtreeplone (tested on plone 3.1)ContributorsDarryl Dixon <darryl.dixon@winterhouseconsulting.com>
Matt Halstead <matt@elyt.com>Download
Package: getpaid.realex
getpaid.realexLicence: GNU General Public LicenseThis module provides a payment plugin for PloneGetPaid. It authorises payments
using realexpayments.com.RequirementsPlone 4A browser with javascript supportjquery 1.4.3 or laterInstallationAdd collective.personaltags to your buildout eggs.:eggs=\
    ...
    getpaid.realexRun buildout, restart plone.It is not necessarty to use the “Site Setup -> Add-ons” as the packages is detected by
PloneGetPaid.ConfigurationOnce you have installed the module go to the “GetPaid” configlet (under “Site Setup”).“Realex” should appear as an option in “Payment Options”. Select it.This implementation can be used with “Visa”, “Laser” or “MasterCard” cards.
“Laser” is being phased out. If you want to use other card types, make
sure you test them.Realex will provide you with test credit card numbers for testing. When I requested
a set, I received Visa, MasterCard, Laser, Switch, Amex, Delta, Diners and Solo numbers.Now go to “Payment Processor Settings”.When you create an account with Realex, they will provide you with a “Merchant Id”
and a “Secret Code”. Provide these on the settings page.When you are testing against your account, you use the sub-account “internettest”.
For live usage, use “internet”.Charge Description allows you to provide an alternative text for the payers statement,
rather than the default on your merchant account. This is not guaranteed to work for
all banks. See Realex developer documentation.You can use the plugin in “Test Mode”. In this mode, data is not sent to the server.
The plugin gives back a test. Use this mode if you do not have an account with
a card processor and want to try it out.LimitsThis implementation has only been tested with Euros. It is only tested with cards available
in Ireland.Changelog1.0dev (unreleased)Initial release
Package: getpaid.recipe.release.fix.zc.recipe.egg
Code repository:https://getpaid.googlecode.com/svn/Questions and comments to getpaid-dev AT googlegroups dot comReport bugs athttp://code.google.com/p/getpaid/issues/listCHANGES1.4 (2009-01-28)update the version for Products.PloneGetPaid, getpaid.warehouse and
getpaid.discountadded getpaid.payflowpro1.3 (2009-01-19)update the version for Products.PloneGetPaid1.2 (2008-12-31)update the version for: getpaid.core, Products.PloneGetPaid,
five.intid, getpaid.googlecheckout, getpaid.paypal and
getpaid.discount [lucielejard]added getpaid.report and getpaid.warehouse to the recipe
[lucielejard]1.1 (2008-11-24)moved the find-links into the recipe, so that we don’t have
to enter that into the buildout anymore [lucielejard]updated the version number of the GETPAID_BASE_PACKAGES
[lucielejard]1.0 (2008-10-15)added documentation to use the fake eggsadded simplejson and ssl-for-setuptools in the recipe, since they are dependenciesMade the recipe work in a buildout with Plone 3.1Added the possibility to choose what getpaid packages you want the recipe to installCreated recipe with ZopeSkel [lucielejard].Detailed DocumentationTested withA buildout using plone 3.1Required optionsMake sure to add unzip = true into your [buildout] part, so that you don’t have problems with packages being zip safe.Supported optionsThe recipe supports the following option:addpackages=You can choose the “extra” packages you want to use with the “addpackages” option. The names listed correspond to the names of the packages. So you could do addpackages=getpaid.discountAvailable packages:getpaid.authorizedotnetgetpaid.googlecheckoutgetpaid.payflowprogetpaid.paymentechgetpaid.paypalgetpaid.pxpaygetpaid.flatrateshippinggetpaid.upsgetpaid.discountgetpaid.reportgetpaid.warehouseWhat to add in your buildoutWe are assuming you have your own buildout created.>>> write('buildout.cfg',
... """
... [buildout]
... parts =
...     yourownparts
...     getpaid
...
... unzip = true
...
... [getpaid]
... recipe = getpaid.recipe.release
...
... addpackages=
...     getpaid.paymentech
...     getpaid.discount
...
...
... [instance]
... eggs =
...     yourowneggs
...     ${getpaid:eggs}
...
... [zope2]
... (...)
... fake-zope-eggs = true
... skip-fake-eggs =
... additional-fake-eggs = ZODB3
... """)In resume:you add the getpaid partin the getpaid part, you can choose the “extra” packages you want to use with the “addpackages” optionby default, the following packages are installed: ore.viewlet, getpaid.core, Products.PloneGetPaid, getpaid.wizard, getpaid.nullpayment, five.intid, hurry.workflow, simplejson, yoma.batching, zc.resourcelibrary and zc.tablethen you will have to run bin/buildout, start your instance and quickinstall PloneGetPaidContributorsLucie Lejard, AuthorChange history
Package: getpaid.report
This package contains report for getpaid.CHANGES0.1 (2008-12-31)add buildout for testing, make new order serialization reentrant,
switch default db connection to in sqlite in memory, db must be
set by app consumer [kapilt]Changed the lenght of some of the schema fields so they match more
realistic expectations, also used unicode for some of the fields
instead of string, beter unicode than string (go python 3000)
[horacio.duran]Detailed Documentationgetpaid.reporta one way synchronization of getpaid data structures to a rdbms for
the purpose of constructing reports.setupsetup the database schemainstalling this getpaid.warehouse also creates a script, in a buildout
its installed to $(buildout-directory)/bin/setup-report-dbthe script is invoked with the sqlalchemy database url. for example,
to setup a postgres database:# createdb is the standard postgres tool for creating databases
$ createdb getpaid
$ ./bin/setup-report-db postgres://localhost/getpaid
… output of database creation scriptsetting up the zope database connectionyou must configure the database url … currently done in python from
an existing product.>> from getpaid.report import schema
>> from sqlalchemy import create_enginecreate a database connection to the database we’re using>> db = create_engine(‘postgres://localhost/getpaid’)bind it to the metadata>> schema.metadata.bind = dbDownload