From jreback at yahoo.com  Thu May  8 23:10:23 2014
From: jreback at yahoo.com (Jeff Reback)
Date: Thu, 8 May 2014 17:10:23 -0400
Subject: [Pandas-dev] pandas release schedule
In-Reply-To: <8A5BBE2F-3AED-4133-B25E-9417C357D329@yahoo.com>
References: <1396542233.92956.YahooMailNeo@web142706.mail.bf1.yahoo.com>
 <CALQtMBaEAtjfQ=AnFvAaNmVwjycktB1RSBOy1qz5GKfZCs+A=w@mail.gmail.com>
 <8A5BBE2F-3AED-4133-B25E-9417C357D329@yahoo.com>
Message-ID: <AEA8BFFB-B691-4EA2-B149-EB420843EF62@yahoo.com>

ok

let's see if can get most of the remaining non doc issues by middle of next week

I'll plan on cutting a rc1 next Friday/sat (16th)

any objections?

Jeff


> On Apr 8, 2014, at 5:29 PM, Jeff Reback <jreback at yahoo.com> wrote:
> 
> I think sending out a RC say 1st week of May is prob reasonable. So let's see what can get done in sql space by then. When you are satisfied with the sql progress, just move anything in the sql issues to the 0.15 issue.
> 
> can then target a release a week or so after that.
> 
> if anyone wants to try to get anything else in but needs time speak up!
> 
> Jeff
> 
> 
>> On Apr 4, 2014, at 8:33 AM, Joris Van den Bossche <jorisvandenbossche at gmail.com> wrote:
>> 
>> Sounds good to me. 
>> 
>> - Do we also target an earlier date to get a RC out? Or set a target date after which only bug fixes / doc improvements go in?
>> 
>> - Are there things we would really want to get in? (and so should get some focus at the moment)
>>     - certainly the SQL still needs some work (#6296)
>>     - other PR/issues?
>> 
>> 
>> Regards,
>> Joris
>> 
>>     
>> 
>> 
>> 2014-04-03 18:23 GMT+02:00 Jeff Reback <jreback at yahoo.com>:
>>> Hey,
>>> 
>>> Thinking that would be nice to release 0.14.0 in mid-late May, depending on how
>>> much of the SQL stuff needs to go in.
>>> 
>>> Then 0.14.1 if necessary maybe 1 month later.
>>> 
>>> Any thoughts?
>>> 
>>> 
>>> 
>>>  Jeff
>>> 
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
>> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140508/16d8c165/attachment.html>

From cpcloud at gmail.com  Fri May  9 00:59:47 2014
From: cpcloud at gmail.com (Phillip Cloud)
Date: Thu, 8 May 2014 18:59:47 -0400
Subject: [Pandas-dev] pandas release schedule
In-Reply-To: <AEA8BFFB-B691-4EA2-B149-EB420843EF62@yahoo.com>
References: <1396542233.92956.YahooMailNeo@web142706.mail.bf1.yahoo.com>
 <CALQtMBaEAtjfQ=AnFvAaNmVwjycktB1RSBOy1qz5GKfZCs+A=w@mail.gmail.com>
 <8A5BBE2F-3AED-4133-B25E-9417C357D329@yahoo.com>
 <AEA8BFFB-B691-4EA2-B149-EB420843EF62@yahoo.com>
Message-ID: <CAKRVfm7vKLJjBL6cijj0gn2G28zDxqTWoUALC=D0re3HjSUHzQ@mail.gmail.com>

Sounds good. If you need help with setting anything up for release let me
know.

On Thursday, May 8, 2014, Jeff Reback <jreback at yahoo.com.dmarc.invalid>
wrote:

> ok
>
> let's see if can get most of the remaining non doc issues by middle of
> next week
>
> I'll plan on cutting a rc1 next Friday/sat (16th)
>
> any objections?
>
> Jeff
>
>
> On Apr 8, 2014, at 5:29 PM, Jeff Reback <jreback at yahoo.com<javascript:_e(%7B%7D,'cvml','jreback at yahoo.com');>>
> wrote:
>
> I think sending out a RC say 1st week of May is prob reasonable. So let's
> see what can get done in sql space by then. When you are satisfied with the
> sql progress, just move anything in the sql issues to the 0.15 issue.
>
> can then target a release a week or so after that.
>
> if anyone wants to try to get anything else in but needs time speak up!
>
> Jeff
>
>
> On Apr 4, 2014, at 8:33 AM, Joris Van den Bossche <
> jorisvandenbossche at gmail.com<javascript:_e(%7B%7D,'cvml','jorisvandenbossche at gmail.com');>>
> wrote:
>
> Sounds good to me.
>
> - Do we also target an earlier date to get a RC out? Or set a target date
> after which only bug fixes / doc improvements go in?
>
> - Are there things we would really want to get in? (and so should get some
> focus at the moment)
>     - certainly the SQL still needs some work (#6296)
>     - other PR/issues?
>
>
> Regards,
> Joris
>
>
>
>
> 2014-04-03 18:23 GMT+02:00 Jeff Reback <jreback at yahoo.com<javascript:_e(%7B%7D,'cvml','jreback at yahoo.com');>
> >:
>
>> Hey,
>>
>> Thinking that would be nice to release 0.14.0 in mid-late May, depending
>> on how
>> much of the SQL stuff needs to go in.
>>
>> Then 0.14.1 if necessary maybe 1 month later.
>>
>> Any thoughts?
>>
>>
>>
>>  Jeff
>>
>> _______________________________________________
>> Pandas-dev mailing list
>> Pandas-dev at python.org<javascript:_e(%7B%7D,'cvml','Pandas-dev at python.org');>
>> https://mail.python.org/mailman/listinfo/pandas-dev
>>
>>
>

-- 

--
Best,
Phillip Cloud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140508/77f0b395/attachment.html>

From jorisvandenbossche at gmail.com  Mon May 12 16:36:27 2014
From: jorisvandenbossche at gmail.com (Joris Van den Bossche)
Date: Mon, 12 May 2014 16:36:27 +0200
Subject: [Pandas-dev] pandas release schedule
In-Reply-To: <CAKRVfm7vKLJjBL6cijj0gn2G28zDxqTWoUALC=D0re3HjSUHzQ@mail.gmail.com>
References: <1396542233.92956.YahooMailNeo@web142706.mail.bf1.yahoo.com>
 <CALQtMBaEAtjfQ=AnFvAaNmVwjycktB1RSBOy1qz5GKfZCs+A=w@mail.gmail.com>
 <8A5BBE2F-3AED-4133-B25E-9417C357D329@yahoo.com>
 <AEA8BFFB-B691-4EA2-B149-EB420843EF62@yahoo.com>
 <CAKRVfm7vKLJjBL6cijj0gn2G28zDxqTWoUALC=D0re3HjSUHzQ@mail.gmail.com>
Message-ID: <CALQtMBbkVfP0pVXw_r1qLA5DaQB6uJFsDwt6XdVskGcbxu6r8w@mail.gmail.com>

Good for me. I will try to finish the last sql things release notes this or
tomorrow evening.


2014-05-09 0:59 GMT+02:00 Phillip Cloud <cpcloud at gmail.com>:

> Sounds good. If you need help with setting anything up for release let me
> know.
>
>
> On Thursday, May 8, 2014, Jeff Reback <jreback at yahoo.com.dmarc.invalid>
> wrote:
>
>> ok
>>
>> let's see if can get most of the remaining non doc issues by middle of
>> next week
>>
>> I'll plan on cutting a rc1 next Friday/sat (16th)
>>
>> any objections?
>>
>> Jeff
>>
>>
>> On Apr 8, 2014, at 5:29 PM, Jeff Reback <jreback at yahoo.com> wrote:
>>
>> I think sending out a RC say 1st week of May is prob reasonable. So let's
>> see what can get done in sql space by then. When you are satisfied with the
>> sql progress, just move anything in the sql issues to the 0.15 issue.
>>
>> can then target a release a week or so after that.
>>
>> if anyone wants to try to get anything else in but needs time speak up!
>>
>> Jeff
>>
>>
>> On Apr 4, 2014, at 8:33 AM, Joris Van den Bossche <
>> jorisvandenbossche at gmail.com> wrote:
>>
>> Sounds good to me.
>>
>> - Do we also target an earlier date to get a RC out? Or set a target date
>> after which only bug fixes / doc improvements go in?
>>
>> - Are there things we would really want to get in? (and so should get
>> some focus at the moment)
>>     - certainly the SQL still needs some work (#6296)
>>     - other PR/issues?
>>
>>
>> Regards,
>> Joris
>>
>>
>>
>>
>> 2014-04-03 18:23 GMT+02:00 Jeff Reback <jreback at yahoo.com>:
>>
>>> Hey,
>>>
>>> Thinking that would be nice to release 0.14.0 in mid-late May, depending
>>> on how
>>> much of the SQL stuff needs to go in.
>>>
>>> Then 0.14.1 if necessary maybe 1 month later.
>>>
>>> Any thoughts?
>>>
>>>
>>>
>>>  Jeff
>>>
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
>>>
>>>
>>
>
> --
>
> --
> Best,
> Phillip Cloud
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140512/36e8a069/attachment.html>

From jeffreback at gmail.com  Sat May 17 13:22:00 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Sat, 17 May 2014 07:22:00 -0400
Subject: [Pandas-dev] ANN: Pandas 0.14.0 Release Candidate 1
Message-ID: <CAHMnJKh-L26x=-3c6pPoSnqmb7fAujSH=hGQ6f-V=On9FLXQTw@mail.gmail.com>

Hi,

I'm pleased to announce the availability of the first release candidate of
Pandas 0.14.0.
Please try this RC and report any issues here: Pandas
Issues<https://github.com/pydata/pandas/issues>
We will be releasing officially in about 2 weeks or so.

This is a major release from 0.13.1 and includes a small number of API
changes, several new features, enhancements, and
performance improvements along with a large number of bug fixes.

Highlights include:

   - Officially support Python 3.4
   - SQL interfaces updated to use sqlalchemy,
   - Display interface changes
   - MultiIndexing Using Slicers
   - Ability to join a singly-indexed DataFrame with a multi-indexed
   DataFrame
   - More consistency in groupby results and more flexible groupby
   specifications
   - Holiday calendars are now supported in CustomBusinessDay
   - Several improvements in plotting functions, including: hexbin, area
   and pie plots.
   - Performance doc section on I/O operations

Since there are some significant changes in the default way DataFrames are
displayed. I have put
up a comment issue looking for some feedback
here<https://github.com/pydata/pandas/issues/7146>

Here are the full whatsnew and documentation links:

v0.14.0 Whatsnew<http://pandas-docs.github.io/pandas-docs-travis/whatsnew.html>

v0.14.0 Documentation Page<http://pandas-docs.github.io/pandas-docs-travis/>

Source tarballs, and windows builds are available here:

Pandas v0.14rc1 Release <https://github.com/pydata/pandas/releases>

A big thank you to everyone who contributed to this release!

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140517/7df8fe5a/attachment.html>

From wesmckinn at gmail.com  Sun May 18 05:59:43 2014
From: wesmckinn at gmail.com (Wes McKinney)
Date: Sat, 17 May 2014 20:59:43 -0700
Subject: [Pandas-dev] [pydata] Re: ANN: Pandas 0.14.0 Release Candidate 1
In-Reply-To: <daaee35f-d1e5-4791-8de8-9ca767892e0e@googlegroups.com>
References: <CAHMnJKh-L26x=-3c6pPoSnqmb7fAujSH=hGQ6f-V=On9FLXQTw@mail.gmail.com>
 <daaee35f-d1e5-4791-8de8-9ca767892e0e@googlegroups.com>
Message-ID: <CAJPUwMBO2Qfrq516vvYrWdLrG_fRbcaaEdRP_JYEgycXLhLPtQ@mail.gmail.com>

On Sat, May 17, 2014 at 8:58 PM, Matthew Brett <matthew.brett at gmail.com> wrote:
> Hi,
>
>
> On Saturday, May 17, 2014 4:22:00 AM UTC-7, Jeff wrote:
>>
>> Hi,
>>
>> I'm pleased to announce the availability of the first release candidate of
>> Pandas 0.14.0.
>> Please try this RC and report any issues here: Pandas Issues
>> We will be releasing officially in about 2 weeks or so.
>>
>> This is a major release from 0.13.1 and includes a small number of API
>> changes, several new features, enhancements, and
>> performance improvements along with a large number of bug fixes.
>>
>
> I built some OSX wheels and put them up in this directory:
>
>  https://nipy.bic.berkeley.edu/scipy_installers/
>
> I installed the wheel and tested on a bare 10.6 machine via our buildbot:
>
> http://nipy.bic.berkeley.edu/builders/scipy-stack-2.7.6-wheel-pre/builds/1/steps/shell_16/logs/stdio
> http://nipy.bic.berkeley.edu/builders/scipy-stack-3.3.5-wheel-pre/builds/0/steps/shell_16/logs/stdio
> http://nipy.bic.berkeley.edu/builders/scipy-stack-3.4.0-wheel-pre/builds/0/steps/shell_16/logs/stdio
>
> Tests were clean apart from this Python 3 bug which Christoph Gohlke already
> found and fixed:
>
> https://github.com/pydata/pandas/pull/7148
>
> If anyone has time to test these, I would be grateful:
>
> pip install -U pip
> pip install --pre -f https://nipy.bic.berkeley.edu/scipy_installers pandas
>
> Cheers,
>
> Matthew
>
> --
> You received this message because you are subscribed to the Google Groups
> "PyData" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pydata+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Thanks Jeff and the team for continuing to carry the torch. Very exciting.

- Wes

From jorisvandenbossche at gmail.com  Tue May 27 16:35:16 2014
From: jorisvandenbossche at gmail.com (Joris Van den Bossche)
Date: Tue, 27 May 2014 16:35:16 +0200
Subject: [Pandas-dev] whatsnew vs release notes
Message-ID: <CALQtMBboX8fdxL+tsUS4aQOL_Sqnkyf+zZSfO6Vp-cAtRO+=EA@mail.gmail.com>

Hi list,

A question about the possible duplicative nature of the release notes and
whatsnew page. I know this has been discussed earlier (eg
https://github.com/pydata/pandas/issues/4389), and the conclusion there was
"*Release notes has every change, with a small description and issue
reference. Whatsnew has 'big' changes, and examples (if necessary), and is
the 'announcement' email, while release notes is the reference doc*". This
is also stated on the wiki (
https://github.com/pydata/pandas/wiki/Documenting-new-features-and-bug-fixes
).

But looking at the actual pages of the upcoming 0.14 release, I think
almost everything in release notes is also in whatsnew, apart from the
(long) bug fixes section, and that whatsnew has examples while release
notes has not, and whatsnew is structured a bit more by topic.
In addition, the whatsnew file has also become much to large to be
appropriate as the 'announcement' but has become the reference doc in my
regard.

Seeing this duplication (and also a lot of PRs that just add the same
sentence in both files), I was wondering if this is worth it. And if it
would not be better (less work for the contributor, and also for a user
looking at these pages on the website having both does not seem that
usefull) to just have one extensive page with the two merged. And then
before a release a summary with the most notable parts of that can be made
to use as announcement?

Regards,
Joris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140527/9aaeb39e/attachment.html>

From jeffreback at gmail.com  Tue May 27 22:44:45 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Tue, 27 May 2014 16:44:45 -0400
Subject: [Pandas-dev] whatsnew vs release notes
In-Reply-To: <CALQtMBboX8fdxL+tsUS4aQOL_Sqnkyf+zZSfO6Vp-cAtRO+=EA@mail.gmail.com>
References: <CALQtMBboX8fdxL+tsUS4aQOL_Sqnkyf+zZSfO6Vp-cAtRO+=EA@mail.gmail.com>
Message-ID: <44C2FCEA-A018-4BE8-A687-41919FDA1A70@gmail.com>

well we are just going to have a link to the whatsnew in the announcement; it's much too long to actually include it in the mail; though planning on including the highlites (at the top will be directly listed)

I think of whatsnew as all changes but with examples (as needed). the original idea behind release notes was that it was a list of issues fixed with very limited examples (or none)

I would be +1 in only using the whatsnew and then maybe have links back to the major sections from the release notes. (the reason for keeping the release notes is that people expect to see them as they are standard parts of a project). so going forward only have to edit whatsnew.

it just seems simpler to maintain a whatsnew for a particular version as a single file (as then no mistaking which section to put the notes in). 

I guess the reverse is in place now for the bug fixes (eg they live in release notes and ref from whatsnew)

> On May 27, 2014, at 10:35 AM, Joris Van den Bossche <jorisvandenbossche at gmail.com> wrote:
> 
> Hi list,
> 
> A question about the possible duplicative nature of the release notes and whatsnew page. I know this has been discussed earlier (eg https://github.com/pydata/pandas/issues/4389), and the conclusion there was "Release notes has every change, with a small description and issue reference. Whatsnew has 'big' changes, and examples (if necessary), and is the 'announcement' email, while release notes is the reference doc". This is also stated on the wiki (https://github.com/pydata/pandas/wiki/Documenting-new-features-and-bug-fixes).
> 
> But looking at the actual pages of the upcoming 0.14 release, I think almost everything in release notes is also in whatsnew, apart from the (long) bug fixes section, and that whatsnew has examples while release notes has not, and whatsnew is structured a bit more by topic.
> In addition, the whatsnew file has also become much to large to be appropriate as the 'announcement' but has become the reference doc in my regard.
> 
> Seeing this duplication (and also a lot of PRs that just add the same sentence in both files), I was wondering if this is worth it. And if it would not be better (less work for the contributor, and also for a user looking at these pages on the website having both does not seem that usefull) to just have one extensive page with the two merged. And then before a release a summary with the most notable parts of that can be made to use as announcement?
> 
> Regards,
> Joris
> 
> 
> 
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140527/aa9b6664/attachment.html>

From matthew.brett at gmail.com  Sun May 18 05:58:09 2014
From: matthew.brett at gmail.com (Matthew Brett)
Date: Sat, 17 May 2014 20:58:09 -0700 (PDT)
Subject: [Pandas-dev] ANN: Pandas 0.14.0 Release Candidate 1
In-Reply-To: <CAHMnJKh-L26x=-3c6pPoSnqmb7fAujSH=hGQ6f-V=On9FLXQTw@mail.gmail.com>
References: <CAHMnJKh-L26x=-3c6pPoSnqmb7fAujSH=hGQ6f-V=On9FLXQTw@mail.gmail.com>
Message-ID: <daaee35f-d1e5-4791-8de8-9ca767892e0e@googlegroups.com>

Hi,

On Saturday, May 17, 2014 4:22:00 AM UTC-7, Jeff wrote:
>
> Hi,
>
> I'm pleased to announce the availability of the first release candidate of 
> Pandas 0.14.0.
> Please try this RC and report any issues here: Pandas Issues<https://github.com/pydata/pandas/issues>
> We will be releasing officially in about 2 weeks or so.
>
> This is a major release from 0.13.1 and includes a small number of API 
> changes, several new features, enhancements, and 
> performance improvements along with a large number of bug fixes. 
>
>
I built some OSX wheels and put them up in this directory:

 https://nipy.bic.berkeley.edu/scipy_installers/

I installed the wheel and tested on a bare 10.6 machine via our buildbot:

http://nipy.bic.berkeley.edu/builders/scipy-stack-2.7.6-wheel-pre/builds/1/steps/shell_16/logs/stdio
http://nipy.bic.berkeley.edu/builders/scipy-stack-3.3.5-wheel-pre/builds/0/steps/shell_16/logs/stdio
http://nipy.bic.berkeley.edu/builders/scipy-stack-3.4.0-wheel-pre/builds/0/steps/shell_16/logs/stdio

Tests were clean apart from this Python 3 bug which Christoph Gohlke 
already found and fixed:

https://github.com/pydata/pandas/pull/7148

If anyone has time to test these, I would be grateful:

pip install -U pip
pip install --pre -f https://nipy.bic.berkeley.edu/scipy_installers pandas

Cheers,

Matthew

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140517/9a6ceeee/attachment.html>

From jeffreback at gmail.com  Fri May 30 14:10:46 2014
From: jeffreback at gmail.com (Jeff)
Date: Fri, 30 May 2014 05:10:46 -0700 (PDT)
Subject: [Pandas-dev] ANN: Pandas 0.14.0 Release Candidate 1
In-Reply-To: <daaee35f-d1e5-4791-8de8-9ca767892e0e@googlegroups.com>
References: <CAHMnJKh-L26x=-3c6pPoSnqmb7fAujSH=hGQ6f-V=On9FLXQTw@mail.gmail.com>
 <daaee35f-d1e5-4791-8de8-9ca767892e0e@googlegroups.com>
Message-ID: <e43f506b-d190-4d81-a1cb-e17c4e1ff264@googlegroups.com>


Matthew have posted the v0.14.0 final release, see here: 
https://github.com/pydata/pandas/releases
Not sure how you pickup the release for the mac wheels. I haven't updated 
PyPi yet as waiting for windows
binaries first. I'd like to put your wheels up there as well. Please lmk 
when I can download them (and lmk if you need anything
to build them).

Thanks!

Jeff

On Saturday, May 17, 2014 11:58:09 PM UTC-4, Matthew Brett wrote:
>
> Hi,
>
> On Saturday, May 17, 2014 4:22:00 AM UTC-7, Jeff wrote:
>>
>> Hi,
>>
>> I'm pleased to announce the availability of the first release candidate 
>> of Pandas 0.14.0.
>> Please try this RC and report any issues here: Pandas Issues 
>> <https://github.com/pydata/pandas/issues>
>> We will be releasing officially in about 2 weeks or so.
>>
>> This is a major release from 0.13.1 and includes a small number of API 
>> changes, several new features, enhancements, and 
>> performance improvements along with a large number of bug fixes. 
>>
>>
> I built some OSX wheels and put them up in this directory:
>
>  https://nipy.bic.berkeley.edu/scipy_installers/
>
> I installed the wheel and tested on a bare 10.6 machine via our buildbot:
>
>
> http://nipy.bic.berkeley.edu/builders/scipy-stack-2.7.6-wheel-pre/builds/1/steps/shell_16/logs/stdio
>
> http://nipy.bic.berkeley.edu/builders/scipy-stack-3.3.5-wheel-pre/builds/0/steps/shell_16/logs/stdio
>
> http://nipy.bic.berkeley.edu/builders/scipy-stack-3.4.0-wheel-pre/builds/0/steps/shell_16/logs/stdio
>
> Tests were clean apart from this Python 3 bug which Christoph Gohlke 
> already found and fixed:
>
> https://github.com/pydata/pandas/pull/7148
>
> If anyone has time to test these, I would be grateful:
>
> pip install -U pip
> pip install --pre -f https://nipy.bic.berkeley.edu/scipy_installers pandas
>
> Cheers,
>
> Matthew
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140530/8db98bbf/attachment.html>

From jeffreback at gmail.com  Fri May 30 18:08:00 2014
From: jeffreback at gmail.com (Jeff)
Date: Fri, 30 May 2014 09:08:00 -0700 (PDT)
Subject: [Pandas-dev] ANN: Pandas 0.14.0 Release Candidate 1
In-Reply-To: <c18e5c02-5f97-4983-9893-1a4654c03021@googlegroups.com>
References: <CAHMnJKh-L26x=-3c6pPoSnqmb7fAujSH=hGQ6f-V=On9FLXQTw@mail.gmail.com>
 <c18e5c02-5f97-4983-9893-1a4654c03021@googlegroups.com>
Message-ID: <803aab90-dd3c-4da4-8b25-11b503117a9a@googlegroups.com>

building on windows is a bit non-trivial (and really not recommended; you 
can try these builds here: http://www.lfd.uci.edu/~gohlke/pythonlibs/#pandas
for rc1 (0.14.0 is building shortly)

On Friday, May 30, 2014 11:59:52 AM UTC-4, klo uo wrote:
>
> On Windows with 64 bit Python:
>
> 1. `pip install -U pandas` (with MSVC) fails: 
> https://gist.githubusercontent.com/anonymous/826f23fbbf0aca077328/raw/082a932cffa0da06133703a274dcdc0b249ec04d/pip.log
>
> after downloading source:
>  
> 2. trying to build, by default with MSVC fails: 
> https://gist.githubusercontent.com/anonymous/3bf2bda7db706be6b9f7/raw/75f2d35360dca9925f9f6335be2394a2e43f99ae/msvc.log
>
> 3. trying to build with mingw fails: 
> https://gist.githubusercontent.com/anonymous/0c6dd00d072846cb4287/raw/490eb96a933ade2d3ef54304a987213eeaa971b0/mingw.log
>
>
> ...waiting for gohlke builds
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140530/a5c312e5/attachment.html>

From jeffreback at gmail.com  Fri May 30 19:44:47 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Fri, 30 May 2014 13:44:47 -0400
Subject: [Pandas-dev] ANN: Pandas 0.14.0 released
Message-ID: <CAHMnJKgKcJQx-0Bm+8eqLkxOuw4xQakXi1u8C_ttO_CMDxfK9g@mail.gmail.com>

Hello,

We are proud to announce v0.14.0 of pandas, a major release from 0.13.1.

This release includes a small number of API changes, several new features,
enhancements, and performance improvements along with a large number of bug
fixes.

This was 4 months of work with 1014 commits by 121 authors encompassing 757
issues.

We recommend that all users upgrade to this version.

*Highlights:*

   -   Officially support Python 3.4
   -   SQL interfaces updated to use sqlalchemy
   -   Display interface changes
   -   MultiIndexing Using Slicers
   -   Ability to join a singly-indexed DataFrame with a multi-indexed
   DataFrame
   -   More consistency in groupby results and more flexible groupby
   specifications
   -   Holiday calendars are now supported in CustomBusinessDay
   -   Several improvements in plotting functions, including: hexbin, area
   and pie plots
   -   Performance doc section on I/O operations

See a full description of Whatsnew for v0.14.0 here:
http://pandas.pydata.org/pandas-docs/stable/whatsnew.html


*What is it:*

*pandas* is a Python package providing fast, flexible, and expressive data
structures designed to make working with ?relational? or ?labeled? data both
easy and intuitive. It aims to be the fundamental high-level building block
for
doing practical, real world data analysis in Python. Additionally, it has
the
broader goal of becoming the most powerful and flexible open source data
analysis / manipulation tool available in any language.


Documentation:
http://pandas.pydata.org/pandas-docs/stable/

Source tarballs, windows binaries are available on PyPI:
https://pypi.python.org/pypi/pandas

windows binaries are courtesy of  Christoph Gohlke and are built on Numpy
1.8
macosx wheels will be available soon, courtesy of Matthew Brett

Please report any issues here:
https://github.com/pydata/pandas/issues


Thanks

The Pandas Development Team


Contributors to the 0.14.0 release

   - Acanthostega
   - Adam Marcus
   - agijsberts
   - akittredge
   - Alex Gaudio
   - Alex Rothberg
   - AllenDowney
   - Andrew Rosenfeld
   - Andy Hayden
   - ankostis
   - anomrake
   - Antoine Mazi?res
   - anton-d
   - bashtage
   - Benedikt Sauer
   - benjamin
   - Brad Buran
   - bwignall
   - cgohlke
   - chebee7i
   - Christopher Whelan
   - Clark Fitzgerald
   - clham
   - Dale Jung
   - Dan Allan
   - Dan Birken
   - danielballan
   - Daniel Waeber
   - David Jung
   - David Stephens
   - Douglas McNeil
   - DSM
   - Garrett Drapala
   - Gouthaman Balaraman
   - Guillaume Poulin
   - hshimizu77
   - hugo
   - immerrr
   - ischwabacher
   - Jacob Howard
   - Jacob Schaer
   - jaimefrio
   - Jason Sexauer
   - Jeff Reback
   - Jeffrey Starr
   - Jeff Tratner
   - John David Reaver
   - John McNamara
   - John W. O'Brien
   - Jonathan Chambers
   - Joris Van den Bossche
   - jreback
   - jsexauer
   - Julia Evans
   - J?lio
   - Katie Atkinson
   - kdiether
   - Kelsey Jordahl
   - Kevin Sheppard
   - K.-Michael Aye
   - Matthias Kuhn
   - Matt Wittmann
   - Max Grender-Jones
   - Michael E. Gruen
   - michaelws
   - mikebailey
   - Mike Kelly
   - Nipun Batra
   - Noah Spies
   - ojdo
   - onesandzeroes
   - Patrick O'Keeffe
   - phaebz
   - Phillip Cloud
   - Pietro Battiston
   - PKEuS
   - Randy Carnevale
   - ribonoous
   - Robert Gibboni
   - rockg
   - sinhrks
   - Skipper Seabold
   - SplashDance
   - Stephan Hoyer
   - Tim Cera
   - Tobias Brandt
   - Todd Jennings
   - TomAugspurger
   - Tom Augspurger
   - unutbu
   - westurner
   - Yaroslav Halchenko
   - y-p
   - zach powers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140530/02f088ef/attachment-0001.html>

From jorisvandenbossche at gmail.com  Sat May 31 15:10:16 2014
From: jorisvandenbossche at gmail.com (Joris Van den Bossche)
Date: Sat, 31 May 2014 15:10:16 +0200
Subject: [Pandas-dev] whatsnew vs release notes
In-Reply-To: <44C2FCEA-A018-4BE8-A687-41919FDA1A70@gmail.com>
References: <CALQtMBboX8fdxL+tsUS4aQOL_Sqnkyf+zZSfO6Vp-cAtRO+=EA@mail.gmail.com>
 <44C2FCEA-A018-4BE8-A687-41919FDA1A70@gmail.com>
Message-ID: <CALQtMBZD5S1q8gNMT5s3DfFMO2pAjSVJPONuB64xXD6MO+PSYg@mail.gmail.com>

So to summarize the changes in the workflow:

- in PR's, only add entries in the relevant whatsnew file (no longer also
in release.rst). So we have only one place where all documentation on
changes, enhancements and bug fixes are gathered
- the entry in release.rst will then only updated before the release as the
announcement with a summary of whatsnew (highlights), etc

I adapted the wiki (
https://github.com/pydata/pandas/wiki/Documenting-new-features-and-bug-fixes)
and contributing.md to reflect this.

Allright?

Joris


2014-05-27 22:44 GMT+02:00 Jeff Reback <jeffreback at gmail.com>:

> well we are just going to have a link to the whatsnew in the announcement;
> it's much too long to actually include it in the mail; though planning on
> including the highlites (at the top will be directly listed)
>
> I think of whatsnew as all changes but with examples (as needed). the
> original idea behind release notes was that it was a list of issues fixed
> with very limited examples (or none)
>
> I would be +1 in only using the whatsnew and then maybe have links back to
> the major sections from the release notes. (the reason for keeping the
> release notes is that people expect to see them as they are standard parts
> of a project). so going forward only have to edit whatsnew.
>
> it just seems simpler to maintain a whatsnew for a particular version as a
> single file (as then no mistaking which section to put the notes in).
>
> I guess the reverse is in place now for the bug fixes (eg they live in
> release notes and ref from whatsnew)
>
> On May 27, 2014, at 10:35 AM, Joris Van den Bossche <
> jorisvandenbossche at gmail.com> wrote:
>
> Hi list,
>
> A question about the possible duplicative nature of the release notes and
> whatsnew page. I know this has been discussed earlier (eg
> https://github.com/pydata/pandas/issues/4389), and the conclusion there
> was "*Release notes has every change, with a small description and issue
> reference. Whatsnew has 'big' changes, and examples (if necessary), and is
> the 'announcement' email, while release notes is the reference doc*".
> This is also stated on the wiki (
> https://github.com/pydata/pandas/wiki/Documenting-new-features-and-bug-fixes
> ).
>
> But looking at the actual pages of the upcoming 0.14 release, I think
> almost everything in release notes is also in whatsnew, apart from the
> (long) bug fixes section, and that whatsnew has examples while release
> notes has not, and whatsnew is structured a bit more by topic.
> In addition, the whatsnew file has also become much to large to be
> appropriate as the 'announcement' but has become the reference doc in my
> regard.
>
> Seeing this duplication (and also a lot of PRs that just add the same
> sentence in both files), I was wondering if this is worth it. And if it
> would not be better (less work for the contributor, and also for a user
> looking at these pages on the website having both does not seem that
> usefull) to just have one extensive page with the two merged. And then
> before a release a summary with the most notable parts of that can be made
> to use as announcement?
>
> Regards,
> Joris
>
>
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140531/dfac66cb/attachment.html>

From jeffreback at gmail.com  Sat May 31 15:12:45 2014
From: jeffreback at gmail.com (Jeff Reback)
Date: Sat, 31 May 2014 09:12:45 -0400
Subject: [Pandas-dev] whatsnew vs release notes
In-Reply-To: <CALQtMBZD5S1q8gNMT5s3DfFMO2pAjSVJPONuB64xXD6MO+PSYg@mail.gmail.com>
References: <CALQtMBboX8fdxL+tsUS4aQOL_Sqnkyf+zZSfO6Vp-cAtRO+=EA@mail.gmail.com>
 <44C2FCEA-A018-4BE8-A687-41919FDA1A70@gmail.com>
 <CALQtMBZD5S1q8gNMT5s3DfFMO2pAjSVJPONuB64xXD6MO+PSYg@mail.gmail.com>
Message-ID: <35681287-D480-4BFF-8FB3-82431265DECE@gmail.com>

perfect

thanks

> On May 31, 2014, at 9:10 AM, Joris Van den Bossche <jorisvandenbossche at gmail.com> wrote:
> 
> So to summarize the changes in the workflow:
> 
> - in PR's, only add entries in the relevant whatsnew file (no longer also in release.rst). So we have only one place where all documentation on changes, enhancements and bug fixes are gathered
> - the entry in release.rst will then only updated before the release as the announcement with a summary of whatsnew (highlights), etc
> 
> I adapted the wiki (https://github.com/pydata/pandas/wiki/Documenting-new-features-and-bug-fixes) and contributing.md to reflect this.
> 
> Allright?
> 
> Joris
> 
> 
> 2014-05-27 22:44 GMT+02:00 Jeff Reback <jeffreback at gmail.com>:
>> well we are just going to have a link to the whatsnew in the announcement; it's much too long to actually include it in the mail; though planning on including the highlites (at the top will be directly listed)
>> 
>> I think of whatsnew as all changes but with examples (as needed). the original idea behind release notes was that it was a list of issues fixed with very limited examples (or none)
>> 
>> I would be +1 in only using the whatsnew and then maybe have links back to the major sections from the release notes. (the reason for keeping the release notes is that people expect to see them as they are standard parts of a project). so going forward only have to edit whatsnew.
>> 
>> it just seems simpler to maintain a whatsnew for a particular version as a single file (as then no mistaking which section to put the notes in). 
>> 
>> I guess the reverse is in place now for the bug fixes (eg they live in release notes and ref from whatsnew)
>> 
>>> On May 27, 2014, at 10:35 AM, Joris Van den Bossche <jorisvandenbossche at gmail.com> wrote:
>>> 
>>> Hi list,
>>> 
>>> A question about the possible duplicative nature of the release notes and whatsnew page. I know this has been discussed earlier (eg https://github.com/pydata/pandas/issues/4389), and the conclusion there was "Release notes has every change, with a small description and issue reference. Whatsnew has 'big' changes, and examples (if necessary), and is the 'announcement' email, while release notes is the reference doc". This is also stated on the wiki (https://github.com/pydata/pandas/wiki/Documenting-new-features-and-bug-fixes).
>>> 
>>> But looking at the actual pages of the upcoming 0.14 release, I think almost everything in release notes is also in whatsnew, apart from the (long) bug fixes section, and that whatsnew has examples while release notes has not, and whatsnew is structured a bit more by topic.
>>> In addition, the whatsnew file has also become much to large to be appropriate as the 'announcement' but has become the reference doc in my regard.
>>> 
>>> Seeing this duplication (and also a lot of PRs that just add the same sentence in both files), I was wondering if this is worth it. And if it would not be better (less work for the contributor, and also for a user looking at these pages on the website having both does not seem that usefull) to just have one extensive page with the two merged. And then before a release a summary with the most notable parts of that can be made to use as announcement?
>>> 
>>> Regards,
>>> Joris
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Pandas-dev mailing list
>>> Pandas-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pandas-dev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20140531/4788e59c/attachment.html>