Simple and efficient tools for data mining and data analysis
Accessible to everybody, and reusable in various contexts
Built on NumPy, SciPy, and matplotlib
Open source, commercially usable - BSD license

More at http://scikit-learn.org/stable/index.html

Address of the bookmark: http://scikit-learn.org/stable/auto_examples/index.html

Professionally, Python is great for backend web development, data analysis, artificial intelligence, and scientific computing. Many developers have also used Python to build productivity tools, games, and desktop apps, so there are plenty of resources to help you learn how to do those as well.

For pros and cons visit http://www.bestprogramminglanguagefor.me/why-learn-python and http://bioinformaticsonline.com/discussion/view/459/python-vs-perl

More resources at https://github.com/CodementorIO/Python-Learning-Resources

Following are the list of useful python programming resources:

• 20 Python Libraries You Aren't Using (But Should) (Just fill the fields with any values)
• A Beginner's Python Tutorial
• A Byte of Python (3.x) (HTML, PDF, EPUB, Mobi)
• A Guide to Python's Magic Methods - Rafe Kettler
• A Whirlwind Tour of Python - Jake VanderPlas (PDF) (EPUB, MOBI)
• Automate the Boring Stuff - Al Sweigart
• Biopython (PDF)
• Build applications in Python the antitextbook (3.x) (HTML, PDF, EPUB, Mobi)
• Building Machine Learning Systems with Python - Willi Richert & Luis Pedro Coelho, Packt. (Just fill the fields with any values)
• Building Skills in Object-Oriented Design (Python) (PDF) (2.1.1)
• Building Skills in Python (PDF) (2.6)
• Code Like a Pythonista: Idiomatic Python
• CodeCademy Python
• Composing Programs (3.x)
• Data Structures and Algorithms in Python - B. R. Preiss (PDF)
• Dive into Python 3 - Mark Pilgrim (3.0)
  • Dive into Python - Mark Pilgrim (2.3)
• From Python to NumPy
• Full Stack Python
• Functional Programming in Python (Just fill the fields with any values)
• Fundamentals of Python Programming - Richard L. Halterman (PDF) (3.2)
• Google's Python Class (2.4 - 2.x)
• Google's Python Style Guide
• Hacking Secret Cyphers with Python - Al Sweigart (3.3)
• Hadoop with Python (Just fill the fields with any values)
• High Performance Python (PDF)
• Hitchhiker's Guide to Python! (2.6)
• How to Make Mistakes in Python - Mike Pirnat (PDF) (1st edition)
• How to Think Like a Computer Scientist: Learning with Python, Interactive Edition (3.2)
  • How to Think Like a Computer Scientist: Learning with Python - Allen B. Downey, Jeff Elkner and Chris Meyers (2.4)
  • Think Python - Allen B. Downey (2.x & 3.0)
• Intermediate Python - Muhammad Yasoob Ullah Khalid (1st edition)
• Introduction to Programming with Python (3.3)
  • Introduction to Programming Using Python - Cody Jackson (1st edition) (2.3)
• Introduction to Python - Kracekumar (2.7.3)
• Invent Your Own Computer Games With Python - Al Sweigart (3.1)
• Learn Python, Break Python
• Learn Python in Y minutes
• Learn Python The Hard Way (2.5 - 2.6)
• Learn to Program Using Python - Cody Jackson (PDF)
• Learning Python - Fabrizio Romano, Packt. (Just fill the fields with any values)
• Learning to Program
• Lectures on scientific computing with python - J.R. Johansson (2.7)
• Making Games with Python & Pygame - Al Sweigart (2.7)
• Modeling Creativity: Case Studies in Python - Tom D. De Smedt (PDF)
• Natural Language Processing with Python (3.x)
• Non-Programmer's Tutorial for Python 3 (3.3)
  • Non-Programmer's Tutorial for Python 2.6 (2.6)
• Picking a Python Version: A Manifesto (Just fill the fields with any values)
• Porting to Python 3: An In-Depth Guide (2.6 - 2.x & 3.1 - 3.x)
• Practical Programming in Python - Jeffrey Elkner (PDF)
• Problem Solving with Algorithms and Data Structures using Python - Bradley N. Miller and David L. Ranum
• Program Arcade Games With Python And Pygame (3.3)
• Programming Computer Vision with Python (PDF)
• Python 2 Official Documentation (PDF, HTML, TEXT) (2.x)
• Python 2.7 quick reference - New Mexico Tech (2.7)
• Python 3 Official Documentation (PDF, EPUB, HTML, TEXT) (3.x)
• Python Cookbook - David Beazley
• Python Data Science Handbook - Jake VanderPlas (HTML, Jupyter Notebooks)
• Python for Econometrics - Kevin Sheppard (PDF) (2.7.5)
• Python for Everybody Exploring Data Using Python 3 - Charles Severance (PDF, EPUB, HTML)
  • Python for Informatics: Exploring Information (2.7.5)
