On Tue, Jan 18, 2011 at 2:35 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 18 Jan 2011 07:14:51 +0100
Ezio Melotti ezio.melo...@gmail.com wrote:
+
+Committing Patches
+==
[...]
+
+ svnmerge.py merge -r 42
+
+This will try to apply the patch to the
It is a surprise to find builtin msilib. Why isn't it used?
Originally, because Python needs to be packaged with an older
release (in particular one that isn't itself maintained anymore).
Today, the problem is that the msilib package doesn't support
merge modules (and if such support was added,
On Wed, Feb 2, 2011 at 6:33 PM, anatoly techtonik techto...@gmail.com wrote:
Making and testing a patch from Python checkout requires compiling
Python, which is not possible for Windows users.
That latter comment hasn't been true since Microsoft started releasing
the Visual Studio Express
On Wed, Feb 2, 2011 at 10:36 AM, Martin v. Löwis mar...@v.loewis.de wrote:
It is a surprise to find builtin msilib. Why isn't it used?
Originally, because Python needs to be packaged with an older
release (in particular one that isn't itself maintained anymore).
That doesn't answer the
On Wed, Jan 26, 2011 at 23:20, brett.cannon python-check...@python.org wrote:
+The in-development branch is where new functionality and semantic changes
new functionalities (dunno if it's plural in english or not)?
+occur. Currently this branch is known as the py3k branch. The next minor
On 02/02/2011 11:04, Sandro Tosi wrote:
On Wed, Jan 26, 2011 at 23:20, brett.cannonpython-check...@python.org wrote:
+The in-development branch is where new functionality and semantic changes
new functionalities (dunno if it's plural in english or not)?
It's an odd one. Functionality can be
On Wed, Feb 2, 2011 at 12:27 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Feb 2, 2011 at 6:33 PM, anatoly techtonik techto...@gmail.com wrote:
Making and testing a patch from Python checkout requires compiling
Python, which is not possible for Windows users.
That latter comment hasn't
On Wed, Feb 2, 2011 at 10:33 AM, anatoly techtonik techto...@gmail.com wrote:
How about patches sent by users who track and fix bugs directly in
codebase of their Python installation?
While I don't personally endorse the above approach, if you're going
to develop inside your installed
On Wed, 2 Feb 2011 12:04:44 +0100
Sandro Tosi sandro.t...@gmail.com wrote:
+Security
+
+A branch less than five years old but no longer in maintenance mode.
+
+The only changes made to a branch that is being maintained for security
+purposes are somewhat obviously those related
In an attempt to record the xml exchange in an xmlrpclib.ServerProxy
connection, I set its verbose flag to 1.
This is the whole premise, and the rest of this message contains a bug
report, and general complaints about the API.
ServerProxy, or to be a bit more specific, the Transport class (which
I'm having some power issues due to a major snow storm so my build slave is
turned off.
Don't worry, everyone's favorite OS will be back to work within the next few
days.
___
Python-Dev mailing list
Python-Dev@python.org
Hello all,
This is my first stab at contributing to this list. I'm writing to lobby for
bug #8797's fix to be removed and for my fix to put in in its place. I'm
probably doing this wrong, so please bear with me. I will embrace whatever
scathing criticism I get.
The ticket covers all the
On Wed, Feb 2, 2011 at 10:55 AM, Sam Bull osir...@gmail.com wrote:
.. I'm writing to lobby for bug #8797's fix to be removed and for my fix to
put in in its place.
Please open a separate issue for your patch. Patches attached to
closed issues will be lost.
Hi Sam
On Wed, Feb 2, 2011 at 5:55 PM, Sam Bull osir...@gmail.com wrote:
This is my first stab at contributing to this list. I'm writing to lobby for
bug #8797's fix to be removed and for my fix to put in in its place.
For what it's worth, I was already about to include your patch as a
Is there or will there be support for python merge modules so we can include
python in our installer?
Also, the discussions I saw about windows installers not removing the path on
uninstall is completely false as regards the installers that wix creates, at
least. I've modified the path many
Am 02.02.2011 13:50, schrieb anatoly techtonik:
We should add less
hardcore instructions how to use bundled diff.py for creating simple
patches like docstring, comment fixes or generating new testcases.
This will greatly reduce the barrier for starting with development.
Given the length of
Le 19/01/2011 18:04, Georg Brandl a écrit :
Am 19.01.2011 16:25, schrieb Eric Smith:
Bonus question: if we remove maintainers.rst from py3k, what do we do in
3.1 and 2.7? I’d favor removing them over keeping outdated versions.
Is there not some advantage to knowing who was the maintainer (or
On Wed, Feb 2, 2011 at 06:50, anatoly techtonik techto...@gmail.com wrote:
On Wed, Feb 2, 2011 at 12:27 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Feb 2, 2011 at 6:33 PM, anatoly techtonik techto...@gmail.com
wrote:
Making and testing a patch from Python checkout requires compiling
On Wed, Feb 02, 2011 at 03:52:17PM +0200, Erez Sh wrote:
Also, ServerProxy should accept an optional output file (=a class with
write,writelines methods), which will be the target of all prints.
Why not logging?
Oleg.
--
Oleg Broytmanhttp://phdru.name/
Am 02.02.2011 20:01, schrieb Hoyt, David:
Is there or will there be support for python merge modules so we can
include python in our installer?
I haven't planned any. Contributions are welcome.
But has there been thought towards migrating away from msilib and using
platform standard tools
Is there or will there be support for python merge modules so we can
include python in our installer?
I haven't planned any. Contributions are welcome.
But has there been thought towards migrating away from msilib and using
platform standard tools such as wix (used by ms office, visual
Hello,
--- python/branches/release31-maint/Lib/configparser.py (original)
+++ python/branches/release31-maint/Lib/configparser.py Wed Feb 2
22:35:48 2011
@@ -88,7 +88,7 @@
try:
-from collections import OrderedDict as _default_dict
+from collections import
On Wed, Feb 2, 2011 at 15:27, Hoyt, David ho...@llnl.gov wrote:
The Installer COM object is the platform standard mechanism, and that's what
msilib uses.
Why maintain a lib when there's (better), free alternatives out there that
are maintained by Microsoft itself? (okay, a group at
On Thu, Feb 3, 2011 at 2:13 AM, Alexander Belopolsky
alexander.belopol...@gmail.com wrote:
On Wed, Feb 2, 2011 at 10:55 AM, Sam Bull osir...@gmail.com wrote:
.. I'm writing to lobby for bug #8797's fix to be removed and for my fix to
put in in its place.
Please open a separate issue for your
The Installer COM object is the platform standard mechanism, and
that's what msilib uses.
Why maintain a lib when there's (better), free alternatives out there
that are maintained by Microsoft itself?
Using msilib is easier than using Wix. It's also more flexible.
All you have to know is
On Wed, Feb 2, 2011 at 11:48, Éric Araujo mer...@netwok.org wrote:
Le 19/01/2011 18:04, Georg Brandl a écrit :
Am 19.01.2011 16:25, schrieb Eric Smith:
Bonus question: if we remove maintainers.rst from py3k, what do we do in
3.1 and 2.7? I’d favor removing them over keeping outdated versions.
On Thu, Feb 3, 2011 at 7:38 AM, eric.araujo python-check...@python.org wrote:
Author: eric.araujo
Date: Wed Feb 2 22:38:37 2011
New Revision: 88324
Log:
Merged revisions 86236,86240,86332,86340,87271,87273,87447 via svnmerge from
svn+ssh://python...@svn.python.org/python/branches/py3k
Martin v. Löwis mar...@v.loewis.de wrote:
The Installer COM object is the platform standard
mechanism, and that's what msilib uses. I really see no need to move
away from that - it can create arbitrary MSI files.
I've used it to package UpLib for Windows -- see
Thanks Nick, I moved the entries.
Cheers
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
all fixed
On Wed, Feb 2, 2011 at 03:04, Sandro Tosi sandro.t...@gmail.com wrote:
On Wed, Jan 26, 2011 at 23:20, brett.cannon python-check...@python.org
wrote:
+The in-development branch is where new functionality and semantic changes
new functionalities (dunno if it's plural in english or
Using msilib is easier than using Wix. It's also more flexible.
IMO, no. It's simply not.
All you have to know is how the MSI schema works.
Same with WiX.
It could easily be extended to do so, in a straight-forward manner.
Other packaging apps already have it - no work needed.
(actually,
If Python was starting at ground zero, and the choices were to create
a library or to use WiX, the answer might have been different.
However with a mature enough library to suit all the needs that anyone
has been willing to author, it's certainly more work to create the WiX
install and
I found it much easier to use than WiX, which I also tried.
I also used to use the Visual Studio installer projects until I needed
something a lot more robust (e.g., customized UI + localizable strings). msilib
does the job people need it to do and that's fine. I'm really not trying to
argue
On Wed, 02 Feb 2011 17:30:43 -0800, Hoyt, David ho...@llnl.gov wrote:
Definitely not. Python is easier than XML.
I disagree.
Just as an FYI, I believe that most people in the Python community find
XML much more of a pain than Python. Many of us (especially those of
us who are not web
I'm really not trying to start a flame war here (my original post
only asked if there was thought towards migrating away from
msilib). There's legitimate need/desire for a merge module to make
it easier to package a specific Python version.
Please recognize that this question is entirely
As far as the possibility of distributing Python as a merge
module? I'd recommend against it. Shared location merge modules are
a maintenance nightmare, and private location merge modules may
not offer the benefit you need. Better to just install the main
Python msi as part of a suite with
36 matches
Mail list logo
