different package versions for different python versions

My application can work under either python2 or python3, but some requirements have different versions. (For example, ipython >=6 for python3, < 6 for python2.) If I specify ipython="*", pipenv lock will pick ipython==6.3.1 I tried specifying

ipython = {version = ">=6.3", markers="python_version >= '3'"}
ipython = {version = "<6", markers="python_version < '3'"}

but pipenv complains about re-using the identifier.

I’m not sure if this is possible; if so I could not find it in the documentation (and maybe that case should be made explicit in the documentation.) If it is not possible and is not intended to be, maybe that should also be said explicitly. Regards

[thernstig]

There are multiple ways it can be achieved with TOML. Which one is the best can be debated. Here is a quick solution:

ipython = [ {version = ">=6.3", markers="python_version >= '3'"},
            {version = "<6", markers="python_version < '3'"} ]

This is a normal array with inline tables, taken directly from the TOML spec.

[kalfa]

@uranusjr can I know why this encouragement? It seems to me that a wrapper solution defeat the purpose of a Pipfile itself.

Why should someone who subscribes to the idea behind pipfile and pipenv, should then choose to use code to describe dependancy as a preferred/encouraged approach? Let’s do “that” until is possible otherwise: yes. But encouraging it, seems opposite to the purpose of the project. Am I missing your point?

I agree on the “if propose, at least propose doable” Although, use cases collection can be done with meta code, and doesn’t really change anything, while enriching the discussion.