Skip to content
This repository was archived by the owner on Oct 23, 2023. It is now read-only.

Conversation

@dcramer
Copy link
Member

@dcramer dcramer commented May 13, 2015

Passing a transport via a scheme prefix is now deprecated in favor of explicit class loading:

>>> Client(dsn, transport=HttpTransport)

Additionally DSN-related configuration is now held in the RemoteConfig helper, which is bound on Client.remote.

This removes raven.conf.load but otherwise should be backwards compatible.

Fixes GH-587

Review on Reviewable

@dcramer
Copy link
Member Author

dcramer commented May 13, 2015

There will be a followup backwards incompatible change that removes binding of Transports to a URL. They will become generic reusable for any HTTP connection. It will only cause problems for people with custom transports (which is likely very few people).

@dcramer dcramer force-pushed the dsn-refactor branch 6 times, most recently from 6e63f8b to 923be66 Compare May 20, 2015 22:19
@dcramer dcramer force-pushed the dsn-refactor branch 2 times, most recently from d737862 to 8492a43 Compare May 22, 2015 00:07
Passing a transport via a scheme prefix is now deprecated in favor of explicit class loading:

>>> Client(dsn, transport=HttpTransport)

Additionally DSN-related configuration is now held in the RemoteConfig helper, which is bound on Client.remote.

Fixes GH-587
@dcramer dcramer merged commit 12bb737 into master May 22, 2015
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 12bb737 on dsn-refactor into ** on master**.

@ashwoods ashwoods deleted the dsn-refactor branch October 29, 2017 19:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecate DSN-based transport configuration

3 participants