pip is /hasdeprecating the use of easy_install. Even the instructions on PyPI recommend pip: http://pypi.python.org/pypi

The older Python requests library doesn't support the API we're using. When loading http libraries at runtime, we should ensure that requests is compatible as we do for JSON. As well, should update setup.py appropriately.

Per the API docs, the proper way to create a refund is as follows:

But this doesn't work. You get AttributeError: 'list' object has no attribute 'create'.

This is because the correct way to create a refund (as described in #5) is ch.refund(amount=whatever).

Docs suggests card retrieval returns name value as None or card holder name . In practice card doesn't have attribute name.

In [21]: cus.cards.retrieve("card_placeholder")
Out[21]:
<Card card id=card_placeholder at 0x4f08a40> JSON: {
  "address_city": null,
  "country": "US",
  "customer": "cus_placeholder",
  "cvc_check": "pass",
  "exp_month": 11,
  "exp_year": 2015,
  "fingerprint": "fingerprint",
  "id": "card_placeholder",
  "last4": "3214",
  "object": "card",
  "type": "Visa"
}

In [22]: card = cus.cards.retrieve("card_placeholder")

In [24]: hasattr(card, 'name')
Out[24]: False

#Stripe version: 
In [25]: stripe_obj.version.VERSION
Out[25]: '1.11.0'

Using your example.py I try and do resp.keys(). It spits back the entire object description. I look at the code, and I see the keys definition which references self._values. I was hoping to not using the _values attribute, since its designated as private, though resp.keys() fails because _values is a set, and not a dict. Is keys() supposed to be removed? or it was missed in some refactor? Thanks!

Try to do:

import stripe
stripe.api_key = 'xxx'

rp = stripe.Recipient.retrieve('xxxxxx')
rp.bank_account = None
rp.save()

Get this:

InvalidRequestError

You passed an empty string for 'bank_account'. We assume empty values are an attempt to unset a parameter; however 'bank_account' cannot be unset. You should remove 'bank_account' from your request or supply a non-empty value

But I can't remove bank_account from the request and can't set it to "" either.

If I install Stripe via pip into a virtualenv and copy/paste the API doc code to create any of the classes such as Token, Charge, Customer, etc, I get:

'module' has no attribute '[classname]'

I tried this on Windows 7 and Ubuntu 11.10 and got the same result.

If you install stripe and dependencies into your system site-packages and then enable a virtualenv, you'll also get the same result.

Virtualenv support is absolutely critical for keeping versions of packages separate per project. If you guys could look into this, it would be super!

This may be a use case you never considered (and maybe don't care about), but all objects derived from stripe.StripeObject cannot be unpickled.

The following will result in a RuntimeError:

import pickle
import stripe

obj = stripe.StripeObject(id="foo")
pickle.loads(pickle.dumps(obj))

pickle.loads triggers infinite recursion in StripeObject.__getattr__, when it tries to check for the existence of a __setstate__ method:

Stacktrace (most recent call last):

 File "pickle.py", line 1382, in loads
    return Unpickler(file).load()
  File "pickle.py", line 858, in load
    dispatch[key](self)
  File "pickle.py", line 1215, in load_build
    setstate = getattr(inst, "__setstate__", None)
  File "stripe/__init__.py", line 504, in __getattr__
    if k in self._transient_values:
  File "stripe/__init__.py", line 504, in __getattr__
    if k in self._transient_values:
  ...
  File "stripe/__init__.py", line 501, in __getattr__
    return self.__dict__[k]
  RuntimeError: maximum recursion depth exceeded

When unpickling the StripeObject, the _transient_values attribute doesn't exist, ergo the recursive call to __getattr__.

This can be fixed by either implementing a custom __getinitargs__ or __getnewargs__ method (see the Python pickle docs).

Perhaps it's just me, but there seems to be something amiss in 'line 4' of Example.py.

'resp = stripe.Charge.execute(...' returns an error, while changing it to 'resp=stripe.Charge.create(...' as in the Stripe API documentation seems to work.

Just thought I'd pass this along.

Using OSX 10.7.1 / Python 2.7

The CLI seems to be missing: Transfer, Recipient, Event, Balance, BalanceTransaction.

We are using Google Compute engine on our project and we are also using Google SQL for our DB and Google Cloud Storage. We have to have Google App Engine installed to be able to connect to these other services. I ran into this problem when trying to run the init_plans.py command.

AssertionError: No api proxy found for service "urlfetch"

Here is the traceback.

Traceback (most recent call last):
File "/home/code/virtualenvs/_/local/lib/python2.7/site-packages/django/core/management/base.py", line 222, in run_from_argv
self.execute(_args, **options.dict)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/django/core/management/base.py", line 255, in execute
output = self.handle(_args, _options)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/payments/management/commands/init_customers.py", line 14, in handle
Customer.create(user=user)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/payments/models.py", line 378, in create
email=user.email
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/stripe/init.py", line 703, in create
response, api_key = requestor.request('post', url, params)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/stripe/init.py", line 233, in request
rbody, rcode, my_api_key = self.request_raw(meth, url, params)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/stripe/init.py", line 292, in request_raw
rbody, rcode = self.urlfetch_request(meth, abs_url, headers, params)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/stripe/init.py", line 432, in urlfetch_request
result = urlfetch.fetch(args)
File "/home/code/virtualenvs//local/lib/python2.7/site-packages/google/appengine/api/urlfetch.py", line 267, in fetch
rpc = create_rpc(deadline=deadline)
File "/home/code/virtualenvs/**__/local/lib/python2.7/site-packages/google/appengine/api/urlfetch.py", line 223, in create_rpc
return apiproxy_stub_map.UserRPC('urlfetch', deadline, callback)
File "/home/code/virtualenvs/_/local/lib/python2.7/site-packages/google/appengine/api/apiproxy_stub_map.py", line 413, in init
self.__rpc = CreateRPC(service, stubmap)
File "/home/code/virtualenvs/_/local/lib/python2.7/site-packages/google/appengine/api/apiproxy_stub_map.py", line 67, in CreateRPC
assert stub, 'No api proxy found for service "%s"' % service
AssertionError: No api proxy found for service "urlfetch"

Since we have google app engine installed but are not using it there is an error thrown about api proxy.

To get around this I had to remove the following form init.py

try:
from google.appengine.api import urlfetch
_httplib = 'urlfetch'
except ImportError:
pass

Not sure what the appropriate fix for this should be going forward. I know my use case is probably rare, but figured you might want to know.

okay, so this issue is killing me, it is directly related to, if not the same as issues #75, and #74.

I've detailed a lot of my problems in issue #75, I understand that the workaround should be:

stripe.verify_ssl_certs = False

However, I've got this set, and a debug log shows it is set to false, just before my call to create a customer, however when I try to create the customer , I'm still getting the SSL error:

  File "/home/john/PycharmProjects/flask-peachy-new/server/lib/stripe/api_requestor.py", line 257, in _check_ssl_cert
    raise error.APIConnectionError(e)
APIConnectionError: [Errno 13] Permission denied

stripe.Charge.create() says that you need to either provide a customer id or a credit card token. This does not mention how one would charge a specific card stored under a customer (rather than always the default card).

Looks like passing the card id to 'card' with the customer id works, but is not documented.

When using PycURL on Windows, we end up with POST submissions like this:

   {
     "C:\\Python27\\lib\\email\\mime\\nonmultipart%2Epy%00n": ""
   }

We should either track down and squash the bug, or (easier) don't use PycURL on Windows (fall back on another library)

https://travis-ci.org/stripe/stripe-python

One tests keeps failing for unknown reasons.

A couple warning/error messages don't mention requests or cite PycURL as our preferred HTTP library, which isn't true anymore (e.g. when we use urllib2, and when we can't find any HTTP library). Those should be updated.

Is there a reason StripeObject is extending dict and additionally overriding __setattr__ in StripeObject? I see the value provided (accessing as dict or obj) however it seems like this repeats a lot of code and that a preferable alternative would be to follow the model of webpy's Storage object:

https://github.com/webpy/webpy/blob/master/web/utils.py, line 52:

class Storage(dict):
    """
    A Storage object is like a dictionary except `obj.foo` can be used
    in addition to `obj['foo']`.

        >>> o = storage(a=1)
        >>> o.a
        1
        >>> o['a']
        1
        >>> o.a = 2
        >>> o['a']
        2
        >>> del o.a
        >>> o.a
        Traceback (most recent call last):
            ...
        AttributeError: 'a'

    """
    def __getattr__(self, key): 
        try:
            return self[key]
        except KeyError, k:
            raise AttributeError, k

    def __setattr__(self, key, value): 
        self[key] = value

    def __delattr__(self, key):
        try:
            del self[key]
        except KeyError, k:
            raise AttributeError, k

    def __repr__(self):     
        return '<Storage ' + dict.__repr__(self) + '>'

Thus, instantiation would be simplified to StripeObject(Storage)

We're on API version 2013-07-05 with stripe 1.18.0. Here's what we can do to reproduce. This example customer has a non-zero account_balance going into this:

    customer = stripe.Customer.retrieve(
        subscription_id,
        api_key=self._api_key,
    )

    # Make the changes. The response we get back from this is missing quite
    # a bit of data, so discard it.
    customer.update_subscription(plan=plan_id, card=credit_card)

    # Re-query the customer so we can get the full, up-to-date values.
    customer = stripe.Customer.retrieve(
        subscription_id,
        api_key=self._api_key,
        expand=['default_card'],
    )

At the end of this, we end up with an account balance of 0 again. This is obviously a pretty big disruption for us. Our tests started failing within the last week, so this appears to be a recent API breakage.

Show which languages this package supports using trove classifiers so tools such as caniusepython3 can correctly report it supporting Python 3.

Please update the CA bundle shipped with this python library. Since June 2011 some CA's have been removed from the 'default ubuntu CA bundle'. ( https://github.com/stripe/stripe-python/blob/master/stripe/data/ca-certificates.crt actually reports the date of the CA bundle to be May 9, 2011 ).

It would be useful to me to be able to set stripe so that it ignores verifying ssl certificates. In requests, this is through the 'verify' kwargs.

Likewise, it might be useful for someone to set the .crt to use via the CA_BUNDLE variable, rather than automatically verifying against the stripe-supplied "data/ca-certificates.crt".

Thanks!

When checking to see if a customer is still active, you must do something like:

if getattr(customer, 'deleted', False):
do_something()

in order to avoid an AttributeError from deletednot being present on live objects.

This is incredibly minor, but it would nicer to be able to just do:

if customer.deleted:
do_something()

by defaulting it to False.

https://warehouse.python.org/project/stripe/ is pretty sparse

When I try to install the Stripe python package (http://pypi.python.org/pypi/stripe) on Ubuntu 10.10, I'm getting the following error:

Fatal Python error: pycurl: libcurl link-time version is older than compile-time version

According to these pages, it appears that there are some version differences:
http://kmaiti.blogspot.com/2011/02/fatal-python-error-pycurl-libcurl-lin...
http://ubuntuforums.org/showthread.php?t=1038856

Should I try updating libcurl or pycurl?

See the full traceback here:

  Downloading from URL http://pypi.python.org/packages/source/s/stripe/stripe-1.5.29.tar.gz#md5... (from http://pypi.python.org/simple/stripe/)
  Running setup.py egg_info for package stripe
    Fatal Python error: pycurl: libcurl link-time version is older than compile-time version
    Complete output from command python setup.py egg_info:
    Fatal Python error: pycurl: libcurl link-time version is older than compile-time version
----------------------------------------
Command python setup.py egg_info failed with error code -6
Exception information:
Traceback (most recent call last):
  File "/opt/ActivePython-2.7/lib/python2.7/site-packages/pip/basecommand.py", line 126, in main
    self.run(options, args)
  File "/opt/ActivePython-2.7/lib/python2.7/site-packages/pip/commands/install.py", line 223, in run
    requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle)
  File "/opt/ActivePython-2.7/lib/python2.7/site-packages/pip/req.py", line 986, in prepare_files
    req_to_install.run_egg_info()
  File "/opt/ActivePython-2.7/lib/python2.7/site-packages/pip/req.py", line 222, in run_egg_info
    command_desc='python setup.py egg_info')
  File "/opt/ActivePython-2.7/lib/python2.7/site-packages/pip/__init__.py", line 255, in call_subprocess
    % (command_desc, proc.returncode))
InstallationError: Command python setup.py egg_info failed with error code -6

Hi again, still having problems on Windows. I installed stripe-python from source, and I can import stripe, however when doing:

stripe.Token.create()

I get: 'module' object has no attribute 'Token'

Can someone please try this with Python 2.7.2 on Windows 7 and see if they get the same error?

Thanks!

I've just updated Stripe API library to the latest version and it stopped working on Google AppEngine due to fact that GAE is blocking imports of some packages such as sockets and SSL.

ERROR    2014-05-10 09:55:16,576 base.py:215] Internal Server Error: /api/billing/subscribe_to_paid_plan/stripe
    Traceback (most recent call last):
...
     File "/src/classes/billing/api_views.py", line 3, in <module>
        import stripe
      File "/src/stripe/__init__.py", line 16, in <module>
        from stripe.resource import (  # noqa
      File "/src/stripe/resource.py", line 5, in <module>
        from stripe import api_requestor, error, util
      File "/src/stripe/api_requestor.py", line 5, in <module>
        import ssl
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 60, in <module>
        import _ssl             # if we can't import it, let the error propagate
      File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/devappserver2/python/sandbox.py", line 852, in load_module
        raise ImportError('No module named %s' % fullname)
    ImportError: No module named _ssl

Are there any chances to make it working on Google AppEngine?

I believe the old lib was just fine. It would be pity if we would be forced to use some other payment system as we like Stripe very much!

I'm just trying to get up and running with stripe, flask and app engine. Working through the sample flask checkout guide the following code is throwing a socket error:

customer = stripe.Customer.create(
        email='[email protected]',
        card=request.form['stripeToken']
    )

The stack trace:

File "/Users/adamoakman/Documents/entourage/code/src/application/views.py", line 49, in profile_entity
email='[email protected]',
File "/Users/adamoakman/Documents/entourage/code/src/lib/stripe/resource.py", line 269, in create
response, api_key = requestor.request('post', url, params)
File "/Users/adamoakman/Documents/entourage/code/src/lib/stripe/api_requestor.py", line 126, in request
self._check_ssl_cert()
File "/Users/adamoakman/Documents/entourage/code/src/lib/stripe/api_requestor.py", line 243, in _check_ssl_cert
(uri.hostname, uri.port or 443))
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 448, in get_server_certificate
s.connect(addr)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 333, in connect
self._real_connect(addr, False)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 314, in _real_connect
self.ca_certs, self.ciphers)
TypeError: must be _socket.socket, not socket

