Log file Viewer

[08:21:43] <McSinyx[m]> not entirely related, should we consider merging #pypa and #pypa-dev

[08:22:41] <McSinyx[m]> the two are quite low traffic and very often development ideas are discussed in #pypa and support questions are asked in #pypa-dev (I'm also guilty of this)

[09:33:39] <abn> Regarding the warehouse RSS feeds and yanked packages: Does any of the feeds publish an item if a released file is yanked?

[09:59:49] <abn> Hmm, answering my own question. No. It is not really published in any of the feeds. Just verified using test.pypi.org

[13:07:20] <ThiefMaster> when switching from setup.py+reqirements.txt to setup.cfg, is there any way to install just the requirements without the package itself? previously i could `pip install -r requirements.txt`, but if i do `pip install -e .` i also install my package of course

[13:07:49] <ThiefMaster> my usecase is CI: i'd like to use the github/travis CI cache to cache the requirements, but not my package itself

[13:09:33] <ThiefMaster> https://github.com/pypa/setuptools/issues/1951 would be nice.. then i could just keep requirements.txt and use `install_requires = file: requirements.txt` in setup.cfg

[13:43:12] <tos9> McSinyx[m]: (+1)

[13:43:28] <tos9> ThiefMaster: setup.cfg doesn't replace requirements.txt

[13:43:41] <tos9> ThiefMaster: it's purely equivalent to setup.py (well, 98% equivalent)

[13:44:32] <ThiefMaster> but what's the point in defining requirements in two places for an end user application (not library) where you only want pinned deps anyway?

[13:45:15] <McSinyx[m]> please elaborate on the two places part

[13:45:19] <tos9> you don't need to, then don't put them in setup.cfg.

[13:45:58] <tos9> ThiefMaster: Note your comment very well supports toad_polo's :) -- that ticket was not suggesting putting requirements.txt in there, nedbat was talking about requirements.in which is a pip-compile file

[13:46:58] <toad_polo> It is a problem that there's no way to install all the requirements for a project except the project.

[13:47:06] <McSinyx[m]> ThiefMaster. as mentioned in the linked issue, setup.py is for weird hacks

[13:47:50] <McSinyx[m]> e.g. keeping req.txt and use something to parse it in setup.py (note that pip install -r also read options from file)

[13:48:45] <ThiefMaster> which means i can't have fully-declarative dependencies (setup.cfg) ;)

[13:49:22] <toad_polo> ThiefMaster: No, you can and should put your dependencies in `setup.cfg`.

[13:51:51] <toad_polo> ThiefMaster: Depending on what you are trying to achieve, probably what you should do is move your dependencies into `setup.cfg` and use `pip-compile` (no arguments) to generate a `requirements.txt`.

[13:52:32] <toad_polo> You can do that as part of your CI, and then `pip install -r requirements.txt` to install all your dependencies without installing the package itself.

[13:53:00] <ThiefMaster> that sounds good :)

[13:53:01] <toad_polo> AFAICT it won't work if you need to install extras or something like that.

[13:54:10] <ThiefMaster> hrm i do need the [dev] extras for CI..

[13:58:39] <McSinyx[m]> just curious (probably I won't come up with anything better than what toad_polo suggested), is it possible for me to view your dependency definitions ThiefMaster?

[13:59:37] <ThiefMaster> McSinyx[m]: https://github.com/indico/newdle/pull/228/files#diff-380c6a8ebbbce17d55d50ef17d3cf906

[14:00:43] <McSinyx[m]> I think you can move [dev] to tox

[14:01:42] <McSinyx[m]> and cache .tox if the test invokation isn't too complicated

[14:01:43] <ThiefMaster> developers also need this stuff

[14:02:21] <McSinyx[m]> if it's declared in tox.ini then running tox would create a venv with those anyway

[14:04:41] <McSinyx[m]> I've just taken a peek at the Makefile: I think it's possible to convert to tox without too much effort

[14:08:59] <McSinyx[m]> *invocation, I'm not German FYI

[14:10:46] <ThiefMaster> isn't tox meant to run tests?

[14:10:54] <ThiefMaster> i never heard about it being used to setup a dev environment

[14:13:41] <ThiefMaster> > and use `pip-compile` (no arguments) to generate a `requirements.txt`

[14:13:43] <ThiefMaster> that looks great

[14:13:49] <ThiefMaster> but not being able to enable extras sucks :/

[14:18:19] <toad_polo> ThiefMaster: I suspect that it would be a good idea to search or / make an issue / PR enabling support for `pip-compile <directory>` and `pip-compile <directory>[extras]`.

[14:19:01] <toad_polo> I do think that `tox` is probably better though. It's designed for this kind of thing.

[14:19:40] <toad_polo> Plus I also think you should install your package when you are testing it (and in fact you should probably only test your package if it's installed): https://blog.ganssle.io/articles/2019/08/test-as-installed.html

[14:20:27] <ThiefMaster> of course, and i do that - this is only about being able to cache the deps for CI

[14:20:52] <toad_polo> How about `pip wheel .[dev]`?

[14:21:36] <toad_polo> `pip wheel .[dev] -w <cache_dir>`, then you can configure `pip` with an environment variable to first search `<cache_dir>` before hitting PyPI.

[14:22:07] <toad_polo> That will mean that you'll get a fixed version, mind you — it's not a caching index like devpi.

[14:29:26] <graingert> ThiefMaster: I use dephell

[14:29:32] <graingert> ThiefMaster: https://github.com/PyCQA/modernize/pull/228/checks?check_run_id=1112643738#step:6:1

[14:30:08] <graingert> ThiefMaster: you probably want to steal my config from that repo

[14:31:27] <graingert> and you can make a tox, "dev" env

[17:47:49] <ThiefMaster> is this a bug? i published indico==2.3 to pypi a while ago (30m or so), but `pip install --use-feature=2020-resolver -U indico` does not upgrade it. the currently-installed version is from a local wheel, `indico @ file:///opt/indico/wheels/indico-2.3.dev0%2B202009141513.3dbbddef32-py2-none-any.whl` according to `pip freeze`

[17:48:20] <ThiefMaster> pip just shows `Requirement already satisfied: indico in ./.venv/lib/python2.7/site-packages (2.3.dev0+202009141513.3dbbddef32)` for it

[17:48:41] <ThiefMaster> if i disable the resolver, it works fine

[19:40:22] <dunk> Is it possible somehow to query a pip package for the actual python-level packages that it provides (e.g. PyYAML --> yaml)

[21:02:07] <sumanah> reminder https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-resolver-in-20-2-2020 that now's a good time to try out the beta of the new dependency resolver so you're forewarned and your environment doesn't break next month

[22:25:18] <FFY00> wouldn't it be a good idea to have pip actively prompting users to use the new resolver? I think these kind of announcements can be easily missed

[22:26:40] <FFY00> "Next release will use the new dependency resolver, try it beforehand with --use-feature=2020-resolver and let us know if you have any issues!"

[22:27:49] <FFY00> will there be at least a flag to use the old resolver if things break?

[23:00:58] <graingert> dunk: pipreqs seems the only way

[23:01:13] <graingert> and if there's a whl

[23:01:23] <graingert> Where there's a whl there's a way

[23:21:57] <toad_polo> FFY00: I think there will be at least one release with a flag to opt out of the new resolver.