On Fri, Sep 25, 2015 at 10:09:50AM -0400, Paul Wouters wrote:
> It's nice to be able to edit the .py for testing without going through
> hoops or building/installing rpms.
Right, but you know that if you're doing that in /usr/lib, that's
*gross*, right? :)
--
Matthew Miller
On 09/25/2015 08:36 AM, Matthew Miller wrote:
On Fri, Sep 25, 2015 at 10:09:50AM -0400, Paul Wouters wrote:
It's nice to be able to edit the .py for testing without going through
hoops or building/installing rpms.
Right, but you know that if you're doing that in /usr/lib, that's
*gross*,
On 9/25/15, Matthew Miller wrote:
> On Fri, Sep 25, 2015 at 11:30:38AM -0400, Bohuslav Kabrda wrote:
>> Maybe we could utilize weak dependencies here. The python-foo package
>> would have only bytecompiled files and would Recommend
>> python-foo-sourcefiles. That way
On Fri, Sep 25, 2015 at 11:30:38AM -0400, Bohuslav Kabrda wrote:
> Maybe we could utilize weak dependencies here. The python-foo package
> would have only bytecompiled files and would Recommend
> python-foo-sourcefiles. That way python-foo-sourcefiles would be
> installed in standard setting, but
On 09/25/2015 10:04 AM, Matthew Miller wrote:
On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
Also, you might consider to ship the precompiled bytecode just
optionally, using recommends.
On contrary, if you insist on shipping the bytecode, why you don't drop
the .py files? I see a
- Original Message -
> On 09/25/2015 08:36 AM, Matthew Miller wrote:
> > On Fri, Sep 25, 2015 at 10:09:50AM -0400, Paul Wouters wrote:
> >> It's nice to be able to edit the .py for testing without going through
> >> hoops or building/installing rpms.
> >
> > Right, but you know that if
On 09/25/2015 10:01 AM, Christopher Meng wrote:
> On 9/25/15, Matthew Miller wrote:
>> On Fri, Sep 25, 2015 at 11:30:38AM -0400, Bohuslav Kabrda wrote:
>>> Maybe we could utilize weak dependencies here. The python-foo package
>>> would have only bytecompiled files and
* Matthew Miller:
> On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
>> Also, you might consider to ship the precompiled bytecode just
>> optionally, using recommends.
>>
>> On contrary, if you insist on shipping the bytecode, why you don't drop
>> the .py files? I see a lot of
Dne 25.9.2015 v 16:04 Matthew Miller napsal(a):
> On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
>> Also, you might consider to ship the precompiled bytecode just
>> optionally, using recommends.
Just to be clear, not/optional shipping the bytecode is the preferred
method IMO
Dne 25.9.2015 v 16:15 Mathieu Bridon napsal(a):
> On Fri, 2015-09-25 at 10:04 -0400, Matthew Miller wrote:
>> On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
>>> Also, you might consider to ship the precompiled bytecode just
>>> optionally, using recommends.
>>>
>>> On contrary, if
On Fri, Sep 25, 2015 at 3:25 PM, Vít Ondruch wrote:
> Dne 25.9.2015 v 16:15 Mathieu Bridon napsal(a):
> > (it is invaluable for learning and
> > debugging purposes to be able to read/edit the code).
>
> Come on, this is not an argument. We don't install source code for any
>
On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
> Also, you might consider to ship the precompiled bytecode just
> optionally, using recommends.
>
> On contrary, if you insist on shipping the bytecode, why you don't drop
> the .py files? I see a lot of duplication all around python
On Fri, 25 Sep 2015, Matthew Miller wrote:
On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
Also, you might consider to ship the precompiled bytecode just
optionally, using recommends.
On contrary, if you insist on shipping the bytecode, why you don't drop
the .py files? I see a
On Fri, 2015-09-25 at 10:04 -0400, Matthew Miller wrote:
> On Thu, Sep 24, 2015 at 10:10:40AM +0200, Vít Ondruch wrote:
> > Also, you might consider to ship the precompiled bytecode just
> > optionally, using recommends.
> >
> > On contrary, if you insist on shipping the bytecode, why you don't
>
On Fri, Sep 25, 2015 at 4:04 PM, Matthew Miller
wrote:
>> On contrary, if you insist on shipping the bytecode, why you don't drop
>> the .py files? I see a lot of duplication all around python packages
Don't do that, it has impact on functionality.
We did this for
On Fri, 2015-09-25 at 16:17 +0200, Fabian Deutsch wrote:
> On Fri, Sep 25, 2015 at 4:04 PM, Matthew Miller
> wrote:
> > > On contrary, if you insist on shipping the bytecode, why you
> > > don't drop
> > > the .py files? I see a lot of duplication all around python
> > >
On Fri, Sep 25, 2015 at 4:26 PM, Stephen Gallagher wrote:
> On Fri, 2015-09-25 at 16:17 +0200, Fabian Deutsch wrote:
>> On Fri, Sep 25, 2015 at 4:04 PM, Matthew Miller
>> wrote:
>> > > On contrary, if you insist on shipping the bytecode, why you
>>
17 matches
Mail list logo