Reference pip’s own bootstrapping instructions rather thanĭuplicating them. Pip as the default installer and recommending that other projects This specific problem can be partially alleviated by strongly promoting Tools available, and different projects recommend different tools. Particular problematic when there are multiple competing installation They need updating by every project that has duplicated them. Install their own project then whenever these instructions need updates Their users how to install the package manager before telling them how to If a project chooses to duplicate the installation instructions and tell New to programming, the use of command line tools and editing systemĮnvironment variables) are a regular feature of feedback the core Pythonĭevelopers receive from professional educators and others introducing new Of dealing with this problem for beginners (who are often also completely Mac OS X users, or more conservative Linux distributions. No such assistance is available for Windows and Provides the relevant cross-platform installer command (such as many major On systems with platform package managers that include a package that Package they can install to make the command work, but that only works Global hook that looks for commands that don’t exist and suggest an OS Some operating systems may ease this pain by providing a Users may get a confusing error message when the installation commandĭoesn’t work. If a project simply assumes a user already has the tooling then beginning Completely forgo the use of dependencies to ease installation concernsĪll of these available options have significant drawbacks.Duplicate the instructions and tell their users how to install the.Assume the user already has a suitable cross-platform package manager. ![]() Projects are currently required to choose from a variety of undesirable The effect of this is that third-party Python This means that, to work effectively with the Python Package IndexĮcosystem, users must know which package manager to install, where to get The platform package manager may not be clear. Include every package that is available on the Python Package Index, andĮven when a desired third-party package is available, the correct name in Requires first identifying an appropriate package manager and thenĮven on systems that do have a platform package manager, it is unlikely to Installing a third-party Python package into a freshly installed Python Improving the new user experienceĬurrently, on systems without a platform package manager and repository, Relates to better enabling the evolution of the broader Python packagingĮcosystem. The first relates to the experience of new users, while the second There are two related, but distinct rationales for the proposal in this This PEP was accepted for inclusion in Python 3.4 by Martin von Löwis on Python 2.7, 3.3 and 3.4 be updated to officially recommend the use of pipĪs the default installer for Python packages, and that appropriate technicalĬhanges be made in Python 3.4 to provide pip by default in support of
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |