-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DFPLY not working.....at all #64
Comments
I don't see any code that uses dfply, only code that uses pandas.
Could you post some example code that uses dfply?
…On Tue, 21 Aug 2018 18:56 jaybundy, ***@***.***> wrote:
Sorry for being so new to this. But I can't get dfply to work....at all.
It tells me select is not defined. I'm very frustrated. All I can find on
the internet is praise for this package and not support for the fact that I
can't get it to work. Below is some code.
from dfply import *
import pandas as pd
flight_data = pd.read_csv('nycflights13.csv')
flight_data.head()
AttributeError: module 'dfply' has no attribute 'select'
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#64>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABOypLk2tFOu54EBaTLxh5ZyuJSaxpKtks5uTEmzgaJpZM4WGS-j>
.
|
Try copying and pasting some of the example code that uses the built-in
diamonds dataframe.
…On Tue, 21 Aug 2018 19:59 Shane Tolmie, ***@***.***> wrote:
I don't see any code that uses dfply, only code that uses pandas.
Could you post some example code that uses dfply?
On Tue, 21 Aug 2018 18:56 jaybundy, ***@***.***> wrote:
> Sorry for being so new to this. But I can't get dfply to work....at all.
> It tells me select is not defined. I'm very frustrated. All I can find on
> the internet is praise for this package and not support for the fact that I
> can't get it to work. Below is some code.
>
> from dfply import *
> import pandas as pd
>
> flight_data = pd.read_csv('nycflights13.csv')
> flight_data.head()
>
> AttributeError: module 'dfply' has no attribute 'select'
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#64>, or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABOypLk2tFOu54EBaTLxh5ZyuJSaxpKtks5uTEmzgaJpZM4WGS-j>
> .
>
|
Thanks for timely support. The actual example code I'm trying to execute comes from: from dfply import * flight_data = pd.read_csv('nycflights13.csv') (flight_data >> Here is the full error message: |
Interestingly, If I just run this code: import os print(dfply) I still get: |
Hello there. What version of python are you using? I don't think it would matter for this specifically, but dfply only works for python 3 now in case you're using python 2... Can you open up a jupyter notebook or ipython console of and type: Then see if |
Version 3.7.0. Interestingly, I seem to be able to get the code to work fine using the interpreter interactively. But when I try to use the package in a script (I write scripts in VS Code), even trying to run "import dfply" only with absolutely no other lines of code, I still get the message: AttributeError: module 'dfply' has no attribute 'select' That's weird, because at that point I haven't referenced select at all (as in the original post). But I have the same problem with dplython. Works fine interactively, can't use it in a script, claims it doesn't have select...but in both cases select shows up in help as well as dir and seems to work fine interactively. |
That is odd for sure. In the code above you posted: import os
import pandas as pd
import dfply
print(dfply) Could you paste the exact error message you get here? |
I believe I figured it out. I was naming the module I used to test the package dfply.py...which obviously broke the import. I'm so sorry to have troubled you guys over such a novice error. But I am very, very grateful for the persistent assistance. Happy Pythoning and Thanks! |
Ah, that makes sense. I've done the same thing before but with a different package. I think every single Python expert makes this mistake at least once in their learning curve. Glad its sorted! |
This was never an issue. It should be deleted.
The text was updated successfully, but these errors were encountered: