Greetings all! I am happy to announce that after a long hiatus, there is
a pre-release of pipenv available for testing.
You can read the full announcement at
https://discuss.python.org/t/announcement-pipenv-beta-release/4051
I look forward to your feedback.
Thanks,
Dan
--
Dan Ryan
Software
to say 'thanks' to Sumana if you see her on IRC, she is
responsible for moving this release forward and is pretty great!
I'd appreciate the help.
Thanks,
-Dan Ryan (techalchemy)
|[0]:| You can look at
https://github.com/pypa/pipenv/issues/3742#issuecomment-492100711and
https://github.com/pypa
with virtualenv usage too.
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Feb 20, 2019, at 11:27 AM, Steve Dower wrote:
>
>> On 20Feb2019 0803, Dan Ryan wrote:
>> One final thing this enables as far as I understand is a sort of npm-like
>> option for ignoring resolution conflic
a resolution.
My only concerns with this PEP relate to bloat. I’d be interested in ways to
reduce duplication across a system with many such folders.
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Feb 20, 2019, at 10:19 AM, Steve Dower wrote:
>
>> On 20Feb.2019 0533, Tzu-ping
y
the provided direct url
· So that leaves me with -- specifiers may be useful for comparison but
_only_ for comparing direct url subdependencies
Dan Ryan
gh: @techalchemy <https://github.com/techalchemy> // e: d...@danryan.co
From: Tzu-ping Chung [mailto:uranu...@gmai
. Just because someone put a ref doesn’t mean they
don’t update that ref’s content :/
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Jan 29, 2019, at 7:15 PM, Nathaniel Smith wrote:
>
>> On Tue, Jan 29, 2019 at 4:11 PM Dan Ryan wrote:
>>
>> In the ideal future would
it wrong? Do you trust the
version in the package or do you allow an override? Conflict resolution is
possible either way but the desired behavior there would seem to favor the
former imo
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Jan 29, 2019, at 4:15 PM, Nathaniel Smith wr
This is great news! Looking congrats and glad to have you back with us!
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Dec 24, 2018, at 3:13 PM, Sumana Harihareswara wrote:
>
> It's been eight months since the release of Warehouse[0] and the sunsetting
> of legacy PyPI[1].
Nice work! Thanks for sharing
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Message-
> From: John Thorvald Wodder II [mailto:jwod...@gmail.com]
> Sent: Thursday, October 18, 2018 12:07 PM
> To: distutils-sig@python.org
> Subject: [Distutils] Announcing Whee
Sorry for causing you additional frustration. I was also frustrated and
underscoring a sense that seems to come through in most of our interactions for
a number of reasons. It isn’t my intention to cause you additional grief, so I
apologize for fanning the flames.
Dan Ryan // pipenv maintainer
discussion?
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Message-
> From: Paul Moore [mailto:p.f.mo...@gmail.com]
> Sent: Sunday, September 30, 2018 3:57 PM
> To: Tzu-ping Chung
> Cc: Distutils
> Subject: [Distutils] Re: Notes from python core sprint on work
ace to put stuff, which schema
to follow, and honestly working with some new users. I do this quite a bit but
I haven't done any formal information gathering. Anecdotally I'll always tell
you I'm right, but if we had some user data on specific pain points /
usability issues I'd definitely be
Thanks Chris, these are excellent suggestions. Can you provide a reference to a
PR you’re working or have worked on so we can jumpstart the process on our end?
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Sep 25, 2018, at 5:47 PM, Chris Jerdonek wrote:
>
>> On Tue, Sep 25,
implementations, which I believe still
have some dependency on pip. For us the roadmap is basically to figure out
- where do the abstractions live
- how do we start
- ???
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Sep 25, 2018, at 8:11 AM, Paul Moore wrote:
>
>> On Tue, 25 Sep 2
is desirable if we want to
maintain this separation as it will probably be confusing -- and the
distinction is already subtle
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
From: Joni Orponen [mailto:j.orpo...@4teamwork.ch]
Sent: Monday, September 24, 2018 11:43 AM
To: distutils-sig
Subject
know we have had unproductive conversations on the issue tracker,
please don’t bring them to the mailing list.
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Sep 20, 2018, at 2:29 PM, Bert JW Regeer wrote:
>
>
>
>> On Sep 20, 2018, at 12:11, Tzu-ping Chung wrote:
>
AFAIK none of the pipenv maintainers have access to the Pipfile repo anyway
besides Kenneth — We are maintaining a fork? Reimplementation? with additional
validation
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Sep 21, 2018, at 9:31 AM, Paul Moore wrote:
>
>> On Fri,
will be able to break this down into a coherent list
of other useful smaller utilities which could be consumed.
Unfortunately this is a mailing list and the discussion is likely to continue
so there is a high probability that my name will show up in your inbox
Dan Ryan
gh: @techal
I have no issue moving things to the PyPA, the list was more of a ‘which of
these is useful’ check
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
From: Donald Stufft [mailto:don...@stufft.io]
Sent: Thursday, September 20, 2018 8:15 AM
To: Dan Ryan
Cc: Tzu-ping Chung; Distutils
Subject: Re
meaningful when the conversation is
about ‘how do we stop doing different things’ ?
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Sep 20, 2018, at 1:22 AM, Chris Jerdonek wrote:
>
>> On Wed, Sep 19, 2018 at 8:54 PM, Dan Ryan wrote:
>> I should clarify that we have a
platform)
https://github.com/sarugaku/virtenv -- python api for virtualenv creation
Happy to provide access or take advice as needed on any of those. Thanks
all for the receptiveness and collaboration
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
From: Donald Stufft [mailto:don...@stufft.
view someone's PR down the road to swap
out some internals.
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Message-
> From: Paul Moore [mailto:p.f.mo...@gmail.com]
> Sent: Tuesday, September 18, 2018 6:09 PM
> To: Donald Stufft
> Cc: Dan Ryan; Thomas Kluyver
a look at what most of our projects are
using from pip can shoot me a message off-list and I can send you a link to
the repository
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Message-
> From: Paul Moore [mailto:p.f.mo...@gmail.com]
> Sent: Tuesday, September 18, 201
To add to these responses, Tzu Ping and I have tried this in a myriad of
creative ways and mostly haven’t been successful while relying on pip’s cli.
The right answer is to invoke the virtualenv pip, it’s just easier
-D
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Sep 14, 2018, a
y and some functionality to handle the prefix
issues would be a big help, but I’m not sure how many of the open PRs will
actually accomplish that.
Perhaps if venv had all of these things, we could just publish a backport for
it and that would provide a transition path
Dan Ryan
gh: @techalche
in seclusion trying to tackle this.
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Aug 21, 2018, at 9:02 AM, Tzu-ping Chung wrote:
>
> Hi Chris,
>
> From my understanding (it is totally possible I could miss something),
> get_vcs_deps()
> is specifically used only for re
end. Our biggest pain point has been some combination of sanitizing and
parsing inputs/markers -- pip does a LOT of internal parsing which is not in
any other library (besides requirementslib, somewhat).
Dan Ryan
gh: @techalchemy <https://github.com/techalchemy> // e: d...@danr
12 hour time shift already, so we will just pick a
good platform to continue the more detailed discussions on. I will follow up
on the other thread we had (sorry again!)
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Message-
> From: Pradyun Gedam [mailto:pradyu..
for clarification there
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Aug 20, 2018, at 4:32 AM, Chris Jerdonek wrote:
>
> Thanks. Is the state of affairs as you described them what you're
> planning for the future as well, or do you anticipate any changes
> worthy of note?
>
and
pretend there is no code behind pip as we construct dependency graphs.
We run into some risk of rework on the resolver front. We just finished a
stateful, forward looking, backtracking resolver (we checked in with Pradyun
but he is quite busy).
Dan Ryan // pipenv maintainer
gh
As a heavy user of certbot myself across numerous systems I would echo Nick and
others’ suggestions about native packaging. Third party tools and docker
containers are basically non starters.
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Jul 26, 2018, at 11:30 AM, Chris Barker - N
documentation, a script, and a patched .deb based on some info we
stumbled across.
The way to get this all working is described in this paste:
https://markdownshare.com/view/b66db977-2dab-4cf6-ad2a-2c88fecd7499
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Mess
1.23]
Asterisks mine
And just to confirm -- from the current setup.py for requests (found at
https://github.com/requests/requests/blob/991e8b76b7a9d21f698b24fa0058d3d5968721bc/setup.py#L54):
> 'urllib3>=1.21.1,<1.24'
Dan Ryan
gh: @techalchemy // e: d...@danryan.co
> -Original Mes
made sizeable
changes to the dependency resolution stack and bundling allows us to patch
freely.
I don’t know that we are a good example though, we are doing significantly more
with pip internals than the average project
-dan
Dan Ryan // pipenv maintainer
gh: @techalchemy
> On Apr 14, 2
34 matches
Mail list logo
