From seeking.that at gmail.com Wed Jan 1 09:38:24 2020 From: seeking.that at gmail.com (Seeking That) Date: Wed, 1 Jan 2020 06:38:24 -0800 Subject: [Pandas-dev] pandas tz conversion issue Message-ID: Hi python pandas bdate_range tz_convert() seems to have problems as it prints the information incorrectly. Please clarity. The python script and the output is shown below: Two issues that can be highlighted here are: 1) Setting the timezone correctly to US/Pacific prints the dates correctly. But the conversion causes the date calculations to be incorrect. 2. Minor issue just related to display. Though the API hasn't changed, the last call has more information hh-mm-ss-xx-xx which is not there for the rest of the calls with same format signature. Thanks SK import pandas as pd c5 = pd.bdate_range(start='1/1/2018', end = '1/31/2018') print(c5) c5 = c5.tz_localize('UTC') print(c5) c5 = c5.tz_convert('US/Pacific') print(c5) c6 = pd.bdate_range(start='1/1/2018', end = '1/31/2018') print(c6) c6 = c6.tz_localize('US/Pacific') print(c6) ------ DatetimeIndex(['2018-01-01', '2018-01-02', '2018-01-03', '2018-01-04', '2018-01-05', '2018-01-08', '2018-01-09', '2018-01-10', '2018-01-11', '2018-01-12', '2018-01-15', '2018-01-16', '2018-01-17', '2018-01-18', '2018-01-19', '2018-01-22', '2018-01-23', '2018-01-24', '2018-01-25', '2018-01-26', '2018-01-29', '2018-01-30', '2018-01-31'], dtype='datetime64[ns]', freq='B') DatetimeIndex(['2018-01-01', '2018-01-02', '2018-01-03', '2018-01-04', '2018-01-05', '2018-01-08', '2018-01-09', '2018-01-10', '2018-01-11', '2018-01-12', '2018-01-15', '2018-01-16', '2018-01-17', '2018-01-18', '2018-01-19', '2018-01-22', '2018-01-23', '2018-01-24', '2018-01-25', '2018-01-26', '2018-01-29', '2018-01-30', '2018-01-31'], dtype='datetime64[ns, UTC]', freq='B') DatetimeIndex(['2017-12-31', '2018-01-01', '2018-01-02', '2018-01-03', '2018-01-04', '2018-01-07', '2018-01-08', '2018-01-09', '2018-01-10', '2018-01-11', '2018-01-14', '2018-01-15', '2018-01-16', '2018-01-17', '2018-01-18', '2018-01-21', '2018-01-22', '2018-01-23', '2018-01-24', '2018-01-25', '2018-01-28', '2018-01-29', '2018-01-30'], dtype='datetime64[ns, US/Pacific]', freq='B') DatetimeIndex(['2018-01-01', '2018-01-02', '2018-01-03', '2018-01-04', '2018-01-05', '2018-01-08', '2018-01-09', '2018-01-10', '2018-01-11', '2018-01-12', '2018-01-15', '2018-01-16', '2018-01-17', '2018-01-18', '2018-01-19', '2018-01-22', '2018-01-23', '2018-01-24', '2018-01-25', '2018-01-26', '2018-01-29', '2018-01-30', '2018-01-31'], dtype='datetime64[ns]', freq='B') DatetimeIndex(['2018-01-01 00:00:00-08:00', '2018-01-02 00:00:00-08:00', '2018-01-03 00:00:00-08:00', '2018-01-04 00:00:00-08:00', '2018-01-05 00:00:00-08:00', '2018-01-08 00:00:00-08:00', '2018-01-09 00:00:00-08:00', '2018-01-10 00:00:00-08:00', '2018-01-11 00:00:00-08:00', '2018-01-12 00:00:00-08:00', '2018-01-15 00:00:00-08:00', '2018-01-16 00:00:00-08:00', '2018-01-17 00:00:00-08:00', '2018-01-18 00:00:00-08:00', '2018-01-19 00:00:00-08:00', '2018-01-22 00:00:00-08:00', '2018-01-23 00:00:00-08:00', '2018-01-24 00:00:00-08:00', '2018-01-25 00:00:00-08:00', '2018-01-26 00:00:00-08:00', '2018-01-29 00:00:00-08:00', '2018-01-30 00:00:00-08:00', '2018-01-31 00:00:00-08:00'], dtype='datetime64[ns, US/Pacific]', freq='B') -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom.augspurger88 at gmail.com Tue Jan 7 14:26:11 2020 From: tom.augspurger88 at gmail.com (Tom Augspurger) Date: Tue, 7 Jan 2020 13:26:11 -0600 Subject: [Pandas-dev] Monthly Dev Meeting Message-ID: Hi all, The next monthly dev call is tomorrow (Wednesday, January 8th) at 18:00 UTC. We invite all to come. https://dev.pandas.io/docs/development/meeting.html We'll use this Zoom link: https://zoom.us/j/942410248 The agenda is at https://docs.google.com/document/d/1tGbTiYORHiSPgVMXawiweGJlBw5dOkVJLY-licoBmBU/edit?usp=sharing if you have topics to discuss. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorisvandenbossche at gmail.com Thu Jan 9 07:15:42 2020 From: jorisvandenbossche at gmail.com (Joris Van den Bossche) Date: Thu, 9 Jan 2020 13:15:42 +0100 Subject: [Pandas-dev] Fwd: [NumFOCUS Projects] Job: Open Source Developer Advocate In-Reply-To: References: Message-ID: ---------- Forwarded message --------- From: Nicole Foster Date: Wed, 8 Jan 2020 at 22:25 Subject: [NumFOCUS Projects] Job: Open Source Developer Advocate To: Fiscally Sponsored Project Representatives , Affiliated Projects Hi Everyone, We recently posted an ad for an Open Source Developer Advocate position with NumFOCUS. We would be thrilled to have a member of our community work with us here at NumFOCUS so we ask that you please share this job posting with anyone you know that might be a good fit. Please feel free to reach out if you have any questions. Thank you for your time and consideration as we work to fill this role. Best, -- Nicole Foster Executive Operations Administrator, NumFOCUS nicole at numfocus.org 512-831-2870 -- You received this message because you are subscribed to the Google Groups "Fiscally Sponsored Project Representatives" group. To unsubscribe from this group and stop receiving emails from it, send an email to projects+unsubscribe at numfocus.org. To view this discussion on the web visit https://groups.google.com/a/numfocus.org/d/msgid/projects/CAJLwxPF5ezbsAEWk4pqWPXk6F7SAU8cESm6GrXpy1ak6%3DBzt6w%40mail.gmail.com . -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom.augspurger88 at gmail.com Thu Jan 9 14:04:05 2020 From: tom.augspurger88 at gmail.com (Tom Augspurger) Date: Thu, 9 Jan 2020 13:04:05 -0600 Subject: [Pandas-dev] Merging after the RC Message-ID: On the call yesterday, we discussed branching strategies after we tag the RC. We're trying to keep the workflow roughly what it was before (with some terms changed). Briefly 1. Don't merge API-breaking changes to master. Those will need to wait until the next *major* release (2.0.0) and we aren't ready to branch that yet. 2. We'll treat master as the next *minor* release. So performance improvements, refactors, bug fixes, new features, will all be merged to master, as long as they aren't API breaking changes. 3. Bugfixes fixing regressions that should be backported should be assigned the milestone for the next bugfix release (e.g. 1.0.0, 1.0.1, 1.1.1). Use your best judgement when deciding whether something is a bugfix or breaking API. And it may have been mentioned briefly, but what are people's thoughts on what should be merged during the RC? IMO, it should be just PRs fixing regressions from 0.25.x. Everything else can just go in the next minor release, and needn't be backported. I'm hoping to tag the RC later today. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom.augspurger88 at gmail.com Fri Jan 10 10:58:04 2020 From: tom.augspurger88 at gmail.com (Tom Augspurger) Date: Fri, 10 Jan 2020 09:58:04 -0600 Subject: [Pandas-dev] ANN: Pandas 1.0.0rc0 released Message-ID: Hi all, I'm pleased to announce that pandas 1.0.0rc0 is now available. This is the first release candidate for 1.0.0. If all goes well, we'll release pandas 1.0.0 in about two weeks. Highlights include - A new scalar for missing values - Dedicated extension types for string and nullable boolean data - Using Numba in rolling.apply - A redesigned website and documentation theme See the whatsnew for a list of all the changes. The release can be installed from PyPI python -m pip install --upgrade --pre pandas==1.0.0rc0 Or from conda-forge conda create -n pandas=1.0.0rc0 -c conda-forge/label/rc -c conda-forge pandas==1.0.0rc0 Please report any issues with the release candidate on the pandas issue tracker . -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsaxton at pm.me Sun Jan 12 21:50:37 2020 From: dsaxton at pm.me (Daniel Saxton) Date: Mon, 13 Jan 2020 02:50:37 +0000 Subject: [Pandas-dev] Question about pd.NA Message-ID: Hi all, First off just wanted to say the new pd.NA value and enhancements to Boolean operations are incredibly cool new features, so congratulations on that. One minor question: (-1) ** pd.NA is always -1 as implemented, but should this also be pd.NA since the "unknown" NA value could be even or odd (or possibly some weird non-integer value)? Thanks, Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jorisvandenbossche at gmail.com Mon Jan 13 04:31:11 2020 From: jorisvandenbossche at gmail.com (Joris Van den Bossche) Date: Mon, 13 Jan 2020 10:31:11 +0100 Subject: [Pandas-dev] Question about pd.NA In-Reply-To: References: Message-ID: Hi Daniel, Thanks for the feedback! Good question, and I think you are right. It's easy to get the wrong idea about the behaviour due to the order of operations: In [21]: -1 ** 2 Out[21]: -1 In [22]: -1 ** 3 Out[22]: -1 where this is seemingly all giving the same result. But doing it correctly: In [55]: (-1) ** 2 Out[55]: 1 In [56]: (-1) ** 3 Out[56]: -1 In [57]: (-1) ** 2.5 Out[57]: (3.061616997868383e-16+1j) you are indeed right that this is not always -1. Also numpy shows this: In [58]: (-1) ** np.array([2, 3, 2.5]) /home/joris/miniconda3/envs/dev/bin/ipython:1: RuntimeWarning: invalid value encountered in power #!/home/joris/miniconda3/envs/dev/bin/python Out[58]: array([ 1., -1., nan]) I opened https://github.com/pandas-dev/pandas/issues/30956 for this. We should fix this for 1.0.0 (PRs always welcome!). It should be a relatively easy fix in removing the special case for -1 (and only leaving it for 1). Best, Joris On Mon, 13 Jan 2020 at 04:02, Daniel Saxton via Pandas-dev < pandas-dev at python.org> wrote: > Hi all, > > First off just wanted to say the new pd.NA value and enhancements to > Boolean operations are incredibly cool new features, so congratulations on > that. One minor question: (-1) ** pd.NA is always -1 as implemented, but > should this also be pd.NA since the "unknown" NA value could be even or odd > (or possibly some weird non-integer value)? > > Thanks, > Daniel > > > _______________________________________________ > 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: From jorisvandenbossche at gmail.com Mon Jan 13 04:54:38 2020 From: jorisvandenbossche at gmail.com (Joris Van den Bossche) Date: Mon, 13 Jan 2020 10:54:38 +0100 Subject: [Pandas-dev] Merging after the RC In-Reply-To: References: Message-ID: On Thu, 9 Jan 2020 at 20:04, Tom Augspurger wrote: > On the call yesterday, we discussed branching strategies after we tag the > RC. > We're trying to keep the workflow roughly what it was before (with some > terms > changed). Briefly > > 1. Don't merge API-breaking changes to master. Those will need to wait > until > the next *major* release (2.0.0) and we aren't ready to branch that yet. > 2. We'll treat master as the next *minor* release. So performance > improvements, > refactors, bug fixes, new features, will all be merged to master, as > long as > they aren't API breaking changes. > 3. Bugfixes fixing regressions that should be backported should be > assigned the > milestone for the next bugfix release (e.g. 1.0.0, 1.0.1, 1.1.1). > > Use your best judgement when deciding whether something is a bugfix or > breaking API. > > And it may have been mentioned briefly, but what are people's thoughts on > what > should be merged during the RC? IMO, it should be just PRs fixing > regressions > from 0.25.x. Everything else can just go in the next minor release, and > needn't > be backported. > I agree we should keep it mainly limited to fixing regressions. In addition to that, I think we can also do: - Non-regression fixes to *new* functionality (bugs in new things, or feedback on new API) - Remember that CI fixes often need to be backported as well, as we want to keep CI green on the 1.0.x branch as well for now. > > I'm hoping to tag the RC later today. > > Tom > _______________________________________________ > 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: From tom.augspurger88 at gmail.com Thu Jan 30 07:10:20 2020 From: tom.augspurger88 at gmail.com (Tom Augspurger) Date: Thu, 30 Jan 2020 06:10:20 -0600 Subject: [Pandas-dev] ANN: Pandas 1.0.0 Message-ID: Hi all, I'm pleased to announce the release of pandas 1.0.0. This is a major release from 0.25.3, and includes a number of API changes, new features, enhancements, and performance improvements along with a large number of bug fixes. Highlights include - A redesigned website and documentation theme - Using Numba in rolling.apply - A new DataFrame method for converting to Markdown - A new scalar for missing values - Dedicated extension types for string and nullable boolean data See the whatsnew for a list of all the changes. We've also written a blog post reflecting on the journey to 1.0 and what it means for our project. The release can be installed from PyPI python -m pip install --upgrade pandas Or with conda from the defaults or conda-forge channels. conda install pandas Thanks to the more than 300 contributors to this release. Please report any issues with the release on the pandas issue tracker. Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From wesmckinn at gmail.com Thu Jan 30 11:21:04 2020 From: wesmckinn at gmail.com (Wes McKinney) Date: Thu, 30 Jan 2020 10:21:04 -0600 Subject: [Pandas-dev] ANN: Pandas 1.0.0 In-Reply-To: References: Message-ID: Congrats to the maintainers and all the contributors! On Thu, Jan 30, 2020 at 6:10 AM Tom Augspurger wrote: > > Hi all, > > I'm pleased to announce the release of pandas 1.0.0. This is a major release from 0.25.3, and includes a number of API changes, new features, enhancements, and performance improvements along with a large number of bug fixes. > > Highlights include > > A redesigned website and documentation theme > Using Numba in rolling.apply > A new DataFrame method for converting to Markdown > A new scalar for missing values > Dedicated extension types for string and > nullable boolean data > > See the whatsnew for a list of all the changes. We've also written a blog post reflecting on the journey to 1.0 and what it means for our project. > > The release can be installed from PyPI > > python -m pip install --upgrade pandas > > Or with conda from the defaults or conda-forge channels. > > conda install pandas > > Thanks to the more than 300 contributors to this release. Please report any issues with the release on the pandas issue tracker. > > Tom > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > https://mail.python.org/mailman/listinfo/pandas-dev