Back in August, van Rossum published a proposal on the Python mailing list recommending type-checking annotations as a valuable feature for the next version of Python to improve the performance of editors and IDEs, linter capabilities, standard notation, and refactoring. Van Rossum’s latest proposal, posted late last month, outlined plans to publish a Python Enhancement Proposal (PEP) in early January to put the feature now known as type hinting on track for inclusion in Python 3.5, slated for release this September.

Reference

https://quip.com/r69HA9GhGa7J

ICRISAT is headquartered in Patancheru near Hyderabad, India, with two regional hubs and five country offices in sub-Saharan Africa. ICRISAT, established in 1972, is a member of the CGIAR Consortium. For more details, see www.icrisat.org.

Responsibilities:Design efficient SQL queries for pulling large sequencing projects.
Serve as a technical adviser to the project leadership and provide computational perspective on product design and deliverability.
Develop and oversee a rapid and incremental software development and release schedule.
Design the software architecture, oversee the implementation and evolution of the design on appropriate hardware platforms.
Working collaboratively in a team environment to design, code, test, debug, and document programs for an integrated genomic analysis pipeline in a rapid and incremental software development and release schedule.
Supervise and review code development and ensure that software products meet project objectives in terms of functionality, scalability, robustness and user experience.
Implement and oversee the QA/QC practices to ensure the development team is adhering to quality standards.
Work closely with the application specialist to integrate feedbacks from teams in each CGIAR center into software customization and improvement.
Assist in training of breeders in the CGIAR centers to use software developed.
Personal Profile:

The applicant should have:

Understanding of genomics data and advanced knowledge of Java, and C/C++ as the programming languages and any of the scripting language like perl and/or Python, SQL
High Performance Computing, data architecture, database platforms and QA/QC practices in software engineering.
She/he should have solid experience in software development projects, preferably as a senior programmer or in the software project management role, and in projects involving big data.
Excellent communication skills are needed to work in this multi-disciplinary, multi-location and multi-cultural team.
Ability to mentor colleagues in quality software development practices is desired.
Educational Qualification : Ph. D or Masters Degree in Computational Biology / Computational Genomics or Equivalent with Research Experience in Mentioned Areas.

More at http://www.icrisat.org/careers/

The primary home page for DendroPy, with detailed tutorials and documentation, is at:

http://dendropy.org/

DendroPy is also hosted in the official Python repository:

http://packages.python.org/DendroPy/

Address of the bookmark: https://pypi.org/project/DendroPy/

What Is Julia Language?

Julia is a programming language that came into the limelight in 2012. It is a general-purpose programming language that was designed for solving scientific computations. Julia was meant to be an alternative to Python, R and other programming languages that were mainly used for manipulating data. This is because it has numerous features that can minimize the complexities of numerical computations. 

Julia optimizes on the best features of Python and R while at the same time overlooks their weaknesses. This explains why it is viewed as an alternative to these programming languages. For instance, it utilizes the readability and simplicity of Python then performs faster.

Julia is the most preferred programming language for data scientists and mathematicians. This is because its core features are similar to the ones that are used on most data software. Also, the language is ideal for these two subjects because its syntax is similar to the standard mathematical formulas.

Key Features Of Julia Language
Uses JIT Compilation
Parallelism
Dynamic Typing
Simple Syntax
Allows Metaprogramming
Accessible to Libraries
-1-Array Indexing

Julia Vs Python And R Programming Languages
1. Speed
Julia is faster than both Python and R. This is a very critical aspect that is given special attention in the big data programming. The high speed of Julia is because of JIT compilers. You will need to install external libraries on Python to achieve similar speed.

2. Syntax
Julia has a math-friendly syntax. The syntax of this programming language is similar to the mathematical formulas hence can be used to perform mathematical and scientific computations. This syntax makes it easier to learn than Python.

3. Parallelism
Although both Python and R use parallelism, Julia uses a top-level parallelism. Julia allows the processor to perform to the optimum level than what Python and R can achieve.

4. Versatility
Julia programming language is more versatile than Python and R. It allows a programmer to move from different codes and functions with ease.

The only area that Python and R are superior to Julia is in terms of community. Given that Julia is a new programming language, it has a small community as compared to others which have been around for years.

In overall Julia programming language is a better alternative that you can use to handle Big data projects. Despite having a small community, it is one of those programming languages that you can easily learn.

Address of the bookmark: https://github.com/google/nucleus

Use the Terminal or an Anaconda Prompt for the following steps.

1. To create an environment:

   conda create --name myenv
   

   NOTE: Replace myenv with the environment name.

2. When conda asks you to proceed, type y:

   proceed ([y]/n)?
   

This creates the myenv environment in /envs/. This environment uses the same version of Python that you are currently using, because you did not specify a version.

