Re: Solutions Manual Test Bank for Macroeconomics, 9th Edition by N. Gregory Mankiw

2017-11-12 Thread zms . ethiopia
On Friday, July 7, 2017 at 12:49:50 AM UTC+3, Test Banks wrote:
> Greetings, 
> 
> Solutions Manuals and Test Bank for " Macroeconomics, 9th Edition by N. 
> Gregory Mankiw " is available at very reasonable price. You can get these 
> files by sending email to pro.fast(@)hotmail(dot)com 
> 
> Send your requests to PRO.FAST(@)HOTMAIL(DOT)COM 
> 
> We do not monitor replies here so simply send us an email at above mentioned 
> email ID 
> 
> MACROECONOMICS, 9TH EDITION BY N. GREGORY MANKIW SOLUTIONS MANUAL TEST BANK 
> 
> We have large collection for Solutions and Test Banks for all subjects. You 
> can email us at PRO.FAST (@) HOTMAIL (DOT) COM for your queries and we will 
> check that book SM and TB for you. 
> 
> ISBN Numbers for this book is given below 
> 
> ISBN-10: 1464182892 
> ISBN-13: 9781464182891
> 
> 
> Cheers, 
> Solutions Manuals and Test Bank Team 
> Since 2008

-- 
https://mail.python.org/mailman/listinfo/python-list


Re: How to modify this from Python 2.x to v3.4?

2017-11-12 Thread jfong
Rick Johnson於 2017年11月12日星期日 UTC+8上午11時07分20秒寫道:
> `print` was changed from a statement to a function, so it's
> just a matter of converting it to a function call. If you
> read the docs for the new print function, it should be
> relatively easy to translate. I don't understand why you're
> having so much trouble.
> 
> 
> https://docs.python.org/3/whatsnew/3.0.html?highlight=print#common-stumbling-blocks

It's a shame I didn't read its doc in v3.4 thoughtfully:

print(*objects, sep=' ', end='\n', file=sys.stdout, flush=False) 

I thought position argument is essential, but it's not in this function:

If no objects are given, print() will just write end.

Thanks for your reminder.

--Jach
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: How to modify this from Python 2.x to v3.4?

2017-11-12 Thread Thomas Jollans
On 2017-11-12 03:06, jf...@ms4.hinet.net wrote:
> I suppose there are many v3.x users who like to use ctypesgen to ease
> the using of ctypes.

Perhaps, but from what I can tell the increasingly popular cffi package
serves a similar need.

By all means, port ctypesgen to Python 3 (and publish your port) if you
want to, but you might want to consider whether it's easier to port your
code from ctypes/ctypesgen to cffi instead.

-- 
Thomas Jollans

-- 
https://mail.python.org/mailman/listinfo/python-list


Re: Need some help with Python Job Board

2017-11-12 Thread justin walters
On Sat, Nov 11, 2017 at 3:27 PM, Skip Montanaro 
wrote:

> The Python Job Board could use a little help in a couple areas. One, we can
> always use help reviewing and approving (or rejecting) submissions. The
> backlog keeps growing, and the existing volunteers who help can't always
> keep up. (This is a good problem to have, reflecting on Python's broad
> popularity in many application domains.)
>
> Two, and perhaps more important, the submission form really needs to
> support WYSIWYG editing. Apparently, most posters are unable to handle
> markup-based systems, probably just pasting content from Word documents.
> Making this change would streamline the review process, as formatting
> problems are currently the biggest impediment to successful submissions.
> There is an open ticket to add this feature:
>
> https://github.com/python/pythondotorg/issues/655
>
> If you can help with either task, please drop a note to j...@python.org.
>
> Thanks,
>
> Skip
> --
> https://mail.python.org/mailman/listinfo/python-list
>

I might be able to help implement a wysiwyg editor. The only issue I can
think of at the moment
would be finding a way to determine if the template should render wysiswyg
content or Markdown content.

I'll need to look over the repo a bit more closely first.
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: Need some help with Python Job Board

2017-11-12 Thread Skip Montanaro
Thanks, Justin. I imagine editors probably exist which can switch between
WYSIWYG and markup. Whether that markup can be Markdown or not, I don't
know. Marc-André Lemburg listed a few possible editors in the ticket he
opened, but I've not dug into their properties.

Skip

On Sun, Nov 12, 2017 at 11:20 AM, justin walters  wrote:

