Refactoring #1064

Get rid of "pylab" in Python scripts

Added by wuttke almost 5 years ago. Updated over 4 years ago.

Status:ArchivedStart date:07 May 2015
Priority:NormalDue date:
Assignee:pospelov% Done:

0%

Category:-
Target version:Sprint 29

Description

In my understanding, "pylab" is nothing more than a very thin layer on top of numpy and matplotlib. Its maintenance status appears questionable. Calling numpy and matplotlib through pylab in our examples has little advantage for superficial users (just makes the code a few bytes shorter), but is annoying for those who want to modify the example code (obsures which modules are actually used, and thereby makes lookup in the API docs more difficult).

History

#1 Updated by wuttke almost 5 years ago

  • Description updated (diff)

#2 Updated by pospelov over 4 years ago

  • Status changed from New to Sprint

#3 Updated by pospelov over 4 years ago

  • Target version set to Sprint 29

#4 Updated by pospelov over 4 years ago

  • Assignee set to pospelov

I take this, it fits refactoring I'm doing now in python examples (related to the IntensityData and Fitting API changes)

#5 Updated by pospelov over 4 years ago

  • Status changed from Sprint to Resolved

#6 Updated by pospelov over 4 years ago

  • Status changed from Resolved to Archived

Also available in: Atom PDF