Search results

== Fedora-Wide Changes and Improvements == == Changes to talk about for regular users ==

{{DISPLAYTITLE:Finalizing Fedora's Switch to Python 3}} ...base]. This page is no longer updated regularly. Talk to the [[SIGs/Python|Python SIG]] if you want to discuss it. }}

...eally about to learn the necessary tools. In my project, the main focus is Python scripting language. The second release is to working towards the direction ...org/fedora-packager fedpkg] is a component within Fedora Packager. It is a python library and cli front end for managing Fedora packages within Fedora's git

Change the python-suds package to use the fork maintained by Jurko Gospodnetić. <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)

Python packages should be sure to have: BuildRequires: python-devel

= python-dateutil 2.x = ...ould work only for python3, so the package was not updated in Fedora. Now, python-dateutil is at version 2.4 and does work with python2. Fedora packages can

== EPEL 7 in Python 3 Plan Draft == === Why Python 3 in EPEL 7, Why not SCLs ===

...astronomers and astrophysicists. This includes observatory control as well as scientific data analysis and astrophotography. ...y Spin provides a complete scientific Python environment (2 and 3) as well as the [http://www.astromatic.net/ AstrOmatic] software. For observational ast

<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) Bugzilla states meaning as usual:

= GCC Python Plugins <!-- The name of your feature --> = ...d be able to use this to easily extend GCC by writing Python scripts, such as adding new warnings for a library that they work on, without needing to use

{{DISPLAYTITLE:Fedora Packaging Guidelines for Python}} == Python Version Support ==

...: via wiki) – e.g. new packages that were in testing for some days as well as important bugfixes (security, hard crashers, ...) * should we try to bug c4chris, so he runs his package status script for epel as well?

...ly update each one using [[rpm]]. Introduced in Fedora 18, it has been the default package manager since Fedora 22. * Documented, solid Python API

{{DISPLAYTITLE:Fedora Packaging Guidelines for Python}} == Python Version Support ==

...ture brings version 1.41.0 of Boost to Fedora 13, together with Boost.MPI. As a side effect, Boost will be built with CMake (instead of BJam) || 2010- ...an report detailed information on the internals of the Python 2 and Python 3 runtimes || 2010-04-06

* python-sphinx ** python-execnet

.../package-maintainers/Staying_Close_to_Upstream_Projects/ upstream] as much as feasible, and your feedback will help improve not only Fedora but Linux and ...compatibility. The classic yum command line tool renamed to yum-deprecated as a transitional step for tools still using it.

Self Contained Changes are: * changes to isolated/leaf package without the impact on other packages/rest of the d

<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same nam = Changes/Default_Package_Manager_Is_DNF =

{{admon/warning|This is a draft of proposed changes for [[Packaging:Python]] page. For more details, see: [https://fedorahosted.org/fpc/ticket/598 FPC = Python Packaging Guidelines =