Hi!
I'm pleased to announce the availability of wxGlade revision 1.0.1
Please download from https://sourceforge.net/projects/wxglade/files/wxglade/1.0.1/
wxGlade is a GUI builder for wxWidgets and wxPython.
The documentation includes a tutorial for people who have not used wxPython
before.
Included are also examples for integration with matplotlib.
A snapshot of the documentation is available at http://wxglade.sourceforge.net/docs/index.html
For support, there's a mailing list at https://sourceforge.net/p/wxglade/mailman/wxglade-general/
git repository and bug tracker are at https://github.com/wxGlade/wxGlade
(These pages are also linked from the help menu.)
Changes in revision 1.0.x:
==========================
Besides many improvements in usability, code generation and widget support,
this is also a major internal refactoring of the main data structure and how
widgets in the Design window are created / updated / destroyed.
*General:*
- sizers only required where wx requires them; not required e.g. for
Frame->Panel (used to be Frame->Sizer->Panel)
- better handling of display updates when properties are edited
- accessibility and usability improvements
- Dialog example
- documentation update
*Widgets:*
- all: separate class related properties into Class / Base Classes /
Instance Class
- Dialog: add StdDialogButtonSizer and standard buttons (stock items);
support SetAffirmativeId, SetEscapeId
- Button: support for image direction
- MenuBar: support lambda event handlers
- GridBagSizer: indicate overlapped slots in the Tree view
*Generated Code:*
- no separation into __set_properties/__do_layout any more
- support for instantiation classes
*Internal:*
- internal structures refactored
- add shell window and Tree Printer
wxGlade is released under the MIT license.
Happy New Year,
Dietmar Schwertberger
dietmar(a)schwertberger.de
<P><A HREF="https://sourceforge.net/projects/wxglade/files/wxglade/1.0.1/">wxGlade 1.0.1</A> - GUI builder for wxPython (31-Dec-20)
Hi All,
On behalf of the NumPy team I am pleased to announce the release of NumPy
1.20.0rc2. This NumPy release is the largest to date, containing some 684
merged pull requests contributed by 184 people. See the list of highlights
below. The Python versions supported for this release are 3.7-3.9, support
for Python 3.6 has been dropped. Wheels can be downloaded from PyPI
<https://pypi.org/project/numpy/1.20.0/>; source archives, release notes,
and wheel hashes are available on Github
<https://github.com/numpy/numpy/releases/tag/v1.20.0>. Linux users will
need pip >= 0.19.3 in order to install manylinux2010 and manylinux2014
wheels.
*Highlights*
- Annotations for NumPy functions. This work is ongoing and improvements
can be expected pending feedback from users.
- Wider use of SIMD to increase execution speed of ufuncs. Much work has
been done in introducing universal functions that will ease use of modern
features across different hardware platforms. This work is ongoing.
- Preliminary work in changing the dtype and casting implementations in
order to provide an easier path to extending dtypes. This work is ongoing
but enough has been done to allow experimentation and feedback.
- Extensive documentation improvements comprising some 185 PR merges.
This work is ongoing and part of the larger project to improve NumPy's
online presence and usefulness to new users.
- Further cleanups related to removing Python 2.7. This improves code
readability and removes technical debt.
- Preliminary support for the upcoming Cython 3.0.
*Contributors*
A total of 184 people contributed to this release. People with a "+" by
their
names contributed a patch for the first time.
* Aaron Meurer +
* Abhilash Barigidad +
* Abhinav Reddy +
* Abhishek Singh +
* Al-Baraa El-Hag +
* Albert Villanova del Moral +
* Alex Leontiev +
* Alex Rockhill +
* Alex Rogozhnikov
* Alexander Belopolsky
* Alexander Kuhn-Regnier +
* Allen Downey +
* Andras Deak
* Andrea Olivo +
* Andrew Eckart +
* Anirudh Subramanian
* Anthony Byuraev +
* Antonio Larrosa +
* Ashutosh Singh +
* Bangcheng Yang +
* Bas van Beek +
* Ben Derrett +
* Ben Elliston +
* Ben Nathanson +
* Bernie Gray +
* Bharat Medasani +
* Bharat Raghunathan
* Bijesh Mohan +
* Bradley Dice +
* Brandon David +
* Brandt Bucher
* Brian Soto +
* Brigitta Sipocz
* Cameron Blocker +
* Carl Leake +
* Charles Harris
* Chris Brown +
* Chris Vavaliaris +
* Christoph Gohlke
* Chunlin Fang
* CloseChoice +
* Daniel G. A. Smith +
* Daniel Hrisca
* Daniel Vanzo +
* David Pitchford +
* Davide Dal Bosco +
* Derek Homeier
* Dima Kogan +
* Dmitry Kutlenkov +
* Douglas Fenstermacher +
* Dustin Spicuzza +
* E. Madison Bray +
* Elia Franzella +
* Enrique Matías Sánchez +
* Erfan Nariman | Veneficus +
* Eric Larson
* Eric Moore
* Eric Wieser
* Erik M. Bray
* EthanCJ-git +
* Etienne Guesnet +
* FX Coudert +
* Felix Divo
* Frankie Robertson +
* Ganesh Kathiresan
* Gengxin Xie
* Gerry Manoim +
* Guilherme Leobas
* Hassan Kibirige
* Hugo Mendes +
* Hugo van Kemenade
* Ian Thomas +
* InessaPawson +
* Isabela Presedo-Floyd +
* Isuru Fernando
* Jakob Jakobson +
* Jakub Wilk
* James Myatt +
* Jesse Li +
* John Hagen +
* John Zwinck
* Joseph Fox-Rabinovitz
* Josh Wilson
* Jovial Joe Jayarson +
* Julia Signell +
* Jun Kudo +
* Karan Dhir +
* Kaspar Thommen +
* Kerem Hallaç
* Kevin Moore +
* Kevin Sheppard
* Klaus Zimmermann +
* LSchroefl +
* Laurie +
* Laurie Stephey +
* Levi Stovall +
* Lisa Schwetlick +
* Lukas Geiger +
* Madhulika Jain Chambers +
* Matthias Bussonnier
* Matti Picus
* Melissa Weber Mendonça
* Michael Hirsch
* Nick R. Papior
* Nikola Forró
* Noman Arshad +
* Paul YS Lee +
* Pauli Virtanen
* Paweł Redzyński +
* Peter Andreas Entschev
* Peter Bell
* Philippe Ombredanne +
* Phoenix Meadowlark +
* Piotr Gaiński
* Raghav Khanna +
* Raghuveer Devulapalli
* Rajas Rade +
* Rakesh Vasudevan
* Ralf Gommers
* Raphael Kruse +
* Rashmi K A +
* Robert Kern
* Rohit Sanjay +
* Roman Yurchak
* Ross Barnowski
* Royston E Tauro +
* Ryan C Cooper +
* Ryan Soklaski
* Safouane Chergui +
* Sahil Siddiq +
* Sarthak Vineet Kumar +
* Sayed Adel
* Sebastian Berg
* Sergei Vorfolomeev +
* Seth Troisi
* Sidhant Bansal +
* Simon Gasse
* Simon Graham +
* Stefan Appelhoff +
* Stefan Behnel +
* Stefan van der Walt
* Steve Dower
* Steve Joachim +
* Steven Pitman +
* Stuart Archibald
* Sturla Molden
* Susan Chang +
* Takanori H +
* Tapajyoti Bose +
* Thomas A Caswell
* Tina Oberoi
* Tirth Patel
* Tobias Pitters +
* Tomoki, Karatsu +
* Tyler Reddy
* Veniamin Petrenko +
* Wansoo Kim +
* Warren Weckesser
* Wei Yang +
* Wojciech Rzadkowski
* Yang Hau +
* Yogesh Raisinghani +
* Yu Feng
* Yuya Unno +
* Zac Hatfield-Dodds
* Zuhair Ali-Khan +
* @abhilash42 +
* @danbeibei +
* @dojafrat
* @dpitch40 +
* @forfun +
* @iamsoto +
* @jbrockmendel +
* @leeyspaul +
* @mitch +
* @prateek arora +
* @serge-sans-paille +
* @skywalker +
* @stphnlyd +
* @xoviat
* @谭九鼎 +
* @JMFT +
* @Jack +
* @Neal C +
Cheers,
Charles Harris
We're happy to announce the pre-launch website for this year's
EuroPython 2021:
* EuroPython 2021 *
https://ep2021.europython.eu/
The site comes with an FAQ page, which lists all the information we have
for you at the moment. We're repeating the most important part here:
EuroPython 2021 will be held online from July 26 - August 1, 2021,
using the following structure:
- two workshop/training days (July 26 - 27)
- three conference days (July 28 - 30)
- two sprint days (July 31 - August 1)
The next steps are preparing the main conference website, adding
content, organizing the call for papers (CFP), setting up the ticket
system, the financial aid program, getting everything tested and
deployed.
Want to join the fun ?
----------------------
We'll have busy weeks ahead of us. If you want to help, please consider
contacting us with details on where you would like to contribute. Please
write to volunteers(a)europython.eu.
Distributed conferencing
------------------------
We are also looking into setting up, what we call EuroPython Nodes,
where attendees can join small groups around the world to attend
EuroPython 2021 together. Please see our FAQ entry for details. The idea
is still in flux and we'd like to get some feedback from user groups or
companies interested in participating:
https://ep2021.europython.eu/faq/#nodes
PS: We have also moved our blog off of Tumblr and onto our own
infrastructure. Hope you like the new design.
Help spread the word
--------------------
Please help us spread this message by sharing it on your social
networks as widely as possible. Thank you !
Link to the blog post:
https://blog.europython.eu/europython-2021-getting-ready/
Tweet:
https://twitter.com/cargodusoir/status/1354756310328356865
Enjoy,
--
EuroPython 2021 Team
https://www.europython-society.org/
pytest 6.2.2 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
https://docs.pytest.org/en/stable/changelog.html.
Thanks to all of the contributors to this release:
* Adam Johnson
* Bruno Oliveira
* Chris NeJame
* Ran Benita
Happy testing,
The pytest Development Team
# Announcement: pip 21.0 has now been released
On behalf of the PyPA, I am pleased to announce that we have just released pip 21.0, a new version of pip. You can install it by running `python -m pip install --upgrade pip`.
This is the first scheduled release of pip in 2021, following our regular [quarterly release schedule](https://pip.pypa.io/en/stable/development/release-process/#release-cadence).
## Highlights
- Removal of Python 2.7 and 3.5 support.
- Dropped support for legacy cache entries from pip < 20.0.
You can find more details (including deprecations and removals) in the [changelog](https://pip.pypa.io/en/stable/news/).
## Regarding Python 2 support
We've also released pip 20.3.4, which contains certain bugfixes for Python 2 users. It is our final Python 2 compatible release, and there are no future Python 2 compatible releases planned.
Python 2 users will need to continue using a version of pip older than 21.0. Upgrading via pip will select a suitable version, because this release is marked as not supporting Python 2. However, if you are upgrading from a version of pip older than 9.0.0, that does not support the `Requires-Python` metadata, you may need to explicitly request `pip < 21.0`.
A Python 2.7 compatible version of `get-pip.py` is available at <https://bootstrap.pypa.io/2.7/>.
## Thanks
As with all pip releases, a significant amount of the work was contributed by pip’s user community. Huge thanks to all who have contributed, whether through code, documentation, issue reports and/or discussion. Your help keeps pip improving, and is hugely appreciated.
Hello,
I am pleased to announce the release of django-saml2-auth, which includes
71 commits, 92 lines of commit messages and 3 separate reviews and
reviewers.
The project is originally developed by Li Fang <https://github.com/fangli>,
but is forked and currently maintained by Mostafa Moradian <
https://github.com/mostafa> and sponsored by Load Impact AB (https://k6.io).
This release is backward incompatible with older versions: 1.x.x and 2.x.x,
and includes heavy refactoring, improving code readability (docstrings,
annotations, ...), tests, new shiny features and the like. You can read
more about the details in the PR description:
https://github.com/loadimpact/django-saml2-auth/pull/14.
The biggest change so far was adding tests and enabling GitHub Actions as
CI, plus the introduction of SP-initiated SSO. The exception and error
handling is also greatly improved.
Mostafa Moradian.
Project homepage: https://github.com/loadimpact/django-saml2-auth
P.S. It is not published to pypi yet, because of naming issues with the
original package.
Announcing the release of Blue version 0.5.1
====
Blue
====
Some folks like `black <https://black.readthedocs.io/en/stable/>`_ but I
prefer `blue <https://blue.readthedocs.io/en/latest/>`_.
What is blue?
=============
``blue`` is a somewhat less uncompromising code formatter than ``black``,
the OG of Python formatters. We love the idea of automatically formatting
Python code, for the same reasons that inspired ``black``, however we take
issue with some of the decisions ``black`` makes. Kudos to ``black`` for
pioneering code formatting for Python, and for its excellent
implementation.
Where the ``blue`` maintainers disagree with the stylistic (and
unconfigurable) choices made by ``black``, we monkeypatch to change these
decisions to our own liking. We intend for these differences to be
minimal; even in cases where we'd prefer something different, there's a lot
we can live with for the sake of consistency.
We'd prefer not to fork or monkeypatch. Instead, our hope is that
eventually we'll be able to work with the ``black`` maintainers to add just
a little bit of configuration and merge back into the ``black`` project.
We'd be ecstatic if ``blue`` eventually were retired. Until then, we'll
maintain our small set of hacks on top of ``black`` and carefully consider
what other deviations are needed to assuage our sensitive, but experienced,
eye.
How do I use blue?
==================
Exactly the same as you would use ``black``. Invoke and configure ``blue``
as you would ``black`` -- just replace the ``black`` command with ``blue``,
sit back, and enjoy even betterly formatted Python code! You can refer to
`black's <https://black.readthedocs.io/en/stable/>`_ documentation for
anything not listed here.
So what's different?
====================
Here is a brief list of differences between ``blue`` and ``black``:
* ``blue`` defaults to single-quoted strings. This is probably the most
painful ``black`` choice to our eyes, and the thing that inspired
``blue``. We strongly prefer using single quoted strings over double
quoted strings for everything *except* docstrings. Don't ask us why we
prefer double quoted strings for docstrings; it just looks better to us!
For all other strings, ``blue`` defaults to single quoted strings.
* ``blue`` defaults to line lengths of 79 characters. Nearly every project
creates a pyproject.toml just to change this one setting so making it
consistent with PEP 8 seems relatively harmless.
We are `accumulating <https://github.com/grantjenks/blue/issues/2>`_ a list
of other deviations we are considering. As we decide to implement any
particular suggestion, we'll turn those into individual issues and tackle
them one-by-one. If you have suggestions for other deviations from
``black``'s choices, please open a separate ticket on our tracker, and
we'll see how it goes!
Why "blue"?
===========
Several reasons! If your formatter is going to beat up your code, it'll
leave it black and blue, or maybe in this case, black *or* blue. Blue is
better!
We also thought about "tan" because, yum! But that project name was
already taken. Frankly, "blue" was also taken, but largely unused. Our
thanks to Nick Ficano for donating the project namespace to us!
Blue is also the color of `LinkedIn <https://www.linkedin.com/>`_, the
authors' gracious employer, and we intend to socialize its use within our
company code base.
Contributors
============
``blue`` thanks this list of contributors for all its wonderful goodness.
* The `wonderful folks <https://github.com/psf/black#authors>`_ from the
``black`` project.
* Grant Jenks
* Barry Warsaw
``blue`` is licensed under the terms of the Apache License Version 2.0.
``black`` is `licensed <https://github.com/psf/black#license>`_ under the
terms of the MIT license.
Project details
===============
* Project home: https://github.com/grantjenks/blue
* Report bugs and suggestions at: https://github.com/grantjenks/blue/issues
* Code hosting: https://github.com/grantjenks/blue.git
* Documentation: https://blue.readthedocs.io/en/latest
=====================================
Announcing icontract-hypothesis 1.0.0
=====================================
An initial release of icontract-hypothesis is now available:
https://github.com/mristin/icontract-hypothesis/releases/tag/v1.0.0
together with IDE integrations:
* https://github.com/mristin/icontract-hypothesis-vim, and
* https://github.com/mristin/icontract-hypothesis-pycharm
About icontract-hypothesis
==========================
Icontract-hypothesis combines design-by-contract with automatic testing.
It is an integration between icontract library for design-by-contract and
Hypothesis library for property-based testing.
The result is a powerful combination that allows you to automatically test
your code. Instead of writing manually the Hypothesis search strategies for
a function, icontract-hypothesis infers them based on the function's
precondition. This makes automatic testing as effortless as it goes.
Since the contracts live close to the code, evolving the code also automatically
evolves the tests.
Maintainer
==========
The icontract-hypothesis is currently maintained by:
* Marko Ristin <marko(a)ristin.ch>
Many thanks to all the people who participated in the discussions and gave
valuable suggestions!
Copyright
=========
Copyright (c) 2020 Marko Ristin <marko(a)ristin.ch>
Icontract-hypothesis is released under the MIT license.
See the file LICENSE for more details.
=======================
Announcing PyYAML-5.4.1
=======================
A new release of PyYAML is now available:
https://github.com/yaml/pyyaml/releases/tag/5.4.1
This release contains a fix for AttributeError during module import in some
mixed version installations.
PyYAML 5.4.1 will be the last release to support Python 2.7 (except for
possible
critical bug fix releases).
Changes
=======
* https://github.com/yaml/pyyaml/pull/480 -- Fix stub compat with older
pyyaml versions that may unwittingly load it
Resources
=========
PyYAML IRC Channel: #pyyaml on irc.freenode.net
PyYAML homepage: https://github.com/yaml/pyyaml
PyYAML documentation: http://pyyaml.org/wiki/PyYAMLDocumentation
Source and binary installers: https://pypi.org/project/PyYAML/
GitHub repository: https://github.com/yaml/pyyaml/
Bug tracking: https://github.com/yaml/pyyaml/issues
YAML homepage: http://yaml.org/
YAML-core mailing list:
http://lists.sourceforge.net/lists/listinfo/yaml-core
About PyYAML
============
YAML is a data serialization format designed for human readability and
interaction with scripting languages. PyYAML is a YAML parser and emitter
for
Python.
PyYAML features a complete YAML 1.1 parser, Unicode support, pickle support,
capable extension API, and sensible error messages. PyYAML supports standard
YAML tags and provides Python-specific tags that allow to represent an
arbitrary Python object.
PyYAML is applicable for a broad range of tasks from complex configuration
files to object serialization and persistence.
Example
=======
```
>>> import yaml
>>> yaml.full_load("""
... name: PyYAML
... description: YAML parser and emitter for Python
... homepage: https://github.com/yaml/pyyaml
... keywords: [YAML, serialization, configuration, persistence, pickle]
... """)
{'keywords': ['YAML', 'serialization', 'configuration', 'persistence',
'pickle'], 'homepage': 'https://github.com/yaml/pyyaml', 'description':
'YAML parser and emitter for Python', 'name': 'PyYAML'}
>>> print(yaml.dump(_))
name: PyYAML
homepage: https://github.com/yaml/pyyaml
description: YAML parser and emitter for Python
keywords: [YAML, serialization, configuration, persistence, pickle]
```
Maintainers
===========
The following people are currently responsible for maintaining PyYAML:
* Ingy döt Net
* Matt Davis
and many thanks to all who have contributed!
See: https://github.com/yaml/pyyaml/pulls
Copyright
=========
Copyright (c) 2017-2021 Ingy döt Net <ingy(a)ingy.net>
Copyright (c) 2006-2016 Kirill Simonov <xi(a)resolvent.net>
The PyYAML module was written by Kirill Simonov <xi(a)resolvent.net>.
It is currently maintained by the YAML and Python communities.
PyYAML is released under the MIT license.
See the file LICENSE for more details.
=====================
Announcing PyYAML-5.4
=====================
A new release of PyYAML is now available:
https://github.com/yaml/pyyaml/releases/tag/5.4
This release contains a security fix for CVE-2020-14343. It removes the
python/module, python/object, and python/object/new tags from the
FullLoader. YAML that uses these tags must be loaded by UnsafeLoader, or a
custom loader that has explicitly enabled them.
This release also adds Python wheels for manylinux1 (x86_64) and MacOS
(x86_64) with the libyaml extension included (built on libyaml 0.2.5).
PyYAML 5.4 will be the last release to support Python 2.7 (except for
possible critical bug fix releases).
Changes
=======
* https://github.com/yaml/pyyaml/pull/407 -- build modernization, remove
distutils, fix metadata, build wheels, CI to GHA
* https://github.com/yaml/pyyaml/pull/472 -- fix for CVE-2020-14343, moves
arbitrary python tags to UnsafeLoader
* https://github.com/yaml/pyyaml/pull/441 -- fix memory leak in implicit
resolver setup
* https://github.com/yaml/pyyaml/pull/392 -- fix py2 copy support for
timezone objects
* https://github.com/yaml/pyyaml/pull/378 -- fix compatibility with Jython
Resources
=========
PyYAML IRC Channel: #pyyaml on irc.freenode.net
PyYAML homepage: https://github.com/yaml/pyyaml
PyYAML documentation: http://pyyaml.org/wiki/PyYAMLDocumentation
Source and binary installers: https://pypi.org/project/PyYAML/
GitHub repository: https://github.com/yaml/pyyaml/
Bug tracking: https://github.com/yaml/pyyaml/issues
YAML homepage: http://yaml.org/
YAML-core mailing list:
http://lists.sourceforge.net/lists/listinfo/yaml-core
About PyYAML
============
YAML is a data serialization format designed for human readability and
interaction with scripting languages. PyYAML is a YAML parser and emitter
for Python.
PyYAML features a complete YAML 1.1 parser, Unicode support, pickle
support, capable extension API, and sensible error messages. PyYAML
supports standard YAML tags and provides Python-specific tags that allow to
represent an arbitrary Python object.
PyYAML is applicable for a broad range of tasks from complex configuration
files to object serialization and persistence.
Example
=======
```
>>> import yaml
>>> yaml.full_load("""
... name: PyYAML
... description: YAML parser and emitter for Python
... homepage: https://github.com/yaml/pyyaml
... keywords: [YAML, serialization, configuration, persistence, pickle]
... """)
{'keywords': ['YAML', 'serialization', 'configuration', 'persistence',
'pickle'], 'homepage': 'https://github.com/yaml/pyyaml', 'description':
'YAML parser and emitter for Python', 'name': 'PyYAML'}
>>> print(yaml.dump(_))
name: PyYAML
homepage: https://github.com/yaml/pyyaml
description: YAML parser and emitter for Python
keywords: [YAML, serialization, configuration, persistence, pickle]
```
Maintainers
===========
The following people are currently responsible for maintaining PyYAML:
* Ingy döt Net
* Matt Davis
and many thanks to all who have contributed!
See: https://github.com/yaml/pyyaml/pulls
Copyright
=========
Copyright (c) 2017-2021 Ingy döt Net <ingy(a)ingy.net>
Copyright (c) 2006-2016 Kirill Simonov <xi(a)resolvent.net>
The PyYAML module was written by Kirill Simonov <xi(a)resolvent.net>.
It is currently maintained by the YAML and Python communities.
PyYAML is released under the MIT license.
See the file LICENSE for more details.
