[MacPorts] #38539: py-oursql: upgrade to 0.9.3.1
MacPorts
noreply at macports.org
Sat Aug 31 02:52:03 PDT 2013
#38539: py-oursql: upgrade to 0.9.3.1
------------------------------+------------------------
Reporter: robsonpeixoto@… | Owner: habnabit@…
Type: update | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: haspatch
Port: py-oursql |
------------------------------+------------------------
Comment (by s@…):
Replying to [comment:5 robsonpeixoto@…]:
> I'm unsure too.
>
> If you add the version variable on '''if {${python.version} >= 30} {'''
will work? Like
>
>
> {{{
> if {${python.version} >= 30} {
> version 0.9.3
> } else {
> version 0.9.3.1
> }
> }}}
Sorry for the slow response. I guess this works:
py-oursql @0.9.3.1 (python, devel, databases)[[BR]]
py26-oursql @0.9.3.1 (python, devel, databases)[[BR]]
py27-oursql @0.9.3.1 (python, devel, databases)[[BR]]
py31-oursql @0.9.3 (python, devel, databases)[[BR]]
py32-oursql @0.9.3 (python, devel, databases)[[BR]]
py33-oursql @0.9.3 (python, devel, databases)
It seems a little odd to have different versions.
It takes a little more effort to get this to work with Python 3.3. Namely,
the oursqlx/oursql.c needs to be regenerated using Cython. I've got a new
Portfile and the appropriate patch ready to go once #39510 lands.
Should I attach the patches to this ticket, to #39510, or create a new
ticket? Should the patches for the new version be based on what's
currently there or on #39510?
--
Ticket URL: <https://trac.macports.org/ticket/38539#comment:6>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list