![]() The paket install process will pin all dependencies to exactly the versions from the external paket.lock file. With the net netcore release and the switch to provide more and more netstandard-only packages Soda player extracting additional dependancies install# The Paket team noticed a dramatic increase of the well known "packages" folder. Historically one way was to tell Paket that you only want to compile for framework: net45. netcore project files don't require any explicit dll-references.csproj/fsproj files can references files in the global cache.Load scripts can reference the files in the global cache.On the other side more features are provided by Paket and the packages folder has become more and more redundant: However, this doesn't prevent netstandard dependencies in all situations. Do not extract into the "packages" folder but use a globally shared directory storage: none You can opt-out of generating the packages folder by using the storage option: 1: 2: 3: 4: 5: Therefore, the paket team decided to make the "packages" folder opt-out. However, the behavior is undefined and may change (please open an issue if you depend on the current behavior or we break you). Soda player extracting additional dependancies download#. ![]() Soda player extracting additional dependancies install#.Having a “dev” is really handy if most packages (like most scikit-hep packages) all provide it.Īliases could also be useful, if you rename an extra but need to provide the old name for compatibility, etc.Ī shortcut syntax would still be nice, having some way to see what extras are available would be nice, and having a way to install only extras would be great. So if I want to setup a dev environment for a package, I have to go look in setup.py, setup.cfg, or pyproject.toml and find what dependencies are defined. The reason this is important: there is no way to do discovery from PyPI via pip. The main reason for having “combined” dependencies are adding common terms, like “dev” - which is “all the development dependencies”, and “all”, which is all the extras. If I can replace it with, this will remove the need for setup.py’s in a lot of places for me! Look at almost any repo in Scikit-HEP (regardless of whether I worked on it, see Packaging - Scikit-HEP), or at cibuildwheel/setup.py at 31770e9ac7161f7df417e46f712cc3368e0a6aa6 I’m a huge fan of “combined” dependencies, and I’ve looked for them with "" and "." syntax it’s the reason almost all my pure-python repositories have a setup.py - I am manually combining dependencies there. The choice of the underscore is very random and a delimiter that is currently not allowed at the beginning of the optional dependencies group name should be used instead (I haven’t checked if underscore is currently allowed). For example a name starting with an underscore ( _) will be treated as one used only in other sets and will not end up in the parsed requirements on its own. Given that, here is above example again, but with the use of my proposal: Īdditionally, there may be an option to declare an optional dependencies set that can only be used in another sets. "pytest character followed by a name of another optional dependencies set should be used. This example package is having 3 sets of optional dependencies, specified in pyproject.toml file as follows: Let’s consider an imaginary package, called example. In the current PEP 621 state, there is no way to specify an optional dependency that occurs in several groups, without repeating yourself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |