Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
152 commits
Select commit Hold shift + click to select a range
96a1cc3
add option to reduce front-end metadata for untracked flags
eli-darkly Oct 5, 2018
e59a1c7
Merge pull request #76 from launchdarkly/eb/ch24449/less-metadata
eli-darkly Oct 5, 2018
89056fc
fix logic for whether a flag is tracked in all_flags_state
eli-darkly Oct 8, 2018
1fc23e4
use expiringdict from PyPi
eli-darkly Oct 14, 2018
0a30e0d
Merge pull request #77 from launchdarkly/eb/ch24449/less-metadata-2
eli-darkly Oct 15, 2018
103b339
Merge pull request #78 from launchdarkly/eb/ch25286/expiring-dict
eli-darkly Oct 15, 2018
40f2ca4
merge from public after release
LaunchDarklyCI Oct 17, 2018
ae8b25e
implement file data source, not including auto-update
eli-darkly Nov 1, 2018
850837d
rm debugging
eli-darkly Nov 1, 2018
aa7684a
rm debugging
eli-darkly Nov 1, 2018
39c9042
Python 3 compatibility fix
eli-darkly Nov 1, 2018
a43bf0c
add file watching, update documentation and tests
eli-darkly Nov 2, 2018
2cea730
readme
eli-darkly Nov 2, 2018
dcf1afe
debugging
eli-darkly Nov 2, 2018
4e98fdd
debugging
eli-darkly Nov 2, 2018
8f3c221
debugging
eli-darkly Nov 2, 2018
84276dd
fix cleanup logic
eli-darkly Nov 2, 2018
2a822e6
rm debugging
eli-darkly Nov 2, 2018
eaabe4d
Merge pull request #79 from launchdarkly/eb/ch26233/file-data-source
eli-darkly Nov 14, 2018
ac5e8de
typo in comment
eli-darkly Nov 14, 2018
39f5f62
merge from public after release
LaunchDarklyCI Nov 14, 2018
040ced9
add feature store wrapper class and make Redis feature store use it
eli-darkly Dec 29, 2018
59a67a8
test the new Redis factory method
eli-darkly Dec 29, 2018
1e38ac1
add DynamoDB support
eli-darkly Dec 29, 2018
431dddf
add test credentials
eli-darkly Dec 29, 2018
3aa5644
link in comment
eli-darkly Dec 31, 2018
bd00276
comment
eli-darkly Dec 31, 2018
11eabd3
Merge branch 'eb/ch28329/feature-store-support' into eb/ch28329/dynamodb
eli-darkly Dec 31, 2018
534ec5d
don't catch exceptions in Redis feature store, let the client catch them
eli-darkly Dec 31, 2018
5f16c8d
gitignore
eli-darkly Dec 31, 2018
ac0f2ea
misc test fixes
eli-darkly Dec 31, 2018
fa56526
Merge branch 'eb/ch28329/feature-store-support' into eb/ch28329/dynamodb
eli-darkly Dec 31, 2018
3a1c2dc
Merge pull request #81 from launchdarkly/eb/ch28329/dynamodb
eli-darkly Jan 9, 2019
b06eef9
Merge pull request #80 from launchdarkly/eb/ch28329/feature-store-sup…
eli-darkly Jan 9, 2019
256b6fb
implement dependency ordering for feature store data
eli-darkly Jan 9, 2019
289077c
fix incomplete implementation & test
eli-darkly Jan 9, 2019
2c59294
Python 3.x fix
eli-darkly Jan 9, 2019
1dd6961
Merge pull request #82 from launchdarkly/eb/ch29197/dependency-order
eli-darkly Jan 15, 2019
78b6118
minor doc fixes
eli-darkly Jan 16, 2019
931d008
merge from public after release
LaunchDarklyCI Jan 16, 2019
3eb821c
feature store test improvements
eli-darkly Jan 18, 2019
cc938e3
better database prefix test
eli-darkly Jan 19, 2019
5b8b337
clarify comment
eli-darkly Jan 19, 2019
b911d9e
Merge pull request #83 from launchdarkly/eb/feature-store-tests
eli-darkly Jan 19, 2019
f9ce243
add Consul feature store integration
eli-darkly Jan 19, 2019
89a96be
typo
eli-darkly Jan 19, 2019
da8c1a6
rm extra import
eli-darkly Jan 19, 2019
b19e618
fix byte/string issue and rename file
eli-darkly Jan 19, 2019
db621dc
rename file
eli-darkly Jan 19, 2019
b09e07e
docs
eli-darkly Jan 19, 2019
9ea89ca
script typo
eli-darkly Jan 19, 2019
a50e6f3
move all low-level feature store integration code into submodules
eli-darkly Jan 19, 2019
68c55b4
Merge pull request #84 from launchdarkly/eb/ch28431/consul
eli-darkly Jan 26, 2019
0baddab
move file data source implementation
eli-darkly Jan 28, 2019
c8585ba
don't need future.with_statement in Python 2.6+
eli-darkly Jan 28, 2019
2a6d53b
don't need future.absolute_import in Python 2.6+
eli-darkly Jan 28, 2019
c32793a
don't need future.print_function when you're printing a single string…
eli-darkly Jan 28, 2019
4971d17
don't need future.division since we're not using the / operator
eli-darkly Jan 28, 2019
0abadf1
rm unused dependency
eli-darkly Jan 28, 2019
e228e90
Revert "rm unused dependency"
eli-darkly Jan 28, 2019
122d7a6
don't need builtins.object unless we're defining an iterator, and eve…
eli-darkly Jan 29, 2019
6a45e70
update docs with note on portability
eli-darkly Jan 29, 2019
858e001
typo
eli-darkly Jan 29, 2019
6788526
Merge pull request #86 from launchdarkly/eb/ch30683/future
eli-darkly Jan 29, 2019
5657142
Merge pull request #85 from launchdarkly/eb/move-modules
eli-darkly Jan 31, 2019
d4d4b8a
update package metadata prior to release
eli-darkly Jan 31, 2019
7a6db77
Merge pull request #87 from launchdarkly/eb/ch30988/setup-py
eli-darkly Jan 31, 2019
4787d44
merge from public after release
LaunchDarklyCI Jan 31, 2019
eaf677e
add test for whether the package can be installed
eli-darkly Jan 31, 2019
eae17f6
fix build
eli-darkly Jan 31, 2019
0892c97
fix build
eli-darkly Jan 31, 2019
e21aa65
fix manifest
eli-darkly Jan 31, 2019
0520a9b
skip test on 3.3
eli-darkly Jan 31, 2019
9deef2d
misc fixes for 3.3
eli-darkly Jan 31, 2019
e44abfa
another 3.3 fix
eli-darkly Jan 31, 2019
273219a
misc fixes
eli-darkly Jan 31, 2019
b3944f9
misc fixes
eli-darkly Jan 31, 2019
02dad33
Merge branch 'eb/ch31016/test-packaging' into eb/ch31016/fix-packaging
eli-darkly Jan 31, 2019
5706f21
Merge pull request #89 from launchdarkly/eb/ch31016/fix-packaging
eli-darkly Jan 31, 2019
9ac4c3b
Merge pull request #88 from launchdarkly/eb/ch31016/test-packaging
eli-darkly Jan 31, 2019
60aa805
merge from public after release
LaunchDarklyCI Jan 31, 2019
b4792e6
add test for importing the built package
eli-darkly Jan 31, 2019
7c2b501
add submodule imports
eli-darkly Jan 31, 2019
a9d481c
ensure that all packages are included in distribution
eli-darkly Jan 31, 2019
71b821f
fix import
eli-darkly Jan 31, 2019
424db63
Merge pull request #91 from launchdarkly/eb/ch31044/package-subdirs-fix
eli-darkly Jan 31, 2019
b2e6c59
Merge pull request #90 from launchdarkly/eb/ch31044/test-package-import
eli-darkly Jan 31, 2019
bee50e8
merge from public after release
LaunchDarklyCI Jan 31, 2019
06fc3b2
add basic pipeline and install deps
hroederld Feb 5, 2019
0165540
add pytest
hroederld Feb 5, 2019
7c9f4e2
remove explicit install of deps
hroederld Feb 5, 2019
a38b957
add other db deps
hroederld Feb 5, 2019
0b6d28f
major cleanup of doc comments, add Sphinx build script
eli-darkly Feb 5, 2019
71534aa
add consul to test-requirements, remove specific reference to install…
hroederld Feb 5, 2019
6bbd65f
Revert "add consul to test-requirements, remove specific reference to…
hroederld Feb 5, 2019
0ec55a7
remove redis and dynamo explicit dep reference
hroederld Feb 5, 2019
49c5993
add requirements.txt
eli-darkly Feb 5, 2019
5228df7
add config file
eli-darkly Feb 5, 2019
f4e5c86
break up API docs into logical groups with a better home page
eli-darkly Feb 5, 2019
9445a6e
misc cleanup
eli-darkly Feb 5, 2019
c496c35
misc cleanup
eli-darkly Feb 5, 2019
a6f1bca
Merge pull request #93 from launchdarkly/eb/ch17280/docs
eli-darkly Feb 5, 2019
68bb4e4
RTD config fixes
eli-darkly Feb 5, 2019
6766920
minor edit
eli-darkly Feb 5, 2019
f612360
Merge pull request #94 from launchdarkly/eb/ch17280/doc-templates
eli-darkly Feb 5, 2019
74e82c8
misc. doc comment edits
eli-darkly Feb 6, 2019
9316b0d
use RTD theme
eli-darkly Feb 6, 2019
794e59f
Merge pull request #92 from launchdarkly/hr/azure
hroederld Feb 6, 2019
5df3b55
Merge pull request #95 from launchdarkly/eb/ch17280/edits
eli-darkly Feb 6, 2019
5eee9ba
Merge pull request #96 from launchdarkly/eb/ch17280/rtd-theme
eli-darkly Feb 6, 2019
338910c
remove jsonpickle
eli-darkly Feb 11, 2019
f586cd1
misc doc comment/readme edits prior to publishing docs
eli-darkly Feb 11, 2019
125d359
Merge pull request #97 from launchdarkly/eb/ch31867/jsonpickle
eli-darkly Feb 12, 2019
0972671
Merge pull request #98 from launchdarkly/eb/ch17280/doc-edits
eli-darkly Feb 12, 2019
dc1f394
merge from public after release
LaunchDarklyCI Feb 12, 2019
9731f4d
add git placeholders for unused dirs
eli-darkly Feb 13, 2019
acfe58e
Merge branch 'master' of github.com:launchdarkly/python-client
eli-darkly Feb 13, 2019
87336db
use default theme
eli-darkly Feb 13, 2019
c7a67dc
Merge branch 'master' of github.com:launchdarkly/python-client
eli-darkly Feb 13, 2019
84198a3
try python -m instead of pytest directly
hroederld Mar 1, 2019
80411dd
add setuptools
hroederld Mar 1, 2019
52c0a19
use python -m for all of pip
hroederld Mar 1, 2019
5bdea5f
add UsePythonVersion task
hroederld Mar 1, 2019
60a66a8
fix indent
hroederld Mar 1, 2019
1907d75
remove manually adding setuptools
hroederld Mar 1, 2019
7cdf9fc
add on 3.7 stages
hroederld Mar 2, 2019
1023d45
fix mkdir for reports
hroederld Mar 2, 2019
b9778b6
upload test artifacts
hroederld Mar 2, 2019
945fc07
Merge pull request #100 from launchdarkly/hr/azurepytest
hroederld Mar 2, 2019
7738c99
Merge commit '327aaac4a5c419ea45d3723d4a87309f67da4a40'
eli-darkly Mar 13, 2019
e5d5e41
skip trying to load pyyaml in Python 3.3
eli-darkly Mar 26, 2019
fd883cd
can't use watchdog in Python 3.3
eli-darkly Mar 26, 2019
b3dc4c4
mark test as skipped
eli-darkly Mar 26, 2019
bd4daf7
Merge pull request #101 from launchdarkly/eb/ch34481/pyyaml-py3.3
eli-darkly Mar 26, 2019
803a794
coerce user attributes into strings when necessary, don't send events…
eli-darkly Mar 29, 2019
b7035a5
more unit tests
eli-darkly Mar 29, 2019
44101b2
remove redundant sanitize step
eli-darkly Mar 29, 2019
4b8ee84
Merge pull request #102 from launchdarkly/eb/ch35206/stringify-attrs
eli-darkly Mar 29, 2019
dd67a7c
merge from public after release
LaunchDarklyCI Mar 29, 2019
ddfb3c2
ensure that client components are cleaned up correct in every configu…
eli-darkly Apr 9, 2019
4ca26c7
Merge pull request #103 from launchdarkly/eb/ch36211/close-ldd
eli-darkly Apr 9, 2019
7585684
miscellaneous test fixes
eli-darkly Apr 9, 2019
a164906
Merge pull request #104 from launchdarkly/eb/fix-tests
eli-darkly Apr 9, 2019
143b66a
merge from public after release
LaunchDarklyCI Apr 10, 2019
950d2b3
Merge branch 'master' of github.com:launchdarkly/python-client
eli-darkly Apr 24, 2019
902be02
update readme format and repo links
eli-darkly Apr 26, 2019
f41f2cc
allow unit tests to be run without databases
eli-darkly Apr 26, 2019
d764fd8
add missing test
eli-darkly Apr 26, 2019
91b1250
Merge pull request #107 from launchdarkly/eb/ch37610/no-db-tests
eli-darkly Apr 26, 2019
ea5d8e8
rm FOSSA link/badge
eli-darkly Apr 26, 2019
6ed12f1
misc fixes
eli-darkly Apr 26, 2019
6cd745f
Merge pull request #106 from launchdarkly/eb/ch36754/readme-update
eli-darkly Apr 26, 2019
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
54 changes: 35 additions & 19 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,33 +1,49 @@
Contributing
------------
# Contributing to the LaunchDarkly Server-side SDK for Python