Any ideas on what is wrong?

I have other packages that require requests 1.0 or greater so I upgraded requests. Now I get this:

Warning: the Stripe library requires that your Python "requests" library has a version no older than 0.8.8, but your "requests" library has version 1.1.0. Stripe will fall back to an alternate HTTP library, so everything should work, though we recommend upgrading your "requests" library. If you have any questions, please contact support@stripe.com. (HINT: running "pip install -U requests" should upgrade your requests library to the latest version.)

The to_dict() function does not properly serialize the whole object, since lists that could potentially contain StripeObjects are passed through as-is. A good example is the Invoice object, invoice['list']['subscriptions'][0] is still a StripeObject.

Since this stuff is all mechanical, it should be pretty easy to write unit tests for, too.

I'm actually running into the same issue as explained in the stripe-ruby issue stripe/stripe-ruby#46 . Reading the thread on that issue, it seems like Heroku will go through with the request anyway. Recently, I've seen a fair amount of our stripe charges (4 times in the past 2 weeks) taking longer than 30 seconds (and hence Heroku cutting off the request) and the charge NOT ending up going through. I'm wondering if there is another issue going on?

smee

Using the testing documentation I've been trying to generate a CardError with using a credit card token generated from the card number 4000000000000002. Charging an order with this generated token does not cause a:

CardError: Your card's security code is incorrect.

But instead charges successfully.

Why is this the case?

If this is the wrong approach, how can I generate this error to test my application?

I'm generating tokens using the class below.

import stripe
from config import settings

class StripeCardTokenGenerator:

    def __init__(self, card_type="normal"):
        stripe.api_key = settings.STRIPE_API_KEY
        self.card_type = card_type
        self.card_number = {
            "normal": 4242424242424242,
            "card_declined": 4000000000000002,
            "incorrect_number": 4242424242424241,
            "expired_card": 4000000000000069,
            "processing_error": 4000000000000119,
            "incorrect_cvc": 4000000000000127,
            "fails_all_charges": 4000000000000341,
            "visa_debit": 4000056655665556
        }[card_type]
        self.card = {
            "number": self.card_number,
            "exp_month": 12,
            "exp_year": 2015,
            "cvc": 123
        }
        self.create_stripe_card_token()

    def create_stripe_card_token(self):
        token = stripe.Token.create(card=self.card).id
        print stripe.api_key
        print token
        return token

Hi,
recently we started integrating some of our services with the Stripe API.
We are using Python to do that and my issue is related to the way the Python SDK interface is currently designed.

Consider the credit cards interface from the documentation:

customer = stripe.Customer.retrieve({CUSTOMER_ID})
customer.cards.create(card=dict(number='', exp_month=...))

