Re: [PyDB2-discuss] New release on sourceforge?

[Dan S. <de...@gm...>]

Attached is a small patch for setup.py to hopefully improve the build
experience on both Windows and on UNIX (DB2DIR is the environment
variable exported by ~/sqllib/db2profile, and because DB2 allows you
to install into any directory on Windows I thought it made sense to
support alternate install directories using the same mechanism).

Now to actually put the code through its paces :)

Dan

On 3/8/05, ??? <yo...@li...> wrote:
> =20
> Oh, I've forgot to fix the notorious timestamp bug about the fraction par=
t=20
> :-(=20
>  =20
> I think I've fixed the bug right now and uploaded to the same place.=20
> You can get by anonymous ftp at
> people.linuxkorea.co.kr/pub/DB2/src.=20
> The filename is the same as the previous one.=20
>  =20
> Can you please check this for me?=20
>  =20
> Thanks.=20
>  =20
> FYI, I've include the ugly part related to timestamp string building:=20
>  =20
>         case SQL_C_TYPE_TIMESTAMP:
>                 timestampSt =3D *(TIMESTAMP_STRUCT *)(buf);
>                 size =3D 26 + 1;
>                 tempStr =3D (char *) MY_MALLOC(size);
>                 memset(tempStr, 0, size);
>                 sprintf(tempStr,
>                               =20
> "%04d-%02d-%02d-%02d.%02d.%02d.",
>                                 timestampSt.year,
>                                 timestampSt.month,
>                                 timestampSt.day,
>                                 timestampSt.hour,
>                                 timestampSt.minute,
>                                 timestampSt.second);=20
>  =20
>                 /* ffffff part */=20
>  =20
>                 fractionPart =3D (char *)MY_MALLOC(size);
>                 memset(fractionPart, 0, size);
>                 sprintf(fractionPart, "%09d", (unsigned
> int)timestampSt.fraction);
>                 fractionPart[6] =3D '\0';
>                 strcat(tempStr, fractionPart);=20
>  =20
>                 /* val =3D
> PyString_FromStringAndSize(tempStr, 26); */ /* paranoid? */
>                 val =3D PyString_FromString(tempStr);=20
>  =20
>                 MY_FREE(tempStr);
>                 MY_FREE(fractionPart);=20
>  =20
>                 break;
> =20
> =20
> ----- Original Message -----=20
> From: Jaco Smuts=20
> To: ???=20
> Cc: Dan Scott ; pyd...@li... ;
> pyd...@li...=20
> Sent: Wednesday, March 09, 2005 1:30 AM=20
> Subject: Re: [PyDB2-discuss] New release on sourceforge?=20
>=20
>=20
> I know little about C, but I'll gladly test it using some db2 scripts I u=
se
> at work=20
>=20
> does this codebase address the timestamp issue (there is a patch for it) =
?=20
>=20
>=20
>=20
>=20
> =20
>  "???" <yo...@li...>=20
> Sent by: pyd...@li...=20
>=20
> 2005/03/08 02:29 PM=20
> =20
> To "Dan Scott" <de...@gm...>,
> <pyd...@li...>=20
> =20
> cc=20
> =20
> Subject Re: [PyDB2-discuss] New release on sourceforge?
> =20
> =20
>=20
>=20
>=20
> Hi~ everyone,
>=20
> I've just refactored the module and uploaded to
> ftp://people.linuxkorea.co.kr/pub/DB2/src.
> Can you please review the source code?
>=20
> I'm sure that this version is much better than the previous one.
> It includes unittest code now.
>=20
> Sooner or later, I would like to upload this version to sf.net.
>=20
> ----- Original Message -----=20
> From: "Dan Scott" <de...@gm...>
> To: <pyd...@li...>
> Sent: Tuesday, February 01, 2005 6:20 AM
> Subject: Re: [PyDB2-discuss] New release on sourceforge?
>=20
>=20
> > On Mon, 31 Jan 2005 17:12:00 +0900, ??? <yo...@li...> wrote:
> >> Hi Dan,
> >>=20
> >> ----- Original Message -----
> >> From: "Dan Scott" <de...@gm...>
> >> To: <pyd...@li...>
> >> Sent: Sunday, January 30, 2005 5:24 AM
> >> Subject: Re: [PyDB2-discuss] New release on sourceforge?
> >>=20
> >>=20
> >> > Hi Yuval, Man-Yong:
> >> >
> >> > Any chance of that 1.0 release happening?
> >>=20
> >> Yuval, I want you to release 1.0.  In fact, I don't know how to releas=
e a
> new version in sf.net.
> >=20
> > Yuval, when you create the release, let me know and I'll update the
> > Python Package Index entry for the project.
> >=20
> >> > Also, it would be a really nice follow-up if Man-Yong could produce
> >> > the win32 binaries for the relatively recent Python 2.4 release.
> >>=20
> >> Sure.
> >=20
> > Excellent!
> >=20
> >> > When you start developing the 1.1 branch, would you consider
> >> > instituting a basic Contributor License Agreement (CLA) like Eclipse
> >> > and Apache do? The CLA is a legal process that asks would-be
> >> > contributors & the contributors' employers to sign off on a form
> >> > stating that the code they are contributing is rightfully theirs to
> >> > contribute -- basically a way of avoiding any contributions from sha=
dy
> >> > sources.
> >> >
> >> > My employer is a bit wary of projects that don't hava a CLA process,
> >> > so I can't be too useful to the effort without it :( Unless you call
> >> > sending requests and little reminder notes to the mailing list
> >> > useful...
> >> >
> >> > Dan
> >>=20
> >> Of course!
> >=20
> > That's great! For further information on the Contributor Licensing
> > Agreement (Python itself adopted a CLA process earlier this month) you
> > can look at http://www.python.org/psf/contrib.html
> >=20
> > This is really exciting; with these steps in place I think this
> > project will really take off and become more active again.