We encourage pull-requests and other contributions from the community. We've also published an [SDK contributor's guide](http://docs.launchdarkly.com/docs/sdk-contributors-guide) that provides a detailed explanation of how our SDKs work.
LaunchDarkly has published an [SDK contributor's guide](https://docs.launchdarkly.com/docs/sdk-contributors-guide) that provides a detailed explanation of how our SDKs work. See below for additional information on how to contribute to this SDK.

Development information (for developing this module itself)
-----------------------------------------------------------
## Submitting bug reports and feature requests

The LaunchDarkly SDK team monitors the [issue tracker](https://github.com/launchdarkly/python-server-sdk/issues) in the SDK repository. Bug reports and feature requests specific to this SDK should be filed in this issue tracker. The SDK team will respond to all newly filed issues within two business days.

1. One-time setup:
## Submitting pull requests

We encourage pull requests and other contributions from the community. Before submitting pull requests, ensure that all temporary or unintended code is removed. Don't worry about adding reviewers to the pull request; the LaunchDarkly SDK team will add themselves. The SDK team will acknowledge all pull requests within two business days.

mkvirtualenv python-client
## Build instructions

1. When working on the project be sure to activate the python-client virtualenv using the technique of your choosing.
### Setup

1. Install requirements (run-time & test):
It's advisable to use [`virtualenv`](https://virtualenv.pypa.io/) to create a development environment within the project directory:

pip install -r requirements.txt
pip install -r test-requirements.txt
```
mkvirtualenv python-client
source ./python-client/bin/activate
```

1. When running unit tests, in order for `test_feature_store.py` to run, you'll need all of the supported databases (Redis, Consul, DynamoDB) running locally on their default ports.
To install the runtime and test requirements:

1. If you want integration tests to run, set the ```LD_SDK_KEY``` environment variable to a valid production SDK Key.
```
pip install -r requirements.txt
pip install -r test-requirements.txt
```

1. ```$ py.test testing```
The additional requirements files `consul-requirements.txt`, `dynamodb-requirements.txt`, `redis-requirements.txt`, and `test-filesource-optional-requirements.txt` can also be installed if you need to test the corresponding features.

1. All code must be compatible with all supported Python versions as described in README. Most portability issues are addressed by using the `six` package. We are avoiding the use of `__future__` imports, since they can easily be omitted by mistake causing code in one file to behave differently from another; instead, whenever possible, use an explicit approach that makes it clear what the desired behavior is in all Python versions (e.g. if you want to do floor division, use `//`; if you want to divide as floats, explicitly cast to floats).
### Testing

Developing with different Python versions
-----------------------------------------
To run all unit tests:

Example for switching to Python 3:
```
pytest
```

```virtualenv -p `which python3` ~/.virtualenvs/python-client```
By default, the full unit test suite includes live tests of the integrations for Consul, DynamoDB, and Redis. Those tests expect you to have instances of all of those databases running locally. To skip them, set the environment variable `LD_SKIP_DATABASE_TESTS=1` before running the tests.

There are also integration tests that can be run against the LaunchDarkly service. To enable them, set the environment variable `LD_SDK_KEY` to a valid production SDK Key.

### Portability

Most portability issues are addressed by using the `six` package. We are avoiding the use of `__future__` imports, since they can easily be omitted by mistake causing code in one file to behave differently from another; instead, whenever possible, use an explicit approach that makes it clear what the desired behavior is in all Python versions (e.g. if you want to do floor division, use `//`; if you want to divide as floats, explicitly cast to floats).

It is preferable to run tests against all supported minor versions of Python (as described in `README.md` under Requirements), or at least the lowest and highest versions, prior to submitting a pull request. However, LaunchDarkly's CI tests will run automatically against all supported versions.
129 changes: 20 additions & 109 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,138 +1,49 @@
LaunchDarkly SDK for Python
===========================
# LaunchDarkly Server-side SDK for Python

[![Circle CI](https://img.shields.io/circleci/project/launchdarkly/python-client.png)](https://circleci.com/gh/launchdarkly/python-client)

[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Flaunchdarkly%2Fpython-client.svg?type=shield)](https://app.fossa.io/projects/git%2Bhttps%3A%2F%2Fgithub.com%2Flaunchdarkly%2Fpython-client?ref=badge_shield)
[![Circle CI](https://img.shields.io/circleci/project/launchdarkly/python-server-sdk.png)](https://circleci.com/gh/launchdarkly/python-server-sdk)

[![PyPI](https://img.shields.io/pypi/v/ldclient-py.svg?maxAge=2592000)](https://pypi.python.org/pypi/ldclient-py)
[![PyPI](https://img.shields.io/pypi/pyversions/ldclient-py.svg)](https://pypi.python.org/pypi/ldclient-py)

[![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)

Supported Python versions
-------------------------

This version of the LaunchDarkly SDK is compatible with Python 2.7, and Python 3.3 through 3.7.

Quick setup
-----------

1. Install the Python SDK with `pip`

pip install ldclient-py

2. Configure the library with your sdk key:

import ldclient

3. Get the client:

ldclient.set_sdk_key("your sdk key")
client = ldclient.get()


HTTPS proxy
------------
Python's standard HTTP library provides built-in support for the use of a HTTPS proxy. If the HTTPS_PROXY environment variable is present then the SDK will proxy all network requests through the URL provided.
## LaunchDarkly overview

How to set the HTTPS_PROXY environment variable on Mac/Linux systems:
```
export HTTPS_PROXY=https://web-proxy.domain.com:8080
```


How to set the HTTPS_PROXY environment variable on Windows systems:
```
set HTTPS_PROXY=https://web-proxy.domain.com:8080
```

Or it can be set from within python:
```
os.environ["https_proxy"] = "https://web-proxy.domain.com:8080"
```

If your proxy requires authentication then you can prefix the URN with your login information:
```
export HTTPS_PROXY=http://user:pass@web-proxy.domain.com:8080
```
or
```
set HTTPS_PROXY=http://user:pass@web-proxy.domain.com:8080
```


Your first feature flag
-----------------------

1. Create a new feature flag on your [dashboard](https://app.launchdarkly.com)
2. In your application code, use the feature's key to check whether the flag is on for each user:

if client.variation("your.flag.key", {"key": "user@test.com"}, False):
# application code to show the feature
else:
# the code to run if the feature is off

Supported Python versions
-------------------------

The SDK is tested with the most recent patch releases of Python 2.7, 3.3, 3.4, 3.5, and 3.6. Python 2.6 is no longer supported.

Database integrations
---------------------
[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/docs/getting-started) using LaunchDarkly today!

[![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)

Feature flag data can be kept in a persistent store using Consul, DynamoDB, or Redis. These adapters are implemented in the `Consul`, `DynamoDB` and `Redis` classes in `ldclient.integrations`; to use them, call the `new_feature_store` method in the appropriate class, and put the returned object in the `feature_store` property of your client configuration. See [`ldclient.integrations`](https://launchdarkly-python-sdk.readthedocs.io/en/latest/api-integrations.html#module-ldclient.integrations) and the [SDK reference guide](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store) for more information.
## Supported Python versions

Note that Consul is not supported in Python 3.3 or 3.4.
This version of the LaunchDarkly SDK is compatible with Python 2.7 and 3.3 through 3.7. It is tested with the most recent patch releases of those versions. Python 2.6 is no longer supported.

Using flag data from a file
---------------------------
## Getting started

For testing purposes, the SDK can be made to read feature flag state from a file or files instead of connecting to LaunchDarkly. See [`ldclient.integrations.Files`](https://launchdarkly-python-sdk.readthedocs.io/en/latest/api-integrations.html#ldclient.integrations.Files) and the [SDK reference guide](https://docs.launchdarkly.com/v2.0/docs/reading-flags-from-a-file) for more details.
Refer to the [SDK reference guide](https://docs.launchdarkly.com/docs/python-sdk-reference) for instructions on getting started with using the SDK.

Learn more
----------
## Learn more

Check out our [documentation](http://docs.launchdarkly.com) for in-depth instructions on configuring and using LaunchDarkly. You can also head straight to the [complete reference guide for this SDK](http://docs.launchdarkly.com/docs/python-sdk-reference).

Generated API documentation is on [readthedocs.io](https://launchdarkly-python-sdk.readthedocs.io/en/latest/).

Testing
-------
## Testing

We run integration tests for all our SDKs using a centralized test harness. This approach gives us the ability to test for consistency across SDKs, as well as test networking behavior in a long-running application. These tests cover each method in the SDK, and verify that event sending, flag evaluation, stream reconnection, and other aspects of the SDK all behave correctly.

[![Test Coverage](https://codeclimate.com/github/launchdarkly/python-client/badges/coverage.svg)](https://codeclimate.com/github/launchdarkly/python-client/coverage) The Code Climate coverage does not include the coverage provided by this integration test harness.

Contributing
------------
## Contributing

See [CONTRIBUTING](CONTRIBUTING.md) for more information.
We encourage pull requests and other contributions from the community. Check out our [contributing guidelines](CONTRIBUTING.md) for instructions on how to contribute to this SDK.

About LaunchDarkly
------------------
## About LaunchDarkly

* LaunchDarkly is a continuous delivery platform that provides feature flags as a service and allows developers to iterate quickly and safely. We allow you to easily flag your features and manage them from the LaunchDarkly dashboard. With LaunchDarkly, you can:
* Roll out a new feature to a subset of your users (like a group of users who opt-in to a beta tester group), gathering feedback and bug reports from real-world use cases.
* Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
* Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
* Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
* LaunchDarkly provides feature flag SDKs for
* [Java](http://docs.launchdarkly.com/docs/java-sdk-reference "LaunchDarkly Java SDK")
* [JavaScript](http://docs.launchdarkly.com/docs/js-sdk-reference "LaunchDarkly JavaScript SDK")
* [PHP](http://docs.launchdarkly.com/docs/php-sdk-reference "LaunchDarkly PHP SDK")
* [Python](http://docs.launchdarkly.com/docs/python-sdk-reference "LaunchDarkly Python SDK")
* [Go](http://docs.launchdarkly.com/docs/go-sdk-reference "LaunchDarkly Go SDK")
* [Node.JS](http://docs.launchdarkly.com/docs/node-sdk-reference "LaunchDarkly Node SDK")
* [Electron](http://docs.launchdarkly.com/docs/electron-sdk-reference "LaunchDarkly Electron SDK")
* [.NET](http://docs.launchdarkly.com/docs/dotnet-sdk-reference "LaunchDarkly .Net SDK")
* [Ruby](http://docs.launchdarkly.com/docs/ruby-sdk-reference "LaunchDarkly Ruby SDK")
* [iOS](http://docs.launchdarkly.com/docs/ios-sdk-reference "LaunchDarkly iOS SDK")
* [Android](http://docs.launchdarkly.com/docs/android-sdk-reference "LaunchDarkly Android SDK")
* [C/C++](http://docs.launchdarkly.com/docs/c-sdk-reference "LaunchDarkly C/C++ SDK")
* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/docs) for a complete list.
* Explore LaunchDarkly
* [launchdarkly.com](http://www.launchdarkly.com/ "LaunchDarkly Main Website") for more information
* [docs.launchdarkly.com](http://docs.launchdarkly.com/ "LaunchDarkly Documentation") for our documentation and SDKs
* [apidocs.launchdarkly.com](http://apidocs.launchdarkly.com/ "LaunchDarkly API Documentation") for our API documentation
* [blog.launchdarkly.com](http://blog.launchdarkly.com/ "LaunchDarkly Blog Documentation") for the latest product updates
* [launchdarkly.com](https://www.launchdarkly.com/ "LaunchDarkly Main Website") for more information
* [docs.launchdarkly.com](https://docs.launchdarkly.com/ "LaunchDarkly Documentation") for our documentation and SDK reference guides
* [apidocs.launchdarkly.com](https://apidocs.launchdarkly.com/ "LaunchDarkly API Documentation") for our API documentation
* [blog.launchdarkly.com](https://blog.launchdarkly.com/ "LaunchDarkly Blog Documentation") for the latest product updates
* [Feature Flagging Guide](https://github.com/launchdarkly/featureflags/ "Feature Flagging Guide") for best practices and strategies
4 changes: 2 additions & 2 deletions scripts/release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
# When done you should commit and push the changes made.

set -uxe
echo "Starting python-client release."
echo "Starting python-server-sdk release."

VERSION=$1

Expand All @@ -28,4 +28,4 @@ python setup.py sdist
pip install twine
python -m twine upload dist/*

echo "Done with python-client release"
echo "Done with python-server-sdk release"
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ def run(self):
author='LaunchDarkly',
author_email='team@launchdarkly.com',
packages=find_packages(),
url='https://github.com/launchdarkly/python-client',
url='https://github.com/launchdarkly/python-server-sdk',
description='LaunchDarkly SDK for Python',
long_description='LaunchDarkly SDK for Python',
install_requires=reqs,
Expand Down
31 changes: 18 additions & 13 deletions testing/test_feature_store.py
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
import boto3
import json
import os
import pytest
import redis
import time
Expand Down Expand Up @@ -165,19 +166,23 @@ def _clear_data(self):


class TestFeatureStore:
params = [
InMemoryTester(),
RedisTester(CacheConfig.default()),
RedisTester(CacheConfig.disabled()),
RedisWithDeprecatedConstructorTester(CacheConfig.default()),
RedisWithDeprecatedConstructorTester(CacheConfig.disabled()),
DynamoDBTester(CacheConfig.default()),
DynamoDBTester(CacheConfig.disabled())
]

if have_consul:
params.append(ConsulTester(CacheConfig.default()))
params.append(ConsulTester(CacheConfig.disabled()))
if os.environ.get('LD_SKIP_DATABASE_TESTS') == '1':
params = [
InMemoryTester()
]
else:
params = [
InMemoryTester(),
RedisTester(CacheConfig.default()),
RedisTester(CacheConfig.disabled()),
RedisWithDeprecatedConstructorTester(CacheConfig.default()),
RedisWithDeprecatedConstructorTester(CacheConfig.disabled()),
DynamoDBTester(CacheConfig.default()),
DynamoDBTester(CacheConfig.disabled())
]
if have_consul:
params.append(ConsulTester(CacheConfig.default()))
params.append(ConsulTester(CacheConfig.disabled()))

@pytest.fixture(params=params)
def tester(self, request):
Expand Down