This design makes stubbing the API requests extremely hard.
In order to handle this when testing the integration, it will require mocking a mocked object.

A simple solution to avoid such situations would be to delegate the card creation and retrieval methods to the customer object instead of a nested method.

Consider an updated example:

customer = stripe.Customer.retrieve({CUSTOMER_ID})
customer.createCard(card=dict(number='', exp_month=...))

This approach is a trivial change, but it makes the sdk integration testing process much more simple and is not damaging at all to the readability of the code.

What do you think about this?

Currently, the default() method of StripeObjectEncoder returns a string when the object is a StripeObject (see init.py:572). Per the json documentation: "default(obj) is a function that should return a serializable version of obj or raise TypeError. The default simply raises TypeError."

In other words, StripeObjectEncoder.default() should only return obj.to_dict().

Reproduced as follows:

import stripe
stripe.api_key = "<your api key>"
print(repr(stripe.Charge.all()))

Resulting in:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.3/site-packages/stripe/resource.py", line 138, in __repr__
    ' '.join(ident_parts), hex(id(self)), str(self))
TypeError: sequence item 1: expected str instance, bytes found

Is this api thread safe? I looked at the flask integration example which exposed the module at the global level. Just want to make sure that it is thread safe.

I'm getting ResourceWarnings when using the API for basic listings:

    import stripe
    stripe.api_key = api_key
    response = stripe.Plan.all()
    response = stripe.Customer.all()


(subscribers)Johns-iMac:src john$ python test.py StripeAuthTestCase
/Users/john/Code/lib/python3.4/site-packages/stripe/resource.py:99: ResourceWarning: unclosed <ssl.SSLSocket fd=4, family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=6, laddr=('192.168.0.5', 58604), raddr=('50.18.212.223', 443)>
  instance = cls(values.get('id'), api_key)

/Users/john/Code/subscribers/lib/python3.4/site-packages/stripe/resource.py:48: ResourceWarning: unclosed <ssl.SSLSocket fd=4, family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=6, laddr=('192.168.0.5', 58417), raddr=('50.18.212.223', 443)>
  return super(StripeObject, self).__setattr__(k, v)




Python 3.4.1 (default, May 19 2014, 13:10:29)
[GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.40)] on darwin
>>> stripe.VERSION
'1.19.0'

Easy enough to quash by commenting out the import warnings in resource.py but an annoyance if you're the type to heed the warnings.

Python 3 is growing with Django recently starting to support it and Pyramid having supported it for a while. I think it would be beneficial to test and develop for both Python 2 and 3 compatibility simultaneously.

Currently, on Google App Engine, the stripe client times out if a request takes more than 55 seconds. The reason for this (see code below), is because Google App Engine has a 60 second timeout for normal requests. However, App Engine backends and TaskQueues are not subject to this deadline.

It is a common usage scenario to do a lot of heavy lifting for billing on a backend (e.g., running reports, generating invoices, etc.). Often the 55 second timeout is too short and the request times out.