> On Sat, Nov 11, 2017 at 3:27 PM, Skip Montanaro 
> wrote:
>
> > The Python Job Board could use a little help in a couple areas. One, we
> can
> > always use help reviewing and approving (or rejecting) submissions. The
> > backlog keeps growing, and the existing volunteers who help can't always
> > keep up. (This is a good problem to have, reflecting on Python's broad
> > popularity in many application domains.)
> >
> > Two, and perhaps more important, the submission form really needs to
> > support WYSIWYG editing. Apparently, most posters are unable to handle
> > markup-based systems, probably just pasting content from Word documents.
> > Making this change would streamline the review process, as formatting
> > problems are currently the biggest impediment to successful submissions.
> > There is an open ticket to add this feature:
> >
> > https://github.com/python/pythondotorg/issues/655
> >
> > If you can help with either task, please drop a note to j...@python.org.
> >
> > Thanks,
> >
> > Skip
> > --
> > https://mail.python.org/mailman/listinfo/python-list
> >
>
> I might be able to help implement a wysiwyg editor. The only issue I can
> think of at the moment
> would be finding a way to determine if the template should render wysiswyg
> content or Markdown content.
>
> I'll need to look over the repo a bit more closely first.
> --
> https://mail.python.org/mailman/listinfo/python-list
>
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: can't get python to run

2017-11-12 Thread Mary Ann via Python-list





trying to install and run Python 3.5.2 (64 bit) and keep getting error message:


the program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing 
from your computer. Try reintalling the program to fix this problem.

I am on Windows 7 Home Premium

I have uninstalled and reinstalled 3.5.2 several times and tried repairing and 
still the error message keeps coming back and i can't run python 3.5.2

I was able to run Python27 and it opened just fine.


I am not a computer person and am just starting to learn python and the 
professor said to install 3.5.2.  I just have no idea what the issue is other 
than maybe an old computer




regards,


Mary Ann

-- 
https://mail.python.org/mailman/listinfo/python-list


Re: can't get python to run

2017-11-12 Thread Paul Moore
On 12 November 2017 at 19:58, Mary Ann via Python-list
 wrote:
>
> trying to install and run Python 3.5.2 (64 bit) and keep getting error 
> message:
>
> the program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing 
> from your computer. Try reintalling the program to fix this problem.
>
> I am on Windows 7 Home Premium
>
> I have uninstalled and reinstalled 3.5.2 several times and tried repairing 
> and still the error message keeps coming back and i can't run python 3.5.2
>
> I was able to run Python27 and it opened just fine.
>
>
> I am not a computer person and am just starting to learn python and the 
> professor said to install 3.5.2.  I just have no idea what the issue is other 
> than maybe an old computer

This is something that comes up for people quite often. In a situation
like this, you can often find useful advice by searching Google. I put
the message "api-ms-win-crt-runtime-l1-1-0.dll is missing from your
computer" into Google, and got a few hits immediately that would
probably have been helpful to you.

What you should do is to download and install the "Visual C++
redistributable for Visual Studio 2015", which you can get from
https://www.microsoft.com/en-in/download/details.aspx?id=48145

You may also find that if you run "Check for updates" on your PC, this
will be installed automatically - MS do distribute this update
automatically, and it may be that you simply haven't updated recently.
But the manual install will work just as well.

Hope this helps,
Paul

PS The reason Python 2.7 works, is that it uses an older version of
Visual C, which doesn't need the newer runtime installed.
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: How to modify this from Python 2.x to v3.4?

2017-11-12 Thread jfong
Thomas Jollans於 2017年11月12日星期日 UTC+8下午5時17分38秒寫道:
> By all means, port ctypesgen to Python 3 (and publish your port) if you
> want to, 

I am not the right person because I have never use Python2 before:-)

> but you might want to consider whether it's easier to port your
> code from ctypes/ctypesgen to cffi instead.

CFFI seems is a little complex, at least to me. I had read its document but 
didn't get through yet:-(

--Jach
-- 
https://mail.python.org/mailman/listinfo/python-list


from xx import yy

2017-11-12 Thread bvdp
I'm having a conceptual mind-fart today. I just modified a bunch of code to use 
"from xx import variable" when variable is a global in xx.py. But, when I 
change/read 'variable' it doesn't appear to change. I've written a bit of code 
to show the problem:

mod1.py
myvar = 99
def setvar(x):
global myvar
myvar = x

test1.py
import mod1
mod1.myvar = 44
print (mod1.myvar)
mod1.setvar(33)
print (mod1.myvar)

If this test1.py is run myvar is fine. But, if I run:

test2.py
from mod1 import myvar, setvar
myvar = 44
print (myvar)
setvar(33)
print (myvar)

