On Sat, Mar 24, 2018 at 9:29 AM, Nick Coghlan wrote:
> On 23 March 2018 at 02:58, Gregory Szorc wrote:
>
>> I'd like to start a discussion around practices for vendoring package
>> dependencies. I'm not sure python-dev is the appropriate venue for
On 24 March 2018 at 19:29, Nick Coghlan wrote:
> On 23 March 2018 at 02:58, Gregory Szorc wrote:
>
>> I'd like to start a discussion around practices for vendoring package
>> dependencies. I'm not sure python-dev is the appropriate venue for this
>>
On 23 March 2018 at 02:58, Gregory Szorc wrote:
> I'd like to start a discussion around practices for vendoring package
> dependencies. I'm not sure python-dev is the appropriate venue for this
> discussion. If not, please point me to one and I'll gladly take it there.
>
module before their own appears ahead of
it on sys.path... thinking out loud here).
Cheers,
Steve
Top-posted from my Windows phone
From: Barry Warsaw
Sent: Thursday, March 22, 2018 12:56
To: Python-Dev
Subject: Re: [Python-Dev] Better support for consuming vendored packages
On Mar 22, 2018, at 12
On Mar 22, 2018, at 12:33, Oleg Broytman wrote:
>
> On Thu, Mar 22, 2018 at 12:30:02PM -0700, Barry Warsaw
> wrote:
>> Developers are mostly going to use pip, and maybe a requirements.txt,
>
> +virtual envs to avoid problems with global site-packages.
On Thu, Mar 22, 2018 at 12:30:02PM -0700, Barry Warsaw wrote:
> Developers are mostly going to use pip, and maybe a requirements.txt,
+virtual envs to avoid problems with global site-packages.
IMO virtualenv for development and frozen app for distribution solve
the
On Mar 22, 2018, at 09:58, Gregory Szorc wrote:
>
> Not all consumers of Python packages wish to consume Python packages in the
> common `pip install ` + `import ` manner. Some Python
> applications may wish to vendor Python package dependencies such that known
>
On 3/22/2018 10:48 AM, Oleg Broytman wrote:
> Hi!
>
> On Thu, Mar 22, 2018 at 09:58:07AM -0700, Gregory Szorc
> wrote:
>> Not all consumers of Python packages wish to consume Python packages in the
>> common `pip install `
>
> IMO `pip` is for developers. To package
Hi!
On Thu, Mar 22, 2018 at 09:58:07AM -0700, Gregory Szorc
wrote:
> Not all consumers of Python packages wish to consume Python packages in the
> common `pip install `
IMO `pip` is for developers. To package and distribute end-user
applications there are rpm,
I'd like to start a discussion around practices for vendoring package
dependencies. I'm not sure python-dev is the appropriate venue for this
discussion. If not, please point me to one and I'll gladly take it there.
I'll start with a problem statement.
Not all consumers of Python packages wish
10 matches
Mail list logo