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...
pytest 3.1.1 has just been released to PyPI.
This is a bug-fix release, being a drop-in replacement. To upgrade::
pip install --upgrade pytest
The full changelog is available at
Thanks to all who contributed to this release, among them:
* Bruno Oliveira
* Florian Bruhin
* Floris Bruynooghe
* Jason R. Coombs
* Ronny Pfannschmidt
The pytest Development Team
PyCA cryptography 1.8 (and 1.8.1) has been released to PyPI.
cryptography includes both high level recipes and low level interfaces
to common cryptographic algorithms such as symmetric ciphers, message
digests, and key derivation functions. We support Python 2.6-2.7,
Python 3.3+, and PyPy.
* BACKWARDS INCOMPATIBLE: Elliptic Curve signature verification no
longer returns True on success. This brings it in line with the
interface’s documentation, and our intent. The correct way to use
verify() has always been to check whether or not InvalidSignature was
* BACKWARDS INCOMPATIBLE: Dropped support for macOS 10.7 and 10.8.
* BACKWARDS INCOMPATIBLE: The minimum supported PyPy version is now 5.3.
* Python 3.3 support has been deprecated, and will be removed in the
next cryptography release.
* Add support for providing tag during GCM finalization via finalize_with_tag().
* Fixed an issue preventing cryptography from compiling against LibreSSL 2.5.x.
* Added key_size convenience methods for determining the bit size of a
secret scalar for an elliptic curve.
* Accessing an unrecognized extension marked critical on an X.509
object will no longer raise an UnsupportedExtension exception, instead
an UnrecognizedExtension object will be returned. This behavior was
based on a poor reading of the RFC, unknown critical extensions only
need to be rejected on certificate verification.
* The CommonCrypto backend has been removed.
* MultiBackend has been removed.
* Whirlpool and RIPEMD160 have been deprecated.
Thanks to all the contributors for their hard work on this release!
-Paul Kehrer (reaperhulk)
I'm delighted to announce the release of Sphinx 1.6.2, now available on
the Python package index at <http://pypi.python.org/pypi/Sphinx>.
It includes about 23 bug fixes for the 1.6.1 release series.
For the full changelog, go to
Thanks to all collaborators and contributers!
What is it?
Sphinx is a tool that makes it easy to create intelligent and beautiful
documentation for Python projects (or other documents consisting of
multiple reStructuredText source files).
IRC: #sphinx-doc on irc.freenode.net
The 10th European Conference on Python in Science will take place
in Erlangen, Germany from August 28 - September 1, 2017.
More information can be found on the conference website:
The EuroSciPy meeting is a cross-disciplinary gathering focused on the use and
development of the Python language in scientific research. This event strives
to bring together both users and developers of scientific tools, as well as
academic research and state of the art industry.
Presentations of scientific tools and libraries using the Python language,
including but not limited to:
* Vector and array manipulation
* Parallel computing
* Scientific visualization
* Scientific data flow and persistence
* Algorithms implemented or exposed in Python
* Web applications and portals for science and engineering-
* Reports on the use of Python in scientific achievements or
* General-purpose Python tools that can be of special interest
to the scientific community.
"firehose" is a Python package intended for managing the results from
code analysis tools (e.g. compiler warnings, static analysis, linters,
It provides parsers for the output of various tools, including for the
output of gcc, clang-analyzer, cppcheck, and findbugs. These parsers
convert the results into a common data model of Python objects, with
methods for lossless roundtrips through a provided XML format. There is
also a JSON equivalent.
It is available on pypi here:
and via git from:
The mailing list is:
Firehose is Free Software, licensed under the LGPLv2.1 or (at your
option) any later version.
It requires Python 2.7 or 3.2 onwards, and has been successfully tested
Changes since 0.5:
* Added Sphinx-based documentation (David Malcolm)
Prebuilt docs can be seen at
* Added parser for flawfinder (David Carlos de Araujo Silva)
* Added parser for splint (David Malcolm)
* Parser for clang analyzer now captures version information,
testid, and other per-issue data (David Malcolm)
On behalf of the Nikola team, I am pleased to announce the immediate
availability of Nikola v7.8.6. It fixes some bugs and adds new
What is Nikola?
Nikola is a static site and blog generator, written in Python.
It can use Mako and Jinja2 templates, and input in many popular markup
formats, such as reStructuredText and Markdown — and can even turn
Jupyter (IPython) Notebooks into blog posts! It also supports image
galleries, and is multilingual. Nikola is flexible, and page builds
are extremely fast, courtesy of doit (which is rebuilding only what
has been changed).
Find out more at the website: https://getnikola.com/
Install using `pip install Nikola` or download tarballs on GitHub and PyPI:
Or if you prefer, Snapcraft packages are now built automatically, and
Nikola v7.8.6 will be available in the stable channel.
* Guess file format from file name on new_post (Issue #2798)
* Use BaguetteBox as lightbox in base theme (Issue #2777)
* New ``deduplicate_ids`` filter, for preventing duplication of HTML
``id`` attributes (Issue #2570)
* Ported gallery image layout to base theme (Issue #2775)
* Better error handling when posts can't be parsed (Issue #2771)
* Use ``.theme`` files to store theme metadata (Issue #2758)
* New ``add_header_permalinks`` filter, for Sphinx-style header links
* Added alternate links for gallery translations (Issue #993)
* Use ``locale.getdefaultlocale()`` for better locale guessing
* Save dependencies for template hooks properly (using ``.__doc__`` or
``.template_registry_identifier`` for callables)
* Enable larger panorama thumbnails (Issue #2780)
* Disable ``archive_rss`` link handler, which was useless because no
such RSS was ever generated (Issue #2783)
* Ignore files ending wih "bak" (Issue #2740)
* Use page.tmpl by default, which is inherited from story.tmpl (Issue
* Limit Jupyter support to notebook >= 4.0.0 (it already was in
requirements-extras.txt; Issue #2733)
After the final review round, we are now happy to announce the
complete list of more than 200 accepted sessions.
* EuroPython 2017 Session List *
Here’s what we have on offer:
- 5 keynotes
- 157 talks
- 20 trainings
- 10 posters
- 4 interactive sessions
- 5 help desks
- 2 EuroPython sessions
for a total of 203 sessions, arranged in 5 tracks from Monday, July
10, thru Friday, July 14, in addition to the Beginners’ Day and Django
Girls workshops on Sunday, July 9, and the Sprints on the weekend July
Please see the session list for details and abstracts. In case you
wonder what poster, interactive and help desk sessions are, please
check the call for proposals:
Additional help desk slots available
We have 5 additional help desk slots available. If you are interested
in arranging one, please see our Call for Proposals for details and
contact program(a)europython.eu to submit your proposal. Organizers of
help desks are eligible for a 25% ticket discount.
Schedule to be announced next week
Our program work group is now working hard on scheduling all these
sessions. We expect to announce the final schedule by the end of next
We will use the same conference schedule layout as in previous years:
* Sunday, July 9: Beginners’ Day and Django Girls workshops;
registration desk opens
* Monday - Friday, July 10-14: Conference talks, trainings, keynotes,
help desks, interactive sessions, etc.
* Saturday - Sunday, July 15-16: Sprints
A typical conference day will open the venue at 08:30, have the first
session around 09:00 and end at 18:30. Lunch breaks are scheduled for
around 13:15. Please note that we don’t serve breakfast.
Aside: If you haven’t done yet, please get your EuroPython 2017 ticket
soon. We will switch to on-desk rates in June, which will cost around
30% more than the regular rates.
EuroPython 2017 Team
PS: Please forward or retweet to help us reach all interested parties:
PyCA cryptography 1.8.2 has been released to PyPI. This is a small bug fix
release to correct an issue with compilation on OpenSSL 1.1.0f.
* Fixed a compilation bug affecting OpenSSL 1.1.0f.
* Updated Windows and macOS wheels to be compiled against OpenSSL 1.1.0f.
-Paul Kehrer (reaperhulk)
On behalf of the entire team and all our wonderful contributors, I'm happy to
announce the release of GNU Mailman 3.1 final. My deep thanks go to all the
Mailman project sprinters at Pycon 2017 for getting us over the line!
Two years after the original release of Mailman 3.0, this version contains a
huge number of improvements across the entire stack. Many bugs have been
fixed and new features added in the Core, Postorius (web u/i), and HyperKitty
(archiver). Upgrading from Mailman 2.1 should be better too. We are seeing
more production sites adopt Mailman 3, and we've been getting great feedback
as these have rolled out.
Important: mailman-bundler, our previous recommended way of deploying Mailman
3, has been deprecated. Abhilash Raj is putting the finishing touches on
Docker images to deploy everything, and he'll have a further announcement in a
week or two.
Feedback is welcome:
What is GNU Mailman?
GNU Mailman is free software for managing electronic mail discussion and
e-newsletter lists. Mailman is integrated with the web, making it easy for
users to manage their accounts and for list owners to administer their lists.
Mailman supports built-in archiving, automatic bounce processing, content
filtering, digest delivery, and more. Mailman 3 is released under the terms
of the GNU General Public License, version 3.
The best places to start for all things related to this release:
(Note: due to timezone skew, some of the tarballs may not be available on PyPI
Happy Mailman Day,
-Your friendly neighborhood cabal
An overview of what's new in Mailman 3.1
Feature parity with Mailman 2.1
* You should be able to do just about everything that you could do in Mailman
2.1 *except* for topics and sibling/umbrella lists.
* Added support for Python 3.5 and 3.6
* MySQL is now an officially supported database
* Many improvements with importing Mailman 2.1 lists
* DMARC mitigations have been added, based on, but different than the same
feature in Mailman 2.1
* The REST API requires HTTP/1.1
* A new REST API version (3.1) has been added which changes how UUIDs are
* Many new REST resources and methods have been added
* Individual mailing lists can augment the system's header matching rules
* `mailman create` now creates missing domains by default
* `mailman digests` now has `--verbose` and `--dry-run` options
* `mailman shell` now supports readline history
* `mailman members` can filter members based on their subscription roles
* A new template system has been added for all messages originating from
* The Message-ID-Hash header replaces X-Message-ID-Hash
* New placeholders have been added for headers and footers
* Unsubscriptions can now be confirmed and/or moderated
* General U/I and U/X improvements
* Many more features from the Core's have been plumbed through
* We've adopted Django social auth logins and dropped Persona (since it's no
longer supported upstream). You can now log in via Facebook, Google,
GitHub, and GitLab.
* Core/REST: Held message resources now have an `original_subject` key that is
not RFC 2047 decoded. `subject` is now RFC 2047 decoded.
* Core/REST: If you've run pre-release versions from git head, and stored
welcome and goodbye templates via REST, the template key names have changed