Please increase this timeout, or better yet, detect when running in a TaskQueue and increase it only in that situation. Thank you.

stripe.init.py:427

    # GAE requests time out after 60 seconds, so make sure we leave
    # some time for the application to handle a slow Stripe
    args['deadline'] = 55

Hello,

Stripe 1.6.1 doesn't seem very happy in a Windows 7, Python 2.7.2 environment. If you simply run:
[code]

import stripe
stripe.VERSION
[/code]
You'll get: AttributeError: 'module' object has no attribute 'VERSION'

You'll receive the same error when trying to use any of the other classes as well, like Token, Customer, Charge, etc.

http://www.python.org/dev/peps/pep-0008/

pep-8 suggests 4 spaces. 4 spaces is pretty much ubiquitous. Also, I seem not to be able to touch the source without reformatting, might just be my system.

Currently, the library supports cents. This works very well, but many people (equally validly) use Decimals for representing amounts in their code. Would it be possible for the library to check whether the provided amount is a Decimal and convert it to cents if so?

If I create a customer, and then attach an invalid coupon via customer.coupon = "invalid" I cannot unset this coupon code by setting .coupon to None as suggested in the documentation.

e.g.,

customer.coupon = "invalid"
customer.save()
InvalidRequestError: No such coupon: invalid
customer.coupon = ""
...
.coupon = None to delete the property

customer.coupon = None
customer.save()
InvalidRequestError: You passed an empty string for 'coupon'. We assume empty values are an attempt to unset a parameter; however 'coupon' cannot be unset. You should remove 'coupon' from your request or supply a non-empty value

I tried making a partial refund by passing in an amount into the Charge.refund() function, but it complained that i was passing in two arguments when it only accepts 1.

Not really a problem but I'm getting a lot of depreciation warnings when using the module, so I checked out your API docs to get the latest way of doing things... which is to use stripe.Invoice etc, which causes the depreciation message!

I can't see any other way other than doing a from stripe.resource import Invoice - but then there's no way to set stripe.api_key.

Docs I'm looking at: https://stripe.com/docs/api?lang=python

Helpful in identifying bugs like #14

As discussed in #40, a StripeClient (with an HTTP client) is a better pattern than one-off changes to support custom configuration. Here's a proposed API for how this will work.

import stripe
import stripe.http_client

client = stripe.Client(
    api_key='sk_test_xxxxxxxxxxxxxx',
    http_client=stripe.http_client.UrlFetchClient(deadline=80)
)

You shouldn't have to use the top level resource classes with a client, so we'll need to expose the resources as attributes

client.charges.all()
client.charges.retrieve()
client.charges.create()

I'd like to make this backwards compatible change, so I'm not proposing we change the current interface, only add the new StripeClient.

This API should also solve #23, #38, and #62 (maybe)

@metcalf thoughts?

Hi guys,

I'm creating charges with the way the documentation suggests:

charge = stripe.Charge.create(
    amount=nail_price,
    currency="usd",
    customer=user.stripe_customer_id,
    description=description
)

But with some users the charge throws:

CardError: Your card's security code is incorrect.

Even through their CVC code check has passed:

Additionally, the cards were successfully created and validated by an iOS application before my application charged them.

Why the cards be charged if they are throwing the CardError?

Please let me know if you need any additional information to solve this issue.

Although it's not strictly mandated by the HTTP spec ( http://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1 - SHOULD rather than MUST ), it might be helpful in a few situations if the stripe-python client explicitly sets a Content-Type on HTTP requests which include an entity-body.

I ran a couple of quick tests, one with the requests library available, and one where it's unavailable (fallback to urllib2), and in both cases the header is not specified when, for example, creating a recipient or transfer.

This came up while creating a test mock endpoint, where it turns out that werkzeug is fairly strict about the situations in which it will attempt to parse entity contents ( https://github.com/mitsuhiko/werkzeug/blob/master/werkzeug/wrappers.py#L314 , https://github.com/mitsuhiko/werkzeug/blob/master/werkzeug/wrappers.py#L350 )

Non-critical and there are various workarounds (intercepting and patching outbound requests), but it'd be a nice-to-have!