On Sat, Jan 18, 2014 at 3:38 PM, big stone <stonebi...@gmail.com> wrote:
And : > - python3.4 is still in beta also, not a released product. > - sadly first RC candidate 1 is February 9, 2014, 2 days earlier. > > Sqlite was so close now, *so close* to achieve this goal ... > Maybe you could get the Python devs to push back the RC deadline, assuming they feel it's important to get 3.8.3 into Python 3.4, or see if Dr. Hipp is willing to push the SQLite release up (assuming nothing goes wrong), or get them both to meet in the middle. Or, if it's expected that there will be no changes to SQLite between when it's tagged as a release candidate and when it's officially released (which can only be known close to that date), perhaps the Python devs will be willing to incorporate the SQLite release candidate into the Python release candidate, under the condition that the SQLite code not functionally change from release candidate to official release status. Or, perhaps a change can be made for a prospective 3.4.1, or if developer and end user demand is sufficient, perhaps the Python devs will agree to accommodate that. You can try, anyway. Joseph _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
