Would storing this information in the pipeline instance suffice or are you looking for realtime feedback? Obviously storing on the pipeline instance means the information disappears after a cross_val_score or *SearchCV run.

Realtime feedback, like the highest verbosity on GridSearchCV. When pipelines get long it is useful to know what stage they are at.

I'd be okay with this.

On 24 September 2015 at 06:04, Sam Zhang [email protected] wrote:

Realtime feedback, like the highest verbosity on GridSearchCV. When
pipelines get long it is useful to know what stage they are at.

—
Reply to this email directly or view it on GitHub
#5298 (comment)
.

Yeah I feel optional verbosity is usually good.

I would like to take this up, if it is still available.

For some reason the appveyor build on my PR failed, but Circle and Travis passed. The errors looked to be located outside my PR. If there's any additional work that needs to be done for a merge, feel free to help out.

@amandeepgautam There is an active PR at #5321 Could you take up some other issue to work on?

#5321 is stalled.

@karandesai-96, if you're bored, you can tackle getting this verbose logging consistent... I'd like to see FeatureUnion covered too.

@jnothman It has been a week since you last commented so I thought it would be better to inform, I am occupied with a couple of open PRs elsewhere so will return to this once they get approved, thanks.

@amueller @jnothman I have a PR open (#8568). Though it is WIP, I ensure you that it would be done within some time. Safe to remove Need Contributor label here 😄

@karandesai-96 any update?

I guess stalled again?

need more verbosity

No updates?