• Python for you and me (2.7.3)
• Python for you and me (3.x)
• Python Idioms (PDF)
• Python in Education (Just fill the fields with any values)
• Python in Hydrology - Sat Kumar Tomer
• Python Koans (2.7 or 3.x)
• Python Module of the Week (3.x)
  • Python Module of the Week (2.x)
• Python Notes for Professionals - Compiled from StackOverflow documentation (3.x)
• Python Practice Book (2.7.1)
• Python Practice Projects
• Python Programming (PDF) (2.6)
• Scipy Lecture Notes
• SICP in Python (3.2)
• Snake Wrangling For Kids (3.x)
• Suporting Python 3: An In-Depth Guide (2.6 - 2.x & 3.1 - 3.x)
• Test-Driven Web Development with Python (3.3 - 3.x)
• Text Processing in Python - David Mertz (2.3 - 2.x)
• The Coder's Apprentice: Learning Programming with Python 3 - Pieter Spronck (PDF) (3.x)
• The Definitive Guide to Jython, Python for the Java Platform - Josh Juneau, Jim Baker, Victor Ng, Leo Soto, Frank Wierzbicki (2.5)
• The Little Book of Python Anti-Patterns (Source)
• The Programming Historian - William J. Turkel, Adam Crymble and Alan MacEachern
• The Python Ecosystem: An Introduction
• The Python GTK+ 3 Tutorial
• The Standard Python Library - Fredrik Lundh
• Think Complexity - Allen B. Downey (2nd Edition) (PDF, HTML)
• Web2py: Complete Reference Manual, 6th Edition (pre-release) (2.5 - 2.x)
• Wikibooks: Python Programming (2.7)

Dash Bio is a suite of bioinformatics components that make it simpler to analyze and visualize bioinformatics data and interact with them in a Dash application.

The source can be found on GitHub at plotly/dash-bio.

These docs are using Dash Bio version 0.1.4.

Address of the bookmark: https://dash.plot.ly/dash-bio

Address of the bookmark: https://github.com/wtmatlock/flanker

Address of the bookmark: https://github.com/dentearl/evolverSimControl

Address of the bookmark: https://sourceforge.net/projects/contiguator/

The image summarise all in one.

More at http://users.rcn.com/jkimball.ma.ultranet/BiologyPages/C/Codons.html

In C, "sequence statements" are imperatives. The "selection" is the "if then else" statement, and the iteration is satisfied by a number of statements, such as the "while," " do," and the "for," while the case-type statement is satisfied by the "switch" statement.

Pseudocode is an artificial and informal language that helps programmers develop algorithms. Pseudocode is a "text-based" detail (algorithmic) design tool.

The rules of Pseudocode are reasonably straightforward. All statements showing "dependency" are to be indented. These include while, do, for, if, switch. Examples below will illustrate this notion.

GUIDE TO PSEUDOCODE LEVEL OF DETAIL: Given record/file descriptions, pseudocode should be created in sufficient detail so as to directly support the programming effort. It is the purpose of pseudocode to elaborate on the algorithmic detail and not just cite an abstraction.

Examples:

1.

If student's grade is greater than or equal to 60
    Print "passed"
else
    Print "failed"  
endif

2.

  
Set total to zero
Set grade counter to one
While grade counter is less than or equal to ten
    Input the next grade
    Add the grade into the total
endwhile 
Set the class average to the total divided by ten
Print the class average.

3.

Initialize total to zero
Initialize counter to zero
Input the first grade
while the user has not as yet entered the sentinel
   add this grade into the running total 
   add one to the grade counter  
   input the next grade (possibly the sentinel)
endwhile

if the counter is not equal to zero
   set the average to the total divided by the counter
   print the average  
else
   print 'no grades were entered' 
endif 

4.

initialize passes to zero
initialize failures to zero
initialize student to one
while student counter is less than or equal to ten
    input the next exam result  
    if the student passed

