Re: Converting py files to .exe and .dmg

2016-01-01 Thread Michiel Overtoom
> On 2016-01-01, at 07:43, Brian Simms wrote: > > when I go into Terminal to run "setup.py install" I keep getting "-bash: > command not found". Try: python setup.py install Greetings, -- https://mail.python.org/mailman/listinfo/python-list

Re: Newbie: Check first two non-whitespace characters

2016-01-01 Thread Jussi Piitulainen
otaksoftspamt...@gmail.com writes: > I need to check a string over which I have no control for the first 2 > non-white space characters (which should be '[{'). > > The string would ideally be: '[{...' but could also be something like > ' [ { '. > > Best to use re and how? Something else?

Re: Newbie: Check first two non-whitespace characters

2016-01-01 Thread Karim
On 01/01/2016 00:25, Mark Lawrence wrote: On 31/12/2015 18:54, Karim wrote: On 31/12/2015 19:18, otaksoftspamt...@gmail.com wrote: I need to check a string over which I have no control for the first 2 non-white space characters (which should be '[{'). The string would ideally be: '[{...' b

Mac Question

2016-01-01 Thread tdsperth
Hi All I am trying to create a directory on a windows drive from my macbook air with python but get a permissions error because the windows ntfs drive is read only - does anyone know away to overcome this issue - I have looked for a utility but have yet to find an answer. Regards and Happy New

Re: Mac Question

2016-01-01 Thread Chris Angelico
On Fri, Jan 1, 2016 at 9:56 PM, wrote: > Hi All > > I am trying to create a directory on a windows drive from my macbook air with > python but get a permissions error because the windows ntfs drive is read > only - does anyone know away to overcome this issue - I have looked for a > utility bu

Re: Mac Question

2016-01-01 Thread tdsperth
On Friday, January 1, 2016 at 7:13:41 PM UTC+8, Chris Angelico wrote: > On Fri, Jan 1, 2016 at 9:56 PM, wrote: > > Hi All > > > > I am trying to create a directory on a windows drive from my macbook air > > with python but get a permissions error because the windows ntfs drive is > > read only

Re: Mac Question

2016-01-01 Thread Chris Angelico
On Fri, Jan 1, 2016 at 10:27 PM, wrote: > I connect to a drive in a windows 10 computer smb://192.168.50.58/c from my > mac but the drive is read only - i am looking for away to make the drive > writable so I can make a directory on the drive from my python script. > You'll have to look into

Re: Mac Question

2016-01-01 Thread William Ray Wing
> On Jan 1, 2016, at 5:56 AM, tdspe...@gmail.com wrote: > > Hi All > > I am trying to create a directory on a windows drive from my macbook air with > python but get a permissions error because the windows ntfs drive is read > only - does anyone know away to overcome this issue - I have looked

Re: Stupid Python tricks

2016-01-01 Thread paul . hermeneutic
On Wed, Dec 30, 2015 at 11:09 PM, Steven D'Aprano wrote: > On Thu, 31 Dec 2015 04:02 pm, Rick Johnson wrote: > > >> Fifteen years later, and Tim Peters' Stupid Python Trick is still the > >> undisputed champion! > > > > And should we be happy about that revelation, or sad? > > Yes! > > Which one,

Example for Multiple and Multilevel Inheritance

2016-01-01 Thread PythonLearner
Hello All, I'm new to this group. I'm looking for examples for Multiple and Multilevel Inheritance without the use of super(). Thanks An Avid Python Learner -- https://mail.python.org/mailman/listinfo/python-list

Re: Example for Multiple and Multilevel Inheritance

2016-01-01 Thread Mark Lawrence
On 01/01/2016 19:16, PythonLearner wrote: Hello All, I'm new to this group. I'm looking for examples for Multiple and Multilevel Inheritance without the use of super(). Thanks An Avid Python Learner Please tell us what you're trying to achive, as without super() you'll be throwing DRY right

We will be moving to GitHub

2016-01-01 Thread Mark Lawrence
Please see https://mail.python.org/pipermail/core-workflow/2016-January/000345.html This should encourage developers at all levels to help out, such that the list of open issues on the bug tracker falls drastically. -- My fellow Pythonistas, ask not what our language can do for you, ask what

Re: We will be moving to GitHub

2016-01-01 Thread Chris Angelico
On Sat, Jan 2, 2016 at 6:39 AM, Mark Lawrence wrote: > Please see > https://mail.python.org/pipermail/core-workflow/2016-January/000345.html > > This should encourage developers at all levels to help out, such that the > list of open issues on the bug tracker falls drastically. How does that inte

Re: We will be moving to GitHub

2016-01-01 Thread Zachary Ware
On Jan 1, 2016 1:47 PM, "Chris Angelico" wrote: > > On Sat, Jan 2, 2016 at 6:39 AM, Mark Lawrence wrote: > > Please see > > https://mail.python.org/pipermail/core-workflow/2016-January/000345.html > > > > This should encourage developers at all levels to help out, such that the > > list of open i

Re: We will be moving to GitHub

2016-01-01 Thread paul . hermeneutic
Mark, it is good to know that a decision has been made so that we can move forward. Is there a summary document that discusses the options examined and why others did not meet the requirements? I am -NOT- trying to dredge up arguments about the choice. I am guessing that there have been some. If

Re: We will be moving to GitHub

2016-01-01 Thread Chris Angelico
On Sat, Jan 2, 2016 at 6:58 AM, Zachary Ware wrote: >> It's not entirely clear whether that message is an acceptance of PEP 481 > or not. > > I've lost track of the pep numbers, but Brett's decision is final; the > canonical CPython repository will be moving to GitHub in the near future. > Note th

Re: Python.Exe Problem

2016-01-01 Thread paul . hermeneutic
Daniel, after the download, please be sure to verify the MD5 checksum to know that the download is correct. On Tue, Dec 29, 2015 at 1:44 PM, Terry Reedy wrote: > On 12/29/2015 11:24 AM, Daniel Lee wrote: > >> Hello, >> >> When I try to run python.exe on my computer with Windows 8, >> > > Which e

Re: We will be moving to GitHub

2016-01-01 Thread Paul Rubin
Zachary Ware writes: > ... the canonical CPython repository will be moving to GitHub in the > near future. Note that we will *not* be using the GitHub issue > tracker or wiki, just the hosting and review/pull request system. Will everyone wanting to submit patches be required to use a Github acc

Re: We will be moving to GitHub

2016-01-01 Thread Zachary Ware
On Jan 1, 2016 2:35 PM, "Paul Rubin" wrote: > > Zachary Ware writes: > > ... the canonical CPython repository will be moving to GitHub in the > > near future. Note that we will *not* be using the GitHub issue > > tracker or wiki, just the hosting and review/pull request system. > > Will everyone

Re: We will be moving to GitHub

2016-01-01 Thread Mark Lawrence
On 01/01/2016 20:03, paul.hermeneu...@gmail.com wrote: Mark, it is good to know that a decision has been made so that we can move forward. Is there a summary document that discusses the options examined and why others did not meet the requirements? I am -NOT- trying to dredge up arguments about

Re: We will be moving to GitHub

2016-01-01 Thread Zachary Ware
On Fri, Jan 1, 2016 at 2:03 PM, wrote: > Is there a summary document that discusses the options examined and why > others did not meet the requirements? I am -NOT- trying to dredge up > arguments about the choice. I am guessing that there have been some. Easiest would be to look through the arch

Re: We will be moving to GitHub

2016-01-01 Thread Paul Rubin
Zachary Ware writes: > Correct, no GitHub account will be required for interactions on the > bugs.python.org tracker, and a patch can move all the way through to commit > entirely on the b.p.o tracker (just as currently). Thanks. -- https://mail.python.org/mailman/listinfo/python-list

Re: Python Data Analysis Recommendations

2016-01-01 Thread Mark Lawrence
On 31/12/2015 17:15, Rob Gaddi wrote: I'm looking for some advice on handling data collection/analysis in Python. I do a lot of big, time consuming experiments in which I run a long data collection (a day or a weekend) in which I sweep a bunch of variables, then come back offline and try to cut

Re: Stupid Python tricks

