Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience.
...definition, class definition, or method definition, after any comments. This is the standard for Python __doc__ attributes. Immediately following a simple assignment at the top level of a module, class definition, or __init__ method definition, after any comments. See Attribute Docstrings below. Additional string literals found immediately after the docstrings in (a) and (b) will be recognized, extracted, and concatenated. See Additional Docstrings below. @@@ 2.2-style "properties" with attri...
...definition Legacy manylinux tags Package installers Package indexes Rejected alternatives Abstract This PEP proposes a scheme for new 'manylinux' wheel tags to be defined without requiring a PEP for every specific tag, similar to how Windows and macOS tags already work. This will allow package maintainers to take advantage of new tags more quickly, while making better use of limited volunteer time. Non-goals include: handling non-glibc-based platforms; integrating with external package mana...
...packages within stub-packages as incomplete since multiple distributions may populate them. Regular packages within namespace packages in stub-package distributions are considered complete unless a py.typed with partial\n is included. Implementation The proposed scheme of indicating support for typing is completely backwards compatible, and requires no modification to package tooling. A sample package with inline types is available [typed_package], as well as a [stub_package]. A sample packag...
...definitions/requirementVersion" }, { "$ref": "#/definitions/requirementTable" }, { "title": "Multiple specifications", "type": "array", "items": { "$ref": "#/definitions/requirementTable" }, "minLength": 1 } ] }, "optionalRequirementTable": { ...
...package "at a glance". GIVE YOUR PACKAGE A VERSION NUMBER. If you give your package a version number from the start, it will be easier to identify different releases in the future. Even "small" packages should have version numbers. Clarify the LICENSE that you release your package under. If you want to release something as free software, you might want to have a look at the "Open Source Definition", and pick one of the licenses mentioned there under "Example ...
...packages that you have installed on your system. Because the SRPMs encompass all the steps required to build binary RPMs, it is a "fire and forget" process -- the simplest source build ever. <!-- <p><b>Warning:</b> These packages install as "/usr/bin/python2". This is because many of the Red Hat tools rely on "/usr/bin/python" being 1.5. For Python code which requires 2.2, they should probably change to use "/usr/bin/python2". The S...
...packages. <hr /> <li />Q) I'm trying to build the RPMS, but I get: <pre>RPM build errors: File not found by glob: /var/tmp/python2.3-2.3.4-root/usr/lib/python2.3/lib-dynload/_tkinter.so*</pre> <li />A) You need to have the Tk development package installed. This package is usually called "tk-devel", and can be obtained from the same place that you normally find packages for your system. You may also need to install the "tcl-devel" package, if...
...packages, you will explicitly have to run "python2.3". Note that all Python RPMs provided by Python.org and Red Hat provide a "/usr/bin/python2.3" (or similar, with major/minor number), even if they also provide "/usr/bin/python". So, yes, it should be safe. <p /> Note that you may need to build and install a second copy of any packages which you need access to with the supplemental version of Python. You can build packages of these files for the Python 2.3...
...definition file. Like YACC, YAPPS supports custom code before and after the grammar definition. YAPPS parsers integrate with the scanner through a Scanner object, which is passed to the parser as a constructor argument. Even though YAPPS supports definition of tokens in the grammar, we have not used this capability in XPath, since we have provided my own scanner class. The YAPPS parser will only require a token() method from the scanner object, which must return a four-tuple (start, e...
...packages. <hr /> <li />Q) I'm trying to build the RPMS, but I get: <pre>RPM build errors: File not found by glob: /var/tmp/python2.3-2.3.5-root/usr/lib/python2.3/lib-dynload/_tkinter.so*</pre> <li />A) You need to have the Tk development package installed. This package is usually called "tk-devel", and can be obtained from the same place that you normally find packages for your system. You may also need to install the "tcl-devel" package, if...
...packages. <hr /> <li />Q) I'm trying to build the RPMS, but I get: <pre>RPM build errors: File not found by glob: /var/tmp/python2.4-2.4.1c2-root/usr/lib/python2.4/lib-dynload/_tkinter.so*</pre> <li />A) You need to have the Tk development package installed. This package is usually called "tk-devel", and can be obtained from the same place that you normally find packages for your system. You may also need to install the "tcl-devel" package, ...
...packages get confused a lot. That's not their fault; that's because the volunteers who maintain the packaging tools don't have enough time to get everything organized so that it's clear and easy to use. In the last few years, the PSF has gotten grants and used that money to massively improve packaging. We overhauled PyPI and we're making pip more consistent, with genuine attention to user experience. With more funding, we can finally make managing packages pleasant as programming in Python. Sum...
...packages are written with portability in mind. For many packages this means they aim to support a wide range of Python releases. If they depend on libraries such as argparse - which started as external libraries, but later got incorporated into core - specifying a single set of requirements is difficult, as the set of required packages differs depending on the version of Python in use. For other packages, designing for portability means supporting multiple operating systems. However, the signifi...
...packages. Discoverability will hopefully be based on package popularity, like with Django packages for example. Third-party stubs have to be versioned using the lowest version of the source package that is compatible. Example: FooPackage has versions 1.0, 1.1, 1.2, 1.3, 2.0, 2.1, 2.2. There are API changes in versions 1.1, 2.0 and 2.2. The stub file package maintainer is free to release stubs for all versions but at least 1.0, 1.1, 2.0 and 2.2 are needed to enable the end user type check all...
...packages, each of which are independently developed and distributed. In order for her users to properly specify dependencies on the right versions of her packages, she specifies the version numbers in the namespace package's setup.py file. Because Carol wants to have to update one version number per package, she specifies the version number in her module and has the setup.py extract the module version number when she builds the sdist archive. David maintains a package in the standard library, ...
...packages are only a basic building block in a secure package update system. Wheel only provides the building block. What's the deal with "purelib" vs. "platlib"? Wheel preserves the "purelib" vs. "platlib" distinction, which is significant on some platforms. For example, Fedora installs pure Python packages to '/usr/lib/pythonX.Y/site-packages' and platform dependent packages to '/usr/lib64/pythonX.Y/site-packages'. A wheel with "Root-Is-Purelib: false" with all its files in {name}-{version...
...Package Index. "Releases" are uniquely identified snapshots of a project. "Distribution packages" are the packaged files which are used to publish and distribute a release. Depending on context, "package" may refer to either a distribution, or to an importable Python module that has a __path__ attribute and hence may also have importable submodules. "Source archive" and "VCS checkout" both refer to the raw source code for a release, prior to creation of an sdist or binary archive. An "sdist" is ...
...packages that you have installed on your system. Because the SRPMs encompass all the steps required to build binary RPMs, it is a "fire and forget" process -- the simplest source build ever. <h3>Download</h3> <p><ul><li><b>Signature:</b> <ul> <li>Many of the following packages were signed with the GPG key in <a href="/ftp/python/2.3/rpms/KRUD-GPG-KEY">KRUD-GPG-KEY</a> </ul> <li><b>Source:<...