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'm pleased to announce the release of NumPy
1.25.2. NumPy 1.25.2 is a maintenance release that fixes bugs and
regressions discovered after the 1.25.1 release. This is the last planned
release in the 1.25.x series, the next final release will be 1.26.0, which
will use the meson build system and support Python 3.12.
The Python versions supported by this release are 3.9-3.11 Note that 32 bit
wheels are only provided for Windows, all other wheels are 64 bits on
account of Ubuntu, Fedora, and other Linux distributions dropping 32 bit
support. Wheels can be downloaded from PyPI
<https://pypi.org/project/numpy/1.25.2/>; source archives, release notes,
and wheel hashes are available on Github
<https://github.com/numpy/numpy/releases/tag/v1.25.2>.
*Contributors*
A total of 13 people contributed to this release. People with a "+" by
their names contributed a patch for the first time.
- Aaron Meurer
- Andrew Nelson
- Charles Harris
- Kevin Sheppard
- Matti Picus
- Nathan Goldbaum
- Peter Hawkins
- Ralf Gommers
- Randy Eckenrode +
- Sam James +
- Sebastian Berg
- Tyler Reddy
- dependabot[bot]
*Pull requests merged*
A total of 19 pull requests were merged for this release.
- #24148: MAINT: prepare 1.25.x for further development
- #24174: ENH: Improve clang-cl compliance
- #24179: MAINT: Upgrade various build dependencies.
- #24182: BLD: use ``-ftrapping-math`` with Clang on macOS
- #24183: BUG: properly handle negative indexes in ufunc_at fast path
- #24184: BUG: PyObject_IsTrue and PyObject_Not error handling in
setflags
- #24185: BUG: histogram small range robust
- #24186: MAINT: Update meson.build files from main branch
- #24234: MAINT: exclude min, max and round from ``np.__all__``
- #24241: MAINT: Dependabot updates
- #24242: BUG: Fix the signature for np.array_api.take
- #24243: BLD: update OpenBLAS to an intermediate commit
- #24244: BUG: Fix reference count leak in str(scalar).
- #24245: BUG: fix invalid function pointer conversion error
- #24255: BUG: Factor out slow ``getenv`` call used for memory policy
warning
- #24292: CI: correct URL in cirrus.star [skip cirrus]
- #24293: BUG: Fix C types in scalartypes
- #24294: BUG: do not modify the input to ufunc_at
- #24295: BUG: Further fixes to indexing loop and added tests
Cheers,
Charles Harris
Thanks everyone for the great feedback on the 3.1.0 release! Caught some glaring regressions that slipped through my test suite. Just published version 3.1.1: https://github.com/pyparsing/pyparsing/releases/tag/3.1.1
- Fixed regression in Word(min), reported by Ricardo Coccioli, good catch! (Issue #502)
- Fixed bug in bad exception messages raised by Forward expressions. PR submitted by Kyle Sunden, thanks for your patience and collaboration on this (#493).
- Fixed regression in SkipTo, where ignored expressions were not checked when looking for the target expression. Reported by catcombo, Issue #500.
- Fixed type annotation for enable_packrat, PR submitted by Mike Urbach, thanks! (Issue #498)
- Some general internal code cleanup. (Instigated by Michal Čihař, Issue #488)
I'm happy to announce the release of PyEmpaq 0.4.
PyEmpaq is a simple but powerful Python packer to run any project with
any virtualenv dependencies anywhwere.
With PyEmpaq you can convert any Python project into a single `.pyz`
file with all the project's content packed inside.
That single file is everything that needs to be distributed. When the
final user executes it, the original project will be expanded, its
dependencies installed in a virtualenv, and then executed. Note that
no special permissions or privileges are required, as everything
happens in the user environment.
Both the packaging and the execution are fully multiplatorm. This
means that you can pack a project in Linux, Windows, MacOS or
whatever, and it will run ok in Linux, Windows, MacOS or whatever. The
only requirement is Python to be already installed.
What's new in this version?
- Remove the installation if ephemeral behaviour is indicated
([related issue](https://github.com/facundobatista/pyempaq/issues/63))
- Allow to change the location where the files get unpacked ([related
issue](https://github.com/facundobatista/pyempaq/issues/62))
- Dump a file with unpacking related metadata in the project's
directory ([related
issue](https://github.com/facundobatista/pyempaq/issues/61))
- Refactored the project's install directory name to include the
Python version and more specifics ([related
issue](https://github.com/facundobatista/pyempaq/issues/58))
- Alert at pack time if any indicated requirement file is excluded
from the included files.
- Log (and transmit when ending the unpacker itself) the return code
of the executed project ([related
issue](https://github.com/facundobatista/pyempaq/issues/64))
- Migrated to the `platformdirs` library to detect the user's data
directory. ([related
issue](https://github.com/facundobatista/pyempaq/issues/60))
For more details please [check the
documentation](https://pyempaq.readthedocs.io/en/latest/) (which
includes demos and examples). The project [exists in
Github](https://github.com/facundobatista/pyempaq/).
Enjoy,
--
. Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org.ar/
Twitter: @facundobatista
What Changed?
=============
This is an enhancement and bug-fix release, and all users are encouraged to upgrade.
Brief summary:
* Added TRUST_EXPIRED to trust_keys.
* Fix #206: Remove deprecated --always-trust in favour of --trust-model always
* Fix #208: Add status_detail attribute to result objects which is populated when
the status is 'invalid recipient' (encryption/decryption) or 'invalid signer'
(signing). This attribute will be set when the result object's status attribute is
set to 'invalid recipient' and will contain more information about the failure in the
form of reason:ident where reason is a text description of the reason, and
ident identifies the recipient key.
* Add scan_keys_mem() function to scan keys in a string.
* Fix #214: Handle multiple signatures when one of them is invalid or unverified.
* A problems attribute was added which holds problems reported by gpg
during verification. This is a list of dictionaries, one for each reported
problem. Each dictionary will have status and keyid keys indicating
the problem and the corresponding key; other information in the dictionaries
will be error specific.
* Fix #217: Use machine-readable interface to query the gpg version.
* Added the ability to export keys to a file.
This release [2] has been signed with my code signing key:
Vinay Sajip (CODE SIGNING KEY) <vinay_sajip at yahoo.co.uk>
Fingerprint: CA74 9061 914E AC13 8E66 EADB 9147 B477 339A 9B86
Recent changes to PyPI don't show the GPG signature with the download links.
An alternative download source where the signatures are available is at [4].
The source code repository is at [1].
Documentation is available at [5].
As always, your feedback is most welcome (especially bug reports [3],
patches and suggestions for improvement, or any other points via this group).
Enjoy!
Cheers
Vinay Sajip
[1] https://github.com/vsajip/python-gnupg
[2] https://pypi.org/project/python-gnupg/0.5.1
[3] https://github.com/vsajip/python-gnupg/issues
[4] https://github.com/vsajip/python-gnupg/releases/
[5] https://docs.red-dove.com/python-gnupg/
What is Lona?
=============
Lona is a web application framework, designed to write responsive web apps in full Python.
Lona 1.15
=========
The new release drops support for Python 3.7 and contains lots of useful bugfixes.
Changelog
=========
https://lona-web.org/1.x/changelog.html#1.15
Version 0.3.7 of distlib has recently been released on PyPI [1]. For newcomers, distlib is a library of packaging functionality which is intended to be usable as the basis for third-party packaging tools.
The main changes in this release are as follows:
* Handle bare newlines when parsing metadata.
* Use version comparison logic for python_full_version.
* Fix shebang computation for source builds of Python.
* Extract tarfiles more safely by incorporating tarfile filters.
* Check for 'has_cert' attribute before using it.
* Fix #200: Improve conformance to PEP440.
* Fix #203: Handle parsing of export entries to allow script names such as "," or ",foo".
A more detailed change log is available at [2].
Please try it out, and if you find any problems or have any suggestions for improvements, please give some feedback using the issue tracker at [3].
Regards,
Vinay Sajip
[1] https://pypi.org/project/distlib/0.3.7/
[2] https://distlib.readthedocs.io/en/0.3.7/overview.html#change-log-for-distlib
[3] https://github.com/pypa/distlib/issues/new/choose
I'm proud to release version 2.3.0 of the Roundup issue
tracker. This release is a bugfix and feature
release, so make sure to read `docs/upgrading.txt
<https://www.roundup-tracker.org/docs/upgrading.html>`_ to
bring your tracker up to date.
The changes, as usual, include some new features and many
bug fixes.
Note that you should run ``roundup-admin ... migrate`` to
update the database schema version. Do this before you use
the web, command-line or mail interface and before any users
access the tracker.
You can download it with::
pip download roundup
then unpack and test/install the tarball. Also::
pip install roundup
(preferably in a virtual environment) can be used.
Among the notable improvements from the 2.2.0 release are:
* Dockerfile demo mode implemented. This allows quick evaluation as
well as the ability to spin up a configured tracker to customise.
* SQLite backends can use WAL mode to reduce blocking between readers
and writers improving concurrent use.
* Redis can be used for session database with SQLite and dbm
backends. Provides a major performance improvement.
* roundup-mailgw can use OAUTH authentication to SMTP
server. (roundup-mailgw command line options changed as a result.)
* Postgres full text index can now be enabled.
* Modifications to in-reply-to threading when there are multiple
matches resulting in more predictable handling of messages.
* Many updates to documentation to make it scannable, useful and
work on mobile.
* Admin documentation includes a section on setting up Content
Security Policy (CSP) to better secure your Roundup trackers.
* REST now allows rate limiting headers to be accessed by client
JavaScript.
* Default number of rounds for PBKDF2 updated to 2M to account for
improvements in password crackers and CPU power.
* Support PBKDF2 with SHA512 for password storage to improve
resistance to password crackers.
* Deprecate SSHA password hash function.
* roundup-admin reindex can be done in batches to manage load
incurred by reindexing.
* roundup-admin can list available templates and their installed
locations. This is useful when installing via pip or in a docker
container as supporting files are not stored in the usual locations
like /usr/share/roundup.
* Crash fixes in detector handling
The file CHANGES.txt has a detailed list of feature additions and
bug fixes (53) for each release. The most recent changes from
there are at the end of this announcement. Also see the
information in doc/upgrading.txt.
If you find bugs, please report them to issues AT roundup-tracker.org
or create an account at https://issues.roundup-tracker.org and open a
new ticket. If you have patches to fix the issues they can be attached
to the email or uploaded to the tracker.
Upgrading
=========
If you're upgrading from an older version of Roundup you *must* follow
all the "Software Upgrade" guidelines given in the doc/upgrading.txt
documentation.
Note that you should run ``roundup-admin ... migrate`` for
all your trackers to update the database schema version. Do
this before you use the web, command-line or mail interface
and before any users access the tracker.
Roundup requires Python 2 newer than version 2.7.12 or Python 3 newer
than or equal to version 3.6 for correct operation. (Python
3.4 or 3.5 may work, but are not tested.) Note that Python 2 support
is being removed from the CI platforms, so you should deploy new
trackers with Python 3 and plan on upgrading older trackers from Python
2 to Python 3. See the upgrade guide.
To give Roundup a try, just download (directions above), unpack and run::
python demo.py
then open the url printed by the demo app.
Release info and download page:
https://pypi.org/project/roundup
Source and documentation is available at the website:
https://www.roundup-tracker.org/
Mailing lists - the place to ask questions:
https://sourceforge.net/p/roundup/mailman/
About Roundup
=============
Roundup is a simple-to-use and install issue-tracking system with
command-line, web and e-mail interfaces. It is based on the winning design
from Ka-Ping Yee in the Software Carpentry "Track" design competition.
Note: Ping is not responsible for this project. The contact for this
project is rouilj at users.sourceforge.net. Use this address for
security or other sensitive issues. Development discussions occur on
the roundup-devel at lists.sourceforge.net mailing list. Tickets can
be opened at https://issues.roundup-tracker.org.
Roundup manages a number of issues (with flexible properties such as
"description", "priority", and so on) and provides the ability to:
(a) submit new issues,
(b) find and edit existing issues, and
(c) discuss issues with other participants.
The system facilitates communication among the participants by managing
discussions and notifying interested parties when issues are edited. One of
the major design goals for Roundup that it be simple to get going. Roundup
is therefore usable "out of the box" with any Python 2.7.2+ (or 3.6+)
installation. It doesn't even need to be "installed" to be operational,
though an install script is provided.
It comes with five basic issue tracker templates
* a classic bug/feature tracker
* a more extensive devel tracker for bug/features etc.
* a responsive version of the devel tracker
* a jinja2 version of the devel template (work in progress)
* a minimal skeleton
and supports four database back-ends (anydbm, sqlite, mysql and postgresql).
Recent Changes
==============
See changelog at:
https://sourceforge.net/p/roundup/code/ci/default/tree/CHANGES.txt
Not much time left! I’ve released 3.12.0 beta 4. We’re now in the run-up to
rc1, so keep that in mind when you backport to the 3.12 branch.
https://www.python.org/downloads/release/python-3120b4/
*This is a beta preview of Python 3.12*
Python 3.12 is still in development. This release, 3.12.0b4, is the final
of four beta release previews of 3.12.
Beta release previews are intended to give the wider community the
opportunity to test new features and bug fixes and to prepare their
projects to support the new feature release.
We *strongly encourage* maintainers of third-party Python projects to *test
with 3.12* during the beta phase and report issues found to the Python bug
tracker <https://github.com/python/cpython/issues> as soon as possible.
While the release is planned to be feature complete entering the beta
phase, it is possible that features may be modified or, in rare cases,
deleted up until the start of the release candidate phase (Monday,
2023-07-31). Our goal is to have no ABI changes after this release, and as
few code changes as possible after 3.12.0rc1, the first release candidate.
To achieve that, it will be *extremely important* to get as much exposure
for 3.12 as possible during the beta phase.
Please keep in mind that this is a preview release and its use is *not
*recommended
for production environments.
*Major new features of the 3.12 series, compared to 3.11*
Some of the new major new features and changes in Python 3.12 are:
- New type annotation syntax for generic classes (PEP 695
<https://peps.python.org/pep-0695/>).
- More flexible f-string parsing, allowing many things previously
disallowed (PEP 701 <https://peps.python.org/pep-0701/>).
- Support for the buffer protocol in Python code (PEP 688
<https://peps.python.org/pep-0688/>).
- Even more improved error messages. More exceptions potentially caused
by typos now make suggestions to the user.
- Many large and small performance improvements (like PEP 709
<https://peps.python.org/pep-0709/>).
- Support for the Linux perf profiler to report Python function names in
traces.
- The deprecated wstr and wstr_length members of the C implementation of
unicode objects were removed, per PEP 623
<https://peps.python.org/pep-0623/>.
- In the unittest module, a number of long deprecated methods and
classes were removed. (They had been deprecated since Python 3.1 or 3.2).
- The deprecated smtpd and distutils modules have been removed (see PEP
594 <https://peps.python.org/pep-0594/> and PEP 632
<https://peps.python.org/pep-0632/>. The setuptools package continues to
provide the distutils module.
- A number of other old, broken and deprecated functions, classes and
methods have been removed.
- Invalid backslash escape sequences in strings now warn with SyntaxWarning
instead of DeprecationWarning, making them more visible. (They will
become syntax errors in the future.)
- The internal representation of integers has changed in preparation for
performance enhancements. (This should not affect most users as it is an
internal detail, but it may cause problems for Cython-generated code.)
- (Hey, fellow core developer, if a feature you find important is
missing from this list, let Thomas know <thomas(a)python.org>.)
For more details on the changes to Python 3.12, see What’s new in Python
3.12 <https://docs.python.org/3.12/whatsnew/3.12.html>. The next
pre-release of Python 3.12 will be 3.12.0rc1, the *first release candidate*,
currently scheduled for 2023-07-31.
*More resources*
Online Documentation <https://docs.python.org/3.12/>.
PEP 693 <https://www.python.org/dev/peps/pep-0693/>, the Python 3.12
Release Schedule.
Report bugs via GitHub Issues <https://github.com/python/cpython/issues>.
Help fund Python and its community <https://www.python.org/psf/donations/>.
*We hope you enjoy the new releases!*
Thanks to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python
Software Foundation <https://www.python.org/psf-landing/>.
Regards from the alternating thunderstorms and heat waves in Amsterdam,
Thomas Wouters.
Your release team,
Ned Deily
Steve Dower
Łukasz Langa
--
Thomas Wouters <thomas(a)python.org>
Hi all,
I'm delighted to announce the latest release of skforecast!
In this release (0.9.0), we have made significant improvements to enhance
performance and deliver an even better experience. Key highlights of this
release:
𝐄𝐧𝐡𝐚𝐧𝐜𝐞𝐝 𝐩𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞: We have refactored our backtesting
and fit methods to leverage multi-processing parallelization, resulting in
faster and more efficient computations.
𝐄𝐱𝐩𝐚𝐧𝐝𝐞𝐝 𝐛𝐚𝐜𝐤𝐭𝐞𝐬𝐭𝐢𝐧𝐠 𝐟𝐮𝐧𝐜𝐭𝐢𝐨𝐧𝐚𝐥𝐢𝐭𝐲: With
new backtesting configurations, you now have more control over when the
forecaster is retrained. This allows for better evaluation and fine-tuning
of different scenarios.
Skforecast is a Python library that eases using scikit-learn regressors as
single and multi-step forecasters. It also works with any regressor
compatible with the scikit-learn API (pipelines, CatBoost, LightGBM,
XGBoost, Ranger...).
Docs: https://skforecast.org/
Why use skforecast?
The fields of statistics and machine learning have developed many excellent
regression algorithms that can be useful for forecasting, but applying them
effectively to time series analysis can still be a challenge. To address
this issue, the skforecast library provides a comprehensive set of tools
for training, validation and prediction in a variety of scenarios commonly
encountered when working with time series. The library is built using the
widely used scikit-learn API, making it easy to integrate into existing
workflows. With skforecast, users have access to a wide range of
functionalities such as feature engineering, model selection,
hyperparameter tuning and many others. This allows users to focus on the
essential aspects of their projects and leave the intricacies of time
series analysis to skforecast.
Happy forecasting!
--
Joaquín Amat Rodrigo
