This course will help you to expertise the usage of Python in Data Science world.
Carter your Python Knowledge so that it can be utilized to get the Insights of Data using Methodologies and Techniques of Data Science...
Understand the concepts of Data science and Python
You will be able to use Python in Discovering Data.
You will have an idea of Statistical and Analytical methods to deal with huge data sets.
You will gain an expertise on Regular Expressions, looping functions and concepts of Object Oriented Programming.
You will be able to create business algorithms and data models using Python and it's techniques.
Work on Real-life Projects will help you to get a practical experience of real scenarios of IT Industry.
Start learning Python for Data Science from basics to advance levels here...
Python 3 becomes more and more popular and is close to a dangerous point
where it can become popular that Python 2. The PSF decided that it's
time to elaborate a new secret plan to ensure that Python users suffer
again with a new major release breaking all their legacy code.
The PSF is happy to announce that the new Python release will be
Why the version 8? It's just to be greater than Perl 6 and PHP 7, but
it's also a mnemonic for PEP 8. By the way, each minor release will now
multiply the version by 2. With Python 8 released in 2016 and one
release every two years, we will beat Firefox 44 in 2022 (Python 64) and
Windows 2003 in 2032 (Python 2048).
A major release requires a major change to justify a version bump: the
new killer feature is that it's no longer possible to import a module
which does not respect the PEP 8. It ensures that all your code is pure.
$ python8 -c 'import keyword'
Lib/keyword.py:16:1: E122 continuation line missing indentation or outdented
Lib/keyword.py:16:1: E265 block comment should start with '# '
Lib/keyword.py:50:1: E122 continuation line missing indentation or outdented
ImportError: no pep8, no glory
Good news: since *no* module of the current standard library of Python 3
respect the PEP 8, the standard library will be simplified to one
unique module, which is new in Python 8: pep8. The standard library will
move to the Python Cheeseshop (PyPI), to reply to an old and popular
DON'T PANIC! You are still able to import your legacy code into
Python 8, you just have to rename all your modules to add a "_noqa" suffix
to the filename. For example, rename utils.py to utils_noqa.py. A side
effect is that you have to update all imports. For example, replace
"import django" with "import django_noqa". After a study of the PSF,
it's a best option to split again the Python community and make sure
that all users are angry.
The plan is that in 10 years, at least 50% of the 77,000 packages on the
Python cheeseshop will be updated to get the "_noqa" tag. After 2020,
the PSF will start to sponsor trolls to harass users of the legacy
Python 3 to force them to migrate to Python 8.
Python 8 is a work-in-progress (it's still an alpha version), the
standard library was not removed yet. Hopefully, trying to import any
module of the standard library fails.
Don't hesitate to propose more ideas to make Python 8 more incompatible
with Python 3!
Note: The change is already effective in the default branch of Python:
py2cs.py 0.1 is now available on github
This script makes a coffeescript <http://coffeescript.org/> (.coffee) file
in the output directory for each source file listed on the command line
(wildcard file names are supported). This script never creates directories
automatically, nor does it overwrite .coffee files unless the --overwrite
command-line option is in effect.
This script merely converts python syntax to the roughly equivalent
coffeescript syntax. It knows nothing about coffeescript semantics. It is
intended *only* to help start creating coffeescript code from an existing
python code base.
This script already does much of the grunt work of converting python to
coffeescript. The script processes itself without error, but coffeescript
itself complains about some results
Edward K. Ream
March 31, 2016
Edward K. Ream: edreamleo(a)gmail.com Leo: http://leoeditor.com/
0.1 is now available here <https://github.com/edreamleo/make-stub-files>.
This script eliminates much of the drudgery of creating python stub (.pyi)
<https://www.python.org/dev/peps/pep-0484/#stub-files> from python source
files. This script should encourage more people to use mypy. Stub files can
be used by people who use Python 2.x code bases.
This script makes a stub (.pyi) file in the output directory for each
source file listed on the command line (wildcard file names are supported).
This script never creates directories automatically, nor does it overwrite
stub files unless the --overwrite command-line option is in effect.
We actually do have a stub generator
<https://github.com/JukkaL/mypy/blob/master/mypy/stubgen.py> as part of
mypy now (it has a few options) but yours has the advantage of providing a
way to tune the generated signatures...This allows for a nice iterative way
of developing stubs.
The script does no type inference. Instead, the user supplies *patterns* in
a configuration file. The script matches these patterns to:
The names of arguments in functions and methods and
The text of *return expressions*. Return expressions are the actual text
of whatever follows the "return" keyword. The script removes all comments
in return expressions and converts all strings to "str". This preprocessing
greatly simplifies pattern matching.
For example, given the method:
def foo(self, i, s):
return "abc" # a comment
and the patterns:
the script produces the stub:
def foo(i: int, s: str) --> str: ...
Edward K. Ream
March 31, 2016
Edward K. Ream: edreamleo(a)gmail.com Leo: http://leoeditor.com/
Announcing Numexpr 2.5.1
Numexpr is a fast numerical expression evaluator for NumPy. With it,
expressions that operate on arrays (like "3*a+4*b") are accelerated
and use less memory than doing the same calculation in Python.
It wears multi-threaded capabilities, as well as support for Intel's
MKL (Math Kernel Library), which allows an extremely fast evaluation
of transcendental functions (sin, cos, tan, exp, log...) while
squeezing the last drop of performance out of your multi-core
processors. Look here for a some benchmarks of numexpr using MKL:
Its only dependency is NumPy (MKL is optional), so it works well as an
easy-to-deploy, easy-to-use, computational engine for projects that
don't want to adopt other solutions requiring more heavy dependencies.
Fixed a critical bug that caused wrong evaluations of log10() and
conj(). These produced wrong results when numexpr was compiled with
Intel's MKL (which is a popular build since Anaconda ships it by
default) and non-contiguous data. This is considered a *critical* bug
and upgrading is highly recommended. Thanks to Arne de Laat and Tom
Kooij for reporting and providing a test unit.
In case you want to know more in detail what has changed in this
Where I can find Numexpr?
The project is hosted at GitHub in:
You can get the packages from PyPI as well (but not for RC releases):
Share your experience
Let us know of any bugs, suggestions, gripes, kudos, etc. you may
Announcing a project hosted on GitHub called nose2pytest (
https://github.com/schollii/nose2pytest). This project helps migrate a test
suite that was written for Nose to work with pure pytest. It converts
nose.tools.assert_ functions into raw assert statements so you can better
(IMO) leverage pytest assertion introspection. It may even decrease test
suite dependencies by 1; after nose2test has been run on a test suite, it
is no longer needed.
The nose2pytest script has already successfully converted approximately
5000 assertions, so this is v1.0. However, there are many ways to harness
Nose functionality so I'm really curious to see if nose2test can be useful
I'm sure there is lots of room for improvement. Any feedback or
contributions would be much appreciated.
I am pleased to announce the first public beta release of Elevation, a tool
for easy access to global terrain digital elevation models, SRTM 30m DEM
and SRTM 90m DEM:
Development effort is directed to fixing bugs and writing better
documentation before the 1.0 release. Testing and contributions are highly
welcomed and appreciated. Every little help counts, so do not hesitate!
User questions are best directed to
The project is free and open source software distributed under the terms of
the Apache License, Version 2.0. and the development has been sponsored by
my employer B-Open Solutions http://bopen.eu.
Alessandro Amici <a.amici(a)bopen.eu>
CTO at B-Open Solutions - http://www.bopen.eu/
Viale Palmiro Togliatti, 1639 - 00155 Roma - tel: +39 06 8370 8269
PyConZA 2016 will take place 6th & 7th October at The River Club, in
Observatory, Cape Town, South Africa. There will be two days of talks,
and we will hold sprints on the 8th & 9th of October.
We are currently accepting proposals for talks. If you would like to
give a presentation, please register at https://za.pycon.org/ and
submit your proposal, following the instructions at
https://za.pycon.org/talks/submit-talk . We hope to notify accepted
presenters by no later than the 9th of September 2016.
The presentation slots will be 30 minutes long, with an additional 10
minutes for discussion at the end. Shared sessions are also possible.
The presentations will be in English.
PyConZA offers a mentorship program for inexperienced speakers. If you
would like assistance preparing your submission, email
team(a)za.pycon.org with a rough draft of your talk proposal and we'll
find a suitable experienced speaker to act as a mentor.
In addition to talks, we are also looking for proposals for tutorials,
demos, sprints and open spaces.
Tutorials are intended to be more in-depth introductions to a topic
with a limited number of attendees. Tutorial sessions can be up to 90
Demos are cool things for attendees to see and interact with.
Open spaces are open discussion forums where communities with a common
interest gather to present views, ask questions and meet people
interested in the topic.
Sprints are coding efforts and hack days that happen after the conference.
There's no need to register a sprint or open space topic upfront, but
doing so allows us to advertise them during the conference.
On behalf of the PyConZA organising committee