* Ben Finney: " Best practice: exclude generated ‘foo.egg-info’ files from
source and VCS (was: Best practice: .egg-info with pybuild from git)" (Fri,
22 Nov 2013 11:35:11 +1100):
@Ben: apologies, first mail was sent to your mail address instead of the group
> Piotr Ożar
* Piotr Ożarowski: " Re: Best practice: .egg-info with pybuild from
git" (Thu, 21 Nov 2013 19:56:05 +0100):
@Piotr: apologies for first not sending the mail to the group, but your mail
address
> [Thomas Goirand, 2013-11-21]
> > On 11/21/2013 08:28 PM, Mathias Behrl
Piotr Ożarowski writes:
> I think Mathias is asking about how to tell git that it should ignore
> these files as well. IMO you should ask upstream to not ship these
> files in git repo/tarballs or remove them in the first commit after
> each merge with upstream.
Yes, the best course is to convin
[Thomas Goirand, 2013-11-21]
> On 11/21/2013 08:28 PM, Mathias Behrle wrote:
> > So finally I would appreciate any input on
> >
> > 1) Which is the preferred procedure to handle .egg-info directories together
> >with building from git?
> >
> > 2) Is there a way to satisfy all common build too
Hello Pythonistas,
I am just searching for some input/confirmation for the best practice with
respect to .egg-info provided in upstream tarballs.
My initial approach was based on the recommendations in the Python
Library Style Guide [1] and App Style Guide [2] to avoid evtl. double build
failures
On 11/21/2013 08:28 PM, Mathias Behrle wrote:
> So finally I would appreciate any input on
>
> 1) Which is the preferred procedure to handle .egg-info directories together
>with building from git?
>
> 2) Is there a way to satisfy all common build tools as debuild,
>git-buildpackage, pbuil
6 matches
Mail list logo