To create an environment with a specific version of Python:

conda create -n myenv python=3.4

To create an environment with a specific package:

conda create -n myenv scipy

OR:

conda create -n myenv python
conda install -n myenv scipy

To create an environment with a specific version of a package:

conda create -n myenv scipy=0.15.0

OR:

conda create -n myenv python
conda install -n myenv scipy=0.15.0

To create an environment with a specific version of Python and multiple packages:

conda create -n myenv python=3.4 scipy=0.15.0 astroid babel

TIP: Install all the programs that you want in this environment at the same time. Installing 1 program at a time can lead to dependency conflicts.

To automatically install pip or another program every time a new environment is created, add the default programs to the create_default_packages section of your .condarc configuration file. The default packages are installed every time you create a new environment. If you do not want the default packages installed in a particular environment, use the --no-default-packages flag:

conda create --no-default-packages -n myenv python

TIP: You can add much more to the conda create command. For details, run conda create --help.

➜ redundans git:(master) ✗ conda create --name py27 python=2.7
Solving environment: done

==> WARNING: A newer version of conda exists. <==
current version: 4.5.0
latest version: 4.5.2

Please update conda by running

$ conda update -n base conda

## Package Plan ##

environment location: /home/urbe/anaconda3/envs/py27

added / updated specs:
- python=2.7

The following packages will be downloaded:

package | build
---------------------------|-----------------
wheel-0.31.0 | py27_0 61 KB
python-2.7.15 | h1571d57_0 12.1 MB
certifi-2018.4.16 | py27_0 142 KB
sqlite-3.23.1 | he433501_0 1.5 MB
setuptools-39.1.0 | py27_0 582 KB
openssl-1.0.2o | h20670df_0 3.4 MB
pip-10.0.1 | py27_0 1.7 MB
ca-certificates-2018.03.07 | 0 124 KB
------------------------------------------------------------
Total: 19.6 MB

The following NEW packages will be INSTALLED:

ca-certificates: 2018.03.07-0
certifi: 2018.4.16-py27_0
libedit: 3.1-heed3624_0
libffi: 3.2.1-hd88cf55_4
libgcc-ng: 7.2.0-hdf63c60_3
libstdcxx-ng: 7.2.0-hdf63c60_3
ncurses: 6.0-h9df7e31_2
openssl: 1.0.2o-h20670df_0
pip: 10.0.1-py27_0
python: 2.7.15-h1571d57_0
readline: 7.0-ha6073c6_4
setuptools: 39.1.0-py27_0
sqlite: 3.23.1-he433501_0
tk: 8.6.7-hc745277_3
wheel: 0.31.0-py27_0
zlib: 1.2.11-ha838bed_2

Proceed ([y]/n)? y

Downloading and Extracting Packages
wheel 0.31.0: #################################################################################################################################################################################################### | 100%
python 2.7.15: ################################################################################################################################################################################################### | 100%
certifi 2018.4.16: ############################################################################################################################################################################################### | 100%
sqlite 3.23.1: ################################################################################################################################################################################################### | 100%
setuptools 39.1.0: ############################################################################################################################################################################################### | 100%
openssl 1.0.2o: ################################################################################################################################################################################################## | 100%
pip 10.0.1: ###################################################################################################################################################################################################### | 100%
ca-certificates 2018.03.07: ###################################################################################################################################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use:
# > source activate py27
#
# To deactivate an active environment, use:
# > source deactivate
#

➜ redundans git:(master) ✗ source activate py27

https://github.com/kyclark/tiny_python_projects

Address of the bookmark: https://github.com/kyclark/tiny_python_projects

Address of the bookmark: https://bioconda.github.io/recipes/snakemake/README.html

• data = mock data for the snakefile to use
• Snakefile = name of the snakemake “formula” file
  • Note: The default file that snakemake looks for in the current working directory is the Snakefile. If you would like to override that you can specify it following the -s
    • snakemake -s snakefile.py
• envs = directory for storing the conda environments that the workflow will use.
• scripts = directory for storing python scripts called by the snakemake formula.
• config.json = json format file with extra parameters for our snakemake file to use.
• cluster.json = json format file with specification for running on the HPC
• samples.txt = file we will use later relating to the config.json file.

Run the snakemake file as a dry run (the example workflow shown above).

• This will build a DAG of the jobs to be run without actually executing them.
• snakemake --dry-run

User can execute rules of interest.

• snakemake --dry-run all VS. snakemake --dry-run call VS. snakemake --dry-run bwa

Run the snakemake file in order to produce an image of the DAG of jobs to be run.

• snakemake --dag | dot -Tsvg > dag.svg OR snakemake --dag | dot -Tsvg > dag.svg

Run the snakemake (this time not as a dry run)

1. snakemake --use-conda