D Gentry added the comment: If you would like to keep track of others who would find it useful, I'd be happy to contribute the msi to the community once its completed.
Also, any information or good references that you could recommend that might aid in producing the installer would be appreciated. Steve mentioned the temp directory as possibly being part of the problem and that would make sense as its only when installer make use of this that the issues seem to occur so I will definitely be looking at that as a possible root cause for the failure. Steve also mentioned that it's not as easy to produce an installer as it may seem.I was wondering if you could elaborate some on what you mean. On a scale of one to ten, with ten being the most difficult, how difficult of a task would you say it is to create this as it seems you have some experience doing this in the past and this will be my first attempt, so I would like to know what I'm getting into before I start. >From the Microsoft article on producing MSI installers, https://msdn.microsoft.com/en-us/library/aa266427(v=vs.60).aspx#vehowbuildinginstallerpackagefileanchor1, it seems fairly simple as long as you have Visual Studio. Is there something I'm not seeing or understanding in the process? Again, if you know of any references that might help educate me or direct me through the process, these would be helpful. I already have a couple strategies I'm thinking of to do this but I would like to see what someone with some experience has to say regarding the issue. -David Gentry On Thu, Aug 10, 2017 at 2:40 PM, Steve Dower <rep...@bugs.python.org> wrote: > > Steve Dower added the comment: > > > when we changed installers was that when we also fixed the > security/permissions problems with the install dir > > Yes, but the permissions issue here isn't the install directory - it is > probably the TEMP directory or some other system restriction. It's > basically impossible to tell from the logs, and I don't even know where to > start asking for configuration settings to see what may be wrong. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue31148> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31148> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com