It doesn't print the '33'.

I thought (apparently incorrectly) that import as would import the name myvar 
into the current module's namespace where it could be read by functions in the 
module

-- 
https://mail.python.org/mailman/listinfo/python-list


Re: from xx import yy

2017-11-12 Thread Ned Batchelder

On 11/12/17 9:17 PM, bvdp wrote:

I'm having a conceptual mind-fart today. I just modified a bunch of code to use 
"from xx import variable" when variable is a global in xx.py. But, when I 
change/read 'variable' it doesn't appear to change. I've written a bit of code to show 
the problem:

mod1.py
myvar = 99
def setvar(x):
 global myvar
 myvar = x

test1.py
import mod1
mod1.myvar = 44
print (mod1.myvar)
mod1.setvar(33)
print (mod1.myvar)


In this case "mod1" is a name in test1 that refers to the mod1 module.  
You can access and assign attributes on that module. Anyone else 
referencing that module (including the module itself) will see those 
changed attributes.

If this test1.py is run myvar is fine. But, if I run:

test2.py
from mod1 import myvar, setvar
myvar = 44
print (myvar)
setvar(33)
print (myvar)

It doesn't print the '33'.


In this case, "myvar" is a name that references the same value as 
mod1.myvar.  Now both myvar and mod1.myvar refer to the same value. 
There is no direct connection between the myvar name and the mod1.myvar 
name.  When you reassign myvar, it now refers to some other value. 
mod1.myvar is unaffected.


--Ned.

I thought (apparently incorrectly) that import as would import the name myvar 
into the current module's namespace where it could be read by functions in the 
module



--
https://mail.python.org/mailman/listinfo/python-list


Re: from xx import yy

2017-11-12 Thread Chris Angelico
On Mon, Nov 13, 2017 at 1:17 PM, bvdp  wrote:
> I'm having a conceptual mind-fart today. I just modified a bunch of code to 
> use "from xx import variable" when variable is a global in xx.py. But, when I 
> change/read 'variable' it doesn't appear to change. I've written a bit of 
> code to show the problem:
>
> mod1.py
> myvar = 99
> def setvar(x):
> global myvar
> myvar = x
>
> test1.py
> import mod1
> mod1.myvar = 44
> print (mod1.myvar)
> mod1.setvar(33)
> print (mod1.myvar)
>
> If this test1.py is run myvar is fine. But, if I run:
>
> test2.py
> from mod1 import myvar, setvar
> myvar = 44
> print (myvar)
> setvar(33)
> print (myvar)
>
> It doesn't print the '33'.
>
> I thought (apparently incorrectly) that import as would import the name myvar 
> into the current module's namespace where it could be read by functions in 
> the module

It imports the *value*. What you have is basically this:

import mod1
myvar = mod1.myvar
setvar = mod1.setvar

Since functions remember their contexts, setvar() still sees the
globals of mod1. But myvar is a simple integer, so it's basically
"myvar = 99".

So basically, you can't from-import anything that's going to be
changed. You can import constants that way ("from stat import
S_IREAD"), or classes/functions (since they're not generally rebound),
but as a general rule, don't from-import anything mutable. In fact, if
you follow the even-more-general rule of "don't bother with
from-imports at all", you'll be right far more than you'll be wrong.

ChrisA
-- 
https://mail.python.org/mailman/listinfo/python-list


matchpy

2017-11-12 Thread Edward Montague
 After successfully installing python 3.6.3 and the appropriate version of
IDLE ,
I attempted to run a matchpy example , to no avail .

 I'm using a debian distribution , 8.x or greater , is there something I
need to be aware of .
The error report points to a statement containing a ' -> ' character , as
far as I know ,
this isn't valid python syntax .
-- 
https://mail.python.org/mailman/listinfo/python-list


Re: matchpy

2017-11-12 Thread Chris Angelico
On Mon, Nov 13, 2017 at 4:42 PM, Edward Montague  wrote:
>  After successfully installing python 3.6.3 and the appropriate version of
> IDLE ,
> I attempted to run a matchpy example , to no avail .
>
>  I'm using a debian distribution , 8.x or greater , is there something I
> need to be aware of .
> The error report points to a statement containing a ' -> ' character , as
> far as I know ,
> this isn't valid python syntax .

It IS valid Python syntax (a function annotation). You'll need to give
a lot more information for us to help you - preferably, a complete
runnable example.

ChrisA
-- 
https://mail.python.org/mailman/listinfo/python-list