From eliswilson at hushmail.com Wed May 1 01:17:32 2013 From: eliswilson at hushmail.com (eliswilson at hushmail.com) Date: Tue, 30 Apr 2013 19:17:32 -0400 Subject: [Pandas-dev] Biggest Fake Conference in Computer Science Message-ID: <20130430231732.B1401E6736@smtp.hushmail.com> Biggest Fake Conference in Computer Science We are researchers from different parts of the world and conducted a study on the world?s biggest bogus computer science conference WORLDCOMP http://sites.google.com/site/worlddump1 organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without any reviews) and we were invited to submit the final paper and a payment of $500+ fee to present the paper. We decided to use the fee for better purposes than making Prof. Hamid Arabnia richer. After that, we received few reminders from WORLDCOMP to pay the fee but we never responded. This fake paper is different from the two fake papers already published (see https://sites.google.com/site/worlddump4 for details) in WORLDCOMP. We MUST say that you should look at the above website if you have any thoughts of participating in WORLDCOMP. DBLP and other indexing agencies have stopped indexing WORLDCOMP?s proceedings since 2011 due to its fakeness. See http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of http://sites.google.com/site/dumpconf for comments from well-known researchers about WORLDCOMP. The status of your WORLDCOMP papers can be changed from scientific to other (i.e., junk or non-technical) at any time. Better not to have a paper than having it in WORLDCOMP and spoil the resume and peace of mind forever! Our study revealed that WORLDCOMP is money making business, using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing out a small chunk of that money (around 20 dollars per paper published in WORLDCOMP?s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) who publicizes WORLDCOMP and also defends it at various forums, using fake/anonymous names. The puppet uses fake names and defames other conferences to divert traffic to WORLDCOMP. He also makes anonymous phone calls and threatens the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). That is, the puppet does all his best to get a maximum number of papers published at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia?s) pockets. Prof. Hamid Arabnia makes a lot of tricks. For example, he appeared in a newspaper to fool the public, claiming him a victim of cyber-attack (see Item 8 in Section 5 of above website). Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has refused to provide the venue for WORLDCOMP?13 because of the fears of their image being tarnished due to WORLDCOMP?s fraudulent activities. That is why WORLDCOMP?13 is taking place at a different resort. WORLDCOMP will not be held after 2013. The draft paper submission deadline is over but still there are no committee members, no reviewers, and there is no conference Chairman. The only contact details available on WORLDCOMP?s website is just an email address! We ask Prof. Hamid Arabnia to publish all reviews for all the papers (after blocking identifiable details) since 2000 conference. Reveal the names and affiliations of all the reviewers (for each year) and how many papers each reviewer had reviewed on average. We also ask him to look at the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 and respond if he has any professional values. Sorry for posting to multiple lists. Spreading the word is the only way to stop this bogus conference. Please forward this message to other mailing lists and people. We are shocked with Prof. Hamid Arabnia and his puppet?s activities at http://worldcomp-fake-bogus.blogspot.com Search Google using the keyword worldcomp fake for additional links. From wesmckinn at gmail.com Fri May 10 01:32:37 2013 From: wesmckinn at gmail.com (Wes McKinney) Date: Thu, 9 May 2013 16:32:37 -0700 Subject: [Pandas-dev] datetimes In-Reply-To: References: Message-ID: On Tue, Apr 30, 2013 at 1:42 PM, Jeff Reback wrote: > Currently we allow ONLY datetime64[ns] as an internal representation (and > analgously timedelta64[ns] for timedeltas). > > There are several issues where things like this are done: > > a) Series([np.datetime(2013,1,1),np.datetime(2013,1,2)],dtype='M8[ms]') > > b) Series([datetime(2013,1,1),datetime(2013,1,2)],dtype='M8[D]') > > > in a) the np.datetimes are by default [us], so we need to do a conversion > to M8[ns], ok, can do that to keep the internal rep, but what about the > dtype specified? is this effectively an astype, but then is this > conceptually just a display thing, e.g. the user wants to view the data as > [ms], rather than [ns] > > several options to think about: > > 1) ignore completely the passed dtype and do some conversions on > np.datetime64 (which we already do) to guarantee > a M8[ns] internally (we do this now, but bork on a passed dtype that is not > M8[ns] when the data is M8) > 2) keep the passed dtype (or the inferred dtype) internally, effectively > making datetimes a suite of M8[ms,D,s,ns......] > 3) keep data a M8[ns] internally and provide an asfreq which works kind of > like the PeriodIndex method, which can provide a DateTimeIndex I guess of > the requested frequency? but then I keep thinking, is there any actual > difference between > 20130101 15:00:01.12345 in [ms], or [ns] (right now no) > > Any thoughts....I know I am ramblings a bit, but confused over what is even > necessary here... > > > Jeff > > > > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > http://mail.python.org/mailman/listinfo/pandas-dev > Little slow getting back. I'm pretty unhappy with how things turned out in NumPy-- I guess it's my fault for not speaking up when the work was being done in 2010 and 2011, but back then no one in the Scientific Python establishment took pandas very seriously. My thinking has always been we should have either have: a) a single timestamp and timedelta data type, and different lower frequencies (annual, montly, etc.) can be handled by the period data type. This is the approach taken by pandas right now b) A timestamp with parametric units. This is the approach taken in NumPy, but with essentially no APIs to help you with that. I'm fine with always yielding datetime64[ns] out of whatever datetime64 dtype is passed. The NumPy data type system is just an ugly implementation detail at this point, especially in this area. - Wes From jeffreback at gmail.com Mon May 13 16:33:16 2013 From: jeffreback at gmail.com (Jeff Reback) Date: Mon, 13 May 2013 10:33:16 -0400 Subject: [Pandas-dev] datetimes In-Reply-To: References: Message-ID: These 2 PR's (already mergerd) will basically disallow astype('datetime64[s]') and such so that we ALWAYS have datetime64[ns] internally https://github.com/pydata/pandas/pull/3550 https://github.com/pydata/pandas/pull/3516 This issue: Timestamp should have alternate constructor for UTC millisecond timestamps https://github.com/pydata/pandas/issues/3540 Will allow passing of a 'unit' keyword to have datetime constructors (primarily Timestamp) to correctly interpret passed in values that are not easily discernable, e.g. ints (or epoch times that are say in ms), and provide conversions to internal datetime64[ns] the only remaining issue I think then would be if we want to have some sort of conversion to something like datetime64[s] (as an output). Not sure if this is even useful. Jeff On Thu, May 9, 2013 at 7:32 PM, Wes McKinney wrote: > On Tue, Apr 30, 2013 at 1:42 PM, Jeff Reback wrote: > > Currently we allow ONLY datetime64[ns] as an internal representation (and > > analgously timedelta64[ns] for timedeltas). > > > > There are several issues where things like this are done: > > > > a) Series([np.datetime(2013,1,1),np.datetime(2013,1,2)],dtype='M8[ms]') > > > > b) Series([datetime(2013,1,1),datetime(2013,1,2)],dtype='M8[D]') > > > > > > in a) the np.datetimes are by default [us], so we need to do a > conversion > > to M8[ns], ok, can do that to keep the internal rep, but what about the > > dtype specified? is this effectively an astype, but then is this > > conceptually just a display thing, e.g. the user wants to view the data > as > > [ms], rather than [ns] > > > > several options to think about: > > > > 1) ignore completely the passed dtype and do some conversions on > > np.datetime64 (which we already do) to guarantee > > a M8[ns] internally (we do this now, but bork on a passed dtype that is > not > > M8[ns] when the data is M8) > > 2) keep the passed dtype (or the inferred dtype) internally, effectively > > making datetimes a suite of M8[ms,D,s,ns......] > > 3) keep data a M8[ns] internally and provide an asfreq which works kind > of > > like the PeriodIndex method, which can provide a DateTimeIndex I guess of > > the requested frequency? but then I keep thinking, is there any actual > > difference between > > 20130101 15:00:01.12345 in [ms], or [ns] (right now no) > > > > Any thoughts....I know I am ramblings a bit, but confused over what is > even > > necessary here... > > > > > > Jeff > > > > > > > > _______________________________________________ > > Pandas-dev mailing list > > Pandas-dev at python.org > > http://mail.python.org/mailman/listinfo/pandas-dev > > > > Little slow getting back. I'm pretty unhappy with how things turned > out in NumPy-- I guess it's my fault for not speaking up when the work > was being done in 2010 and 2011, but back then no one in the > Scientific Python establishment took pandas very seriously. > > My thinking has always been we should have either have: > > a) a single timestamp and timedelta data type, and different lower > frequencies (annual, montly, etc.) can be handled by the period data > type. This is the approach taken by pandas right now > > b) A timestamp with parametric units. This is the approach taken in > NumPy, but with essentially no APIs to help you with that. > > I'm fine with always yielding datetime64[ns] out of whatever > datetime64 dtype is passed. The NumPy data type system is just an ugly > implementation detail at this point, especially in this area. > > - Wes > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > http://mail.python.org/mailman/listinfo/pandas-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffreback at gmail.com Fri May 17 23:23:59 2013 From: jeffreback at gmail.com (Jeff Reback) Date: Fri, 17 May 2013 17:23:59 -0400 Subject: [Pandas-dev] change/wes can you turn the docs builder on? hasn't updated since may 11..thanks Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeffreback at gmail.com Mon May 20 13:57:57 2013 From: jeffreback at gmail.com (Jeff Reback) Date: Mon, 20 May 2013 07:57:57 -0400 Subject: [Pandas-dev] 0.11.1 Message-ID: very little left in the issues space y-p? https://github.com/pydata/pandas/issues/3573 a PR I think should be included https://github.com/pydata/pandas/pull/3649 I think y-p has a couple as well a couple of issues for wesm: https://github.com/pydata/pandas/issues/3501 https://github.com/pydata/pandas/issues/3453 a to_csv issue about quoting https://github.com/pydata/pandas/issues/3503 maybe...chang? https://github.com/pydata/pandas/issues/3634 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wesmckinn at gmail.com Mon May 20 20:51:14 2013 From: wesmckinn at gmail.com (Wes McKinney) Date: Mon, 20 May 2013 11:51:14 -0700 Subject: [Pandas-dev] 0.11.1 In-Reply-To: References: Message-ID: On Mon, May 20, 2013 at 4:57 AM, Jeff Reback wrote: > very little left in the issues space > > y-p? > https://github.com/pydata/pandas/issues/3573 > > a PR I think should be included > https://github.com/pydata/pandas/pull/3649 > > I think y-p has a couple as well > > a couple of issues for wesm: > https://github.com/pydata/pandas/issues/3501 > https://github.com/pydata/pandas/issues/3453 > > a to_csv issue about quoting > https://github.com/pydata/pandas/issues/3503 > > maybe...chang? > https://github.com/pydata/pandas/issues/3634 > > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > http://mail.python.org/mailman/listinfo/pandas-dev > Cool-- just moved these to 0.11.1 milestone. What do you think about merging the JSON-back-from-the-dead code, right after 0.11.1? From jreback at yahoo.com Mon May 20 22:25:44 2013 From: jreback at yahoo.com (Jeff Reback) Date: Mon, 20 May 2013 16:25:44 -0400 Subject: [Pandas-dev] 0.11.1 In-Reply-To: References: Message-ID: <91D9610D-F91C-47CC-AD6C-D1161A5F689B@yahoo.com> sounds good should these method be in pandas.io.json to avoid bloating the core methods? On May 20, 2013, at 2:51 PM, Wes McKinney wrote: > On Mon, May 20, 2013 at 4:57 AM, Jeff Reback wrote: >> very little left in the issues space >> >> y-p? >> https://github.com/pydata/pandas/issues/3573 >> >> a PR I think should be included >> https://github.com/pydata/pandas/pull/3649 >> >> I think y-p has a couple as well >> >> a couple of issues for wesm: >> https://github.com/pydata/pandas/issues/3501 >> https://github.com/pydata/pandas/issues/3453 >> >> a to_csv issue about quoting >> https://github.com/pydata/pandas/issues/3503 >> >> maybe...chang? >> https://github.com/pydata/pandas/issues/3634 >> >> _______________________________________________ >> Pandas-dev mailing list >> Pandas-dev at python.org >> http://mail.python.org/mailman/listinfo/pandas-dev > > Cool-- just moved these to 0.11.1 milestone. What do you think about > merging the JSON-back-from-the-dead code, right after 0.11.1? From wesmckinn at gmail.com Tue May 21 09:32:17 2013 From: wesmckinn at gmail.com (Wes McKinney) Date: Tue, 21 May 2013 00:32:17 -0700 Subject: [Pandas-dev] 0.11.1 In-Reply-To: <91D9610D-F91C-47CC-AD6C-D1161A5F689B@yahoo.com> References: <91D9610D-F91C-47CC-AD6C-D1161A5F689B@yahoo.com> Message-ID: On Mon, May 20, 2013 at 1:25 PM, Jeff Reback wrote: > sounds good > should these method be in > pandas.io.json > > to avoid bloating the core methods? > > > On May 20, 2013, at 2:51 PM, Wes McKinney wrote: > >> On Mon, May 20, 2013 at 4:57 AM, Jeff Reback wrote: >>> very little left in the issues space >>> >>> y-p? >>> https://github.com/pydata/pandas/issues/3573 >>> >>> a PR I think should be included >>> https://github.com/pydata/pandas/pull/3649 >>> >>> I think y-p has a couple as well >>> >>> a couple of issues for wesm: >>> https://github.com/pydata/pandas/issues/3501 >>> https://github.com/pydata/pandas/issues/3453 >>> >>> a to_csv issue about quoting >>> https://github.com/pydata/pandas/issues/3503 >>> >>> maybe...chang? >>> https://github.com/pydata/pandas/issues/3634 >>> >>> _______________________________________________ >>> Pandas-dev mailing list >>> Pandas-dev at python.org >>> http://mail.python.org/mailman/listinfo/pandas-dev >> >> Cool-- just moved these to 0.11.1 milestone. What do you think about >> merging the JSON-back-from-the-dead code, right after 0.11.1? I feel that JSON is an important enough serialization format (along with CSV/TSV, definitely) to be core methods. What do you think? From wesmckinn at gmail.com Fri May 24 23:58:16 2013 From: wesmckinn at gmail.com (Wes McKinney) Date: Fri, 24 May 2013 14:58:16 -0700 Subject: [Pandas-dev] 0.11.1 In-Reply-To: References: <91D9610D-F91C-47CC-AD6C-D1161A5F689B@yahoo.com> Message-ID: On Tue, May 21, 2013 at 3:18 AM, Jeff Reback wrote: > oh I agree they should be core methods > (and have to_json,read_json) > > just think all io should be put in pandas.io > (as we r moving that way already there for: csv,hdf,excel,html...) > > just easier to manage > > and then put the accessor methods in core.generic (for to_) and have the read_ from the top level API > > avoids code bloat in the core/frame and friends > > actually would deprecate from_csv constructors as well - I think pd.read_csv pretty dominant now > > > On May 21, 2013, at 3:32 AM, Wes McKinney wrote: > >> On Mon, May 20, 2013 at 1:25 PM, Jeff Reback wrote: >>> sounds good >>> should these method be in >>> pandas.io.json >>> >>> to avoid bloating the core methods? >>> >>> >>> On May 20, 2013, at 2:51 PM, Wes McKinney wrote: >>> >>>> On Mon, May 20, 2013 at 4:57 AM, Jeff Reback wrote: >>>>> very little left in the issues space >>>>> >>>>> y-p? >>>>> https://github.com/pydata/pandas/issues/3573 >>>>> >>>>> a PR I think should be included >>>>> https://github.com/pydata/pandas/pull/3649 >>>>> >>>>> I think y-p has a couple as well >>>>> >>>>> a couple of issues for wesm: >>>>> https://github.com/pydata/pandas/issues/3501 >>>>> https://github.com/pydata/pandas/issues/3453 >>>>> >>>>> a to_csv issue about quoting >>>>> https://github.com/pydata/pandas/issues/3503 >>>>> >>>>> maybe...chang? >>>>> https://github.com/pydata/pandas/issues/3634 >>>>> >>>>> _______________________________________________ >>>>> Pandas-dev mailing list >>>>> Pandas-dev at python.org >>>>> http://mail.python.org/mailman/listinfo/pandas-dev >>>> >>>> Cool-- just moved these to 0.11.1 milestone. What do you think about >>>> merging the JSON-back-from-the-dead code, right after 0.11.1? >> >> I feel that JSON is an important enough serialization format (along >> with CSV/TSV, definitely) to be core methods. What do you think? >> _______________________________________________ >> Pandas-dev mailing list >> Pandas-dev at python.org >> http://mail.python.org/mailman/listinfo/pandas-dev Agreed, deprecate from_* methods and simply have pandas.read_json and DataFrame.to_json, etc. - Wes From wesmckinn at gmail.com Sun May 26 00:37:10 2013 From: wesmckinn at gmail.com (Wes McKinney) Date: Sat, 25 May 2013 15:37:10 -0700 Subject: [Pandas-dev] change/wes can you turn the docs builder on? hasn't updated since may 11..thanks In-Reply-To: References: Message-ID: On Fri, May 17, 2013 at 2:23 PM, Jeff Reback wrote: > > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > http://mail.python.org/mailman/listinfo/pandas-dev > This is back up and running post-move finally (we were missing some cables and a spare keyboard/mouse). I'll look into the status of the Jenkins runs on Windows versions when I can-- all those need to be upgraded to NumPy 1.7.1 too I presume (they're still on 1.6.1 but it's ABI compatible AFAIK). From jeffreback at gmail.com Sun May 26 00:42:45 2013 From: jeffreback at gmail.com (Jeff Reback) Date: Sat, 25 May 2013 18:42:45 -0400 Subject: [Pandas-dev] change/wes can you turn the docs builder on? hasn't updated since may 11..thanks In-Reply-To: References: Message-ID: great! need to install BeautifulSoup4 and html5lib on your doc build box as well otherwise looks good thxs On May 25, 2013, at 6:37 PM, Wes McKinney wrote: > On Fri, May 17, 2013 at 2:23 PM, Jeff Reback wrote: >> >> _______________________________________________ >> Pandas-dev mailing list >> Pandas-dev at python.org >> http://mail.python.org/mailman/listinfo/pandas-dev > > This is back up and running post-move finally (we were missing some > cables and a spare keyboard/mouse). I'll look into the status of the > Jenkins runs on Windows versions when I can-- all those need to be > upgraded to NumPy 1.7.1 too I presume (they're still on 1.6.1 but it's > ABI compatible AFAIK). > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > http://mail.python.org/mailman/listinfo/pandas-dev From wesmckinn at gmail.com Sun May 26 00:44:14 2013 From: wesmckinn at gmail.com (Wes McKinney) Date: Sat, 25 May 2013 15:44:14 -0700 Subject: [Pandas-dev] change/wes can you turn the docs builder on? hasn't updated since may 11..thanks In-Reply-To: References: Message-ID: On Sat, May 25, 2013 at 3:42 PM, Jeff Reback wrote: > great! > > need to install BeautifulSoup4 > and html5lib on your doc build box as well > > otherwise looks good > thxs > > > On May 25, 2013, at 6:37 PM, Wes McKinney wrote: > >> On Fri, May 17, 2013 at 2:23 PM, Jeff Reback wrote: >>> >>> _______________________________________________ >>> Pandas-dev mailing list >>> Pandas-dev at python.org >>> http://mail.python.org/mailman/listinfo/pandas-dev >> >> This is back up and running post-move finally (we were missing some >> cables and a spare keyboard/mouse). I'll look into the status of the >> Jenkins runs on Windows versions when I can-- all those need to be >> upgraded to NumPy 1.7.1 too I presume (they're still on 1.6.1 but it's >> ABI compatible AFAIK). >> _______________________________________________ >> Pandas-dev mailing list >> Pandas-dev at python.org >> http://mail.python.org/mailman/listinfo/pandas-dev Yeah and upgrade xlrd also. From jreback at yahoo.com Thu May 30 23:03:32 2013 From: jreback at yahoo.com (Jeff Reback) Date: Thu, 30 May 2013 17:03:32 -0400 Subject: [Pandas-dev] docs Message-ID: <9F21E198-2374-489C-896A-B956C6CDFC4A@yahoo.com> docs regenerated today but must have been a failure somewhere as io.rst and api.rst still reflecting the old version (while everything else seems ok) weird Still need bs4 / html5lib on the build machine! thanks Jeff From changshe at gmail.com Thu May 30 23:39:08 2013 From: changshe at gmail.com (Chang She) Date: Thu, 30 May 2013 14:39:08 -0700 Subject: [Pandas-dev] docs In-Reply-To: <9F21E198-2374-489C-896A-B956C6CDFC4A@yahoo.com> References: <9F21E198-2374-489C-896A-B956C6CDFC4A@yahoo.com> Message-ID: i'm on it On Thu, May 30, 2013 at 2:03 PM, Jeff Reback wrote: > docs regenerated today > but must have been a failure somewhere as io.rst and api.rst still reflecting the old version (while everything else seems ok) > > weird > > Still need bs4 / html5lib on the build machine! > > thanks > Jeff > > _______________________________________________ > Pandas-dev mailing list > Pandas-dev at python.org > http://mail.python.org/mailman/listinfo/pandas-dev From changshe at gmail.com Thu May 30 23:53:16 2013 From: changshe at gmail.com (Chang She) Date: Thu, 30 May 2013 14:53:16 -0700 Subject: [Pandas-dev] docs In-Reply-To: References: <9F21E198-2374-489C-896A-B956C6CDFC4A@yahoo.com> Message-ID: I installed bs4 / html5lib and new docs are currently building On Thu, May 30, 2013 at 2:39 PM, Chang She wrote: > i'm on it > > On Thu, May 30, 2013 at 2:03 PM, Jeff Reback wrote: >> docs regenerated today >> but must have been a failure somewhere as io.rst and api.rst still reflecting the old version (while everything else seems ok) >> >> weird >> >> Still need bs4 / html5lib on the build machine! >> >> thanks >> Jeff >> >> _______________________________________________ >> Pandas-dev mailing list >> Pandas-dev at python.org >> http://mail.python.org/mailman/listinfo/pandas-dev From changshe at gmail.com Fri May 31 02:29:21 2013 From: changshe at gmail.com (Chang She) Date: Thu, 30 May 2013 17:29:21 -0700 Subject: [Pandas-dev] docs In-Reply-To: References: <9F21E198-2374-489C-896A-B956C6CDFC4A@yahoo.com> Message-ID: ok i think we're all set with the docs. On Thu, May 30, 2013 at 2:53 PM, Chang She wrote: > I installed bs4 / html5lib and new docs are currently building > > On Thu, May 30, 2013 at 2:39 PM, Chang She wrote: >> i'm on it >> >> On Thu, May 30, 2013 at 2:03 PM, Jeff Reback wrote: >>> docs regenerated today >>> but must have been a failure somewhere as io.rst and api.rst still reflecting the old version (while everything else seems ok) >>> >>> weird >>> >>> Still need bs4 / html5lib on the build machine! >>> >>> thanks >>> Jeff >>> >>> _______________________________________________ >>> Pandas-dev mailing list >>> Pandas-dev at python.org >>> http://mail.python.org/mailman/listinfo/pandas-dev From cpcloud at gmail.com Fri May 31 23:18:00 2013 From: cpcloud at gmail.com (Phillip Cloud) Date: Fri, 31 May 2013 17:18:00 -0400 Subject: [Pandas-dev] mailing list Message-ID: hey guys, is it possible we could move this list to google groups? -------------- next part -------------- An HTML attachment was scrubbed... URL: