Bug 393 – QNetworkReply.error should be both signal and method

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 393 - QNetworkReply.error should be both signal and method

Summary:

QNetworkReply.error should be both signal and method

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtNetwork
Version:	HEAD
Platform:	All All

Importance:	P3 major
Assigned To:	Marcelo Lira

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-09-29 09:36 EEST by Marcelo Lira
Modified:	2010-11-25 17:48 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marcelo Lira 2010-09-29 09:36:18 EEST

In C++ QNetworkReply.error is both a method:

NetworkError QNetworkReply::error () const

and a signal:

void QNetworkReply::error ( QNetworkReply::NetworkError code ) [signal]

Currently the PySide bindings exports only the signal version of "error".

Comment 1 Hugo Parente Lima 2010-09-29 11:58:00 EEST

This method was renamed to errorCode().

Comment 2 Marcelo Lira 2010-10-13 16:33:47 EEST

QNetworkReply.errorCode is once again called QNetworkReply.error.

Fixed in commits Shiboken/1.0/d0a0db84, PySide/1.0/c86a509a

Comment 3 renato filho 2010-11-25 17:48:10 EET

released on 1.0.0~beta1