* ui_ux: => 0
* easy: => 0
Comment:
The issue with contrib.gis was somehow resolved since this ticket was
filed. The issue with the version number still exists.
[http://docs.python.org/distutils/setupscript.html#additional-meta-data
Distutils' docs] say:
> It is recommended that versions take the form major.minor[.patch[.sub]].
> Encoding the version information is an art in itself. Python packages
generally adhere to the version format major.minor[.patch][sub]. The major
number is 0 for initial, experimental releases of software. It is
incremented for releases that represent major milestones in a package. The
minor number is incremented when important new features are added to the
package. The patch number increments when bug-fix releases are made.
Additional trailing version information is sometimes used to indicate sub-
releases. These are “a1,a2,...,aN” (for alpha releases, where
functionality and API may change), “b1,b2,...,bN” (for beta releases,
which only fix bugs) and “pr1,pr2,...,prN” (for final pre-release release
testing). Some examples:
> 0.1.0
> the first, experimental release of a package
> 1.0.1a2
> the second alpha release of the first patch version of 1.0
--
Ticket URL: <https://code.djangoproject.com/ticket/11236#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by aaugustin):
I just uploaded a patch to #17491 to fix the format of the version number.
If that patch is committed, this ticket will probably be fixed.
--
Ticket URL: <https://code.djangoproject.com/ticket/11236#comment:4>
* status: new => closed
* resolution: => fixed
Comment:
In [17351]:
{{{
#!CommitTicketReference repository="" revision="17351"
Fixed #17491 -- Honored the version number format expected by distutils.
Fixed #11236 too.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/11236#comment:5>
* status: closed => reopened
* resolution: fixed =>
Comment:
Hum, ``python.exe setup.py bdist_msi`` still returns an error:
{{{
Writing build\bdist.win32\msi\Lib\site-packages\Django-1.4.0a1-py2.7.egg-
info
Traceback (most recent call last):
File "setup.py", line 98, in <module>
'Topic :: Software Development :: Libraries :: Python Modules',
File "C:\Python27\lib\distutils\core.py", line 152, in setup
dist.run_commands()
File "C:\Python27\lib\distutils\dist.py", line 953, in run_commands
self.run_command(cmd)
File "C:\Python27\lib\distutils\dist.py", line 972, in run_command
cmd_obj.run()
File "C:\Python27\lib\distutils\command\bdist_msi.py", line 255, in run
self.add_files()
File "C:\Python27\lib\distutils\command\bdist_msi.py", line 318, in
add_files
db.Commit()
_msi.MSIError: 1: 2263 2: _Tables 3: -2147287032
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/11236#comment:6>
* component: Uncategorized => Packaging
--
Ticket URL: <https://code.djangoproject.com/ticket/11236#comment:8>
* status: new => closed
* resolution: => wontfix
Comment:
I'm going to close this ticket given a lack of motivation of why we need
an MSI installer and the fact that we likely don't have anyone interested
in debugging that error. If someone is motivated and can fix it, feel free
to reopen.
--
Ticket URL: <https://code.djangoproject.com/ticket/11236#comment:9>