2016-01-01 Thread Serhiy Storchaka
On 01.01.16 21:00, paul.hermeneu...@gmail.com wrote: On Wed, Dec 30, 2015 at 11:09 PM, Steven D'Aprano wrote: On Thu, 31 Dec 2015 04:02 pm, Rick Johnson wrote: Fifteen years later, and Tim Peters' Stupid Python Trick is still the undisputed champion! And should we be happy about that revel

Re: Python Data Analysis Recommendations

2016-01-01 Thread Ravi Narasimhan
On 1/1/16 1:24 PM, Mark Lawrence wrote: > On 31/12/2015 17:15, Rob Gaddi wrote: >> I'm looking for some advice on handling data collection/analysis in >> Python. ... >> The whole process feels a bit grindy; like I keep having to do a lot of >> ad-hoc stitching things together. And I keep hearing

Re: Stupid Python tricks

2016-01-01 Thread Serhiy Storchaka
On 31.12.15 05:51, Steven D'Aprano wrote: Fifteen years later, and Tim Peters' Stupid Python Trick is still the undisputed champion! It may be platform depended, but on my computer the obvious way is 10% faster the Stupid Python Trick. -- https://mail.python.org/mailman/listinfo/python-list

Re: Need help on a project To :"Create a class called BankAccount with the following parameters "

2016-01-01 Thread xaviertim017
On Saturday, December 26, 2015 at 12:06:07 AM UTC+1, Won Chang wrote: > i have gotten the answer of that problem Please Can you post the answer you got. If convenient send to my email xaviertim...@gmail.com. Thanks in advance. -- https://mail.python.org/mailman/listinfo/python-list

Re: Need help on a project To :"Create a class called BankAccount with the following parameters "

2016-01-01 Thread xaviertim017
On Saturday, December 12, 2015 at 10:05:29 AM UTC+1, Harbey Leke wrote: > Create a class called BankAccount > > .Create a constructor that takes in an integer and assigns this to a > `balance` property. > > .Create a method called `deposit` that takes in cash deposit amount and > updates the ba

Re: We will be moving to GitHub

2016-01-01 Thread Terry Reedy
On 1/1/2016 4:08 PM, Zachary Ware wrote: On Fri, Jan 1, 2016 at 2:03 PM, wrote: Is there a summary document that discusses the options examined and why others did not meet the requirements? I am -NOT- trying to dredge up arguments about the choice. I am guessing that there have been some. Ea

Re: We will be moving to GitHub

2016-01-01 Thread Paul Rubin
Terry Reedy writes: > While the decision might not be my personal first choice, we > absolutely need more core developers contributing, including reviewing > contributed patches. Yeah, I'm not delighted by the choice either, but as long as the core devs have bought in and it doesn't affect non-co

Re: We will be moving to GitHub

2016-01-01 Thread Steven D'Aprano
On Sat, 2 Jan 2016 07:09 am, Chris Angelico wrote: > Yes, git is a capable tool. But so is Mercurial, and the arguments > weren't primarily based on differences in functionality (which are > pretty minor). It's mainly about the network effect. You call it the network effect. I call it monoculture

Re: We will be moving to GitHub

2016-01-01 Thread Ben Finney
Zachary Ware writes: > On Jan 1, 2016 2:35 PM, "Paul Rubin" wrote: > > Will everyone wanting to submit patches be required to use a Github > > account? Or will it be enough to put the patch in an outside repo > > and link to it in the Python issue tracker? I'm glad that (it sounds > > like) no G

Re: We will be moving to GitHub

2016-01-01 Thread Ben Finney
Terry Reedy writes: > On 1/1/2016 4:08 PM, Zachary Ware wrote: > > There were three reasons given in Brett's decision message: > > > > 1. No major distinguishing features between GitHub or GitLab It seems “complete source code available and freely licensed, allowing the community to implemen

Re: We will be moving to GitHub

2016-01-01 Thread Chris Angelico
On Sat, Jan 2, 2016 at 5:43 PM, Steven D'Aprano wrote: > On Sat, 2 Jan 2016 07:09 am, Chris Angelico wrote: > >> Yes, git is a capable tool. But so is Mercurial, and the arguments >> weren't primarily based on differences in functionality (which are >> pretty minor). It's mainly about the network