add one to passes else add one to failures add one to student counter endif endwhile print the number of passes print the number of failures if eight or more students passed print "raise tuition" endif

5.

Larger example:  

NOTE:  NEVER ANY DATA DECLARATIONS IN PSEUDOCODE

Print out appropriate heading and make it pretty
While not EOF do:
     Scan over blanks and white space until a char is found 
	(get first character on the line)
     set can't-be-ascending-flag to 0
     set consec cntr to 1
     set ascending cntr to 1
     putchar first char of string to screen
     set read character to hold character
     While next character read != blanks and white space
          putchar out on screen
          if new char = hold char + 1
               add 1 to consec cntr
               set hold char = new char
               continue
          endif
          if new char >= hold char 
               if consec cntr < 3 
                    set consec cntr to 1
               endif
               set hold char = new char
               continue
          endif
          if new char < hold char
               if consec cntr < 3
                    set consec cntr to 1
               endif
               set hold char = new char
               set can't be ascending flag to 1
               continue
           endif
     end while
     if consec cntr >= 3 
          printf (Appropriate message 1 and skip a line)
          add 1 to consec total
     endif
     if  can't be ascending flag = 0
          printf (Appropriate message 2 and skip a line)
          add 1 to ascending total
     else
          printf (Sorry message and skip a line)
          add 1 to sorry total
     endif
end While
Print out totals:  Number of consecs, ascendings, and sorries.
Stop

Some Keywords That Should be Used And Additional Points

For looping and selection, The keywords that are to be used include Do While...EndDo; Do Until...Enddo; While .... Endwhile is acceptable. Also, Loop .... endloop is also VERY good and is language independent. Case...EndCase; If...Endif; Call ... with (parameters); Call; Return ....; Return; When;

Always use scope terminators for loops and iteration.

As verbs, use the words Generate, Compute, Process, etc. Words such as set, reset, increment, compute, calculate, add, sum, multiply, ... print, display, input, output, edit, test , etc. with careful indentation tend to foster desirable pseudocode. Also, using words such as Set and Initialize, when assigning values to variables is also desirable.

More on Formatting and Conventions in Pseudocoding

• INDENTATION in pseudocode should be identical to its implementation in a programming language. Try to indent at least four spaces.
• As noted above, the pseudocode entries are to be cryptic, AND SHOULD NOT BE PROSE. NO SENTENCES.
• No flower boxes (discussed ahead) in your pseudocode.
• Do not include data declarations in your pseudocode.
• But do cite variables that are initialized as part of their declarations. E.g. "initialize count to zero" is a good entry.

  ---

  Function Calls, Function Documentation, and Pseudocode
• Calls to Functions should appear as:
• Returns in functions should appear as:
• Function headers should appear as:
• Note that in C, arguments and parameters such as "fieldn" could be written: "pointer to fieldn ...."
• Functions called with addresses should be written as:
• Function headers containing pointers should be indicated as:
• Returns in functions where a pointer is returned:
• It would not hurt the appearance of your pseudocode to draw a line or make your function header line "bold" in your pseudocode. Try to set off your functions.
• Try to use scope terminators in your pseudocode and source code too. It really hels the readability of the text.

  ---

  Source Code
• EVERY function should have a flowerbox PRECEDING IT. This flower box is to include the functions name, the main purpose of the function, parameters it is expecting (number and type), and the type of the data it returns. All of these listed items are to be on separate lines with spaces in between each explanatory item.
• FORMAT of flowerbox should be

   

  	 ********************************************************
  	 Function:   ( cryptic text describing single function
  		     ....... (indented like this) 	
  		     .......
  	 Calls:      Start listing functions "this" function calls
  		     Show these functions:  one per line, indented
  
  	 Called by:  List of functions that calls "this" function
  		     Show these functions:  one per line, indented.
  
  	 Input Parameters:  list, if appropriate; else None
  	 
  	 Returns:    List, if appropriate.
  	 ****************************************************************
  

• INDENTATION is critically important in Source Code. Follow standard examples given in class. If in doubt, ASK. Always indent statements within IFs, FOR loops, WILLE loops, SWITCH statements, etc. a consistent number of spaces, such as four. Alternatively, use the tab key. One or two spaces is insufficient.
• Use scope terminators at the end of if statements, for statements, while statements, and at the end of functions. It will make your program much more readable.

  SPELLING ERRORS ARE NOT ACCEPTABLE