>
> > > IMHO, the main system without a package manager is Windows.
> >
> > AFAICT the MacOS platform also lacks in this area.
>
> Actually, they both have them. Windows has Cygwin (rpm-based), while
> for MacOS Fink (deb-based), MacPorts (FreeBSD ports-like), and
> NetBSD's pkgsrc are all viab
Phillip J. Eby wrote:
> It would be, if .eggs were a packaging format, rather than a binary
> distribution/runtime format.
>
> Remember "eggs are to Python as jars are to Java" -- a Java .jar
> doesn't contain documentation either, unless it's needed at
> runtime. Same for configuration files.
Stephen Hansen writes:
> >
> > > > IMHO, the main system without a package manager is Windows.
> > >
> > > AFAICT the MacOS platform also lacks in this area.
> >
> > Actually, they both have them. Windows has Cygwin (rpm-based), while
> > for MacOS Fink (deb-based), MacPorts (FreeBSD por
At 12:12 AM 4/10/2008 -0700, Stephen Hansen wrote:
>I think PJE's idea here is very good. Just include certain files and
>such in the RPM/DEB that will satisfy the
>"python-package-management" system. For RPM/DEB users and their OS's
>database of packages, its irrelevant largely-- they'll still
On Wed, Apr 09 2008 at 11:12:58AM BRT, Trent Nelson <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Is there another online sprint/bugfix day in the pipeline? If not, can
> there be? ;-)
+1.
The Sao Paulo User's Group gathered to work on the last Bug Day, and I think
it was very productive (both for gener
Hi Martin,
On Wed, 2008-04-09 at 23:27 +0200, "Martin v. Löwis" wrote:
> > Can anyone give me a hand on this? As far as I could
> > investigate, I must change setup.py in order to get this issue fixed,
> > right?
>
> Wrong. I didn't read your entire message, but this is definitely wrong.
> setup.
> If I understood correctly, you're saying that Python's building process
> involves only the C compiler, right? So, in order to fix this issue that
> I've found, I only need to modify configure.in file (and maybe
> Makefile.pre.in). Is that correct?
Correct. There are also some additional shell s
I know that doing merges is rather painful because of the Misc/NEWS
files. Would it be possible to have the NEWS log generated from commit
messages? I was thinking something like this in a message:
Fixed this and that
**NEWS:Library**
#1234 X is now known as Y.
It should be fairly simple to writ
In the past we haven't done that because often the change logs are
either too chatty (they do administrative stuff that doesn't deserve a
NEWS entry) or they are too brief (in the heat of the battle
developers don't always write great changelog entries). While it's
easy to fix NEWS its not easy to
On Thu, Apr 10, 2008 at 7:55 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> In the past we haven't done that because often the change logs are
> either too chatty (they do administrative stuff that doesn't deserve a
> NEWS entry) or they are too brief (in the heat of the battle
> developers d
On Thu, Apr 10, 2008 at 5:59 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Thu, Apr 10, 2008 at 7:55 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > In the past we haven't done that because often the change logs are
> > either too chatty (they do administrative stuff that doesn't des
On Thu, Apr 10, 2008 at 6:24 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> Also, there's the issue of which section of the NEWS file an entry
> should be added. That's often subjective.
>
Agreed. For example we have both Library and Extension Module categories in
the NEWS file. I always e
12 matches
Mail list logo
