Sir,
Please note that and we are Transferring payment again to your
Designated bank As advised earlier.
Kindly see attached covering letter with Bank Swift for follow up with
your bank.
Also see below specification Of payment breakdown.
USD 3,146.05
USD 28,550.00
Please kindly confirm t
.
This would mean StopIteration would bubble out of generator expressions as
the person who posted the original topic on python ideas wanted. And the
stop hack would no longer work.
Both generator expressions and comprehensions could be viewed as supplying
the body in a loop. This is in
On 11/22/2014 02:16 PM, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 6:49 AM, Ron Adam wrote:
>
>OPTION 1:
>
>Make comprehensions act more like generator expressions.
>
>It would mean a while loop in the object creation point is converted to a
>for loop. (or something
could think and reason about them in the same way.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail
On 11/22/2014 04:23 PM, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 8:03 AM, Ron Adam wrote:
>>Making comprehensions work more like generator expressions
>>would, IMO, imply making the same change to all for loops: having a
>>StopIteration raised by the body of the loop
On 11/22/2014 06:20 PM, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 11:05 AM, Ron Adam wrote:
>Se we have these...
>
> Tuple Comprehension (...)
> List Comprehension [...]
> Dict Comprehension {...} Colon make's it different from sets.
>
On 11/22/2014 07:06 PM, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 11:51 AM, Ron Adam wrote:
>
>
>On 11/22/2014 06:20 PM, Chris Angelico wrote:
>>
>>Hmmm, there's no such thing as tuple comprehensions.
>
>Just didn't think it through quite well enou
On 11/23/2014 04:08 AM, Terry Reedy wrote:
On 11/22/2014 5:23 PM, Chris Angelico wrote:
On Sun, Nov 23, 2014 at 8:03 AM, Ron Adam wrote:
Making comprehensions work more like generator expressions
would, IMO, imply making the same change to all for loops: having a
StopIteration raised by the
On 11/23/2014 04:15 PM, Chris Angelico wrote:
On Mon, Nov 24, 2014 at 5:28 AM, Ron Adam wrote:
>With the passage of the PEP, it will change what is different about them
>once it's in full effect. The stop hack won't work in both, and you may get
>a RuntimeError in ge
easier to do as well.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On 03/07/2015 04:58 AM, Steven D'Aprano wrote:
On Fri, Mar 06, 2015 at 08:00:20PM -0500, Ron Adam wrote:
>Have you considered doing this by having different magic numbers in the
>.pyc file for standard, -O, and -O0 compiled bytecode files? Python
>already checks that number
async function might be...
async def yielding():
pass
In a routine is taking very long time, just inserting "await yielding()" in
the long calculation would let other awaitables run.
If the async loop only has one coroutine (awaitable) in it, then it will be
just like calling a
On 05/02/2015 04:18 PM, Arnaud Delobelle wrote:
On 1 May 2015 at 20:59, Guido van Rossum wrote:
>On Fri, May 1, 2015 at 12:49 PM, Ron Adam wrote:
>>
>>
>>Another useful async function might be...
>>
>>async def yielding():
>>pass
>>
he same task, even if there is another one that
>could run. It's up to the scheduler whether it
>implements any kind of "fair" scheduling policy.
That's what I understood but the example ('yielding()') provided by
Ron Adam seemed to imply otherwise, so I wanted t
File "", line 1, in
File "", line 9, in func
File "", line 6, in _C
UnboundLocalError: local variable 'y' referenced before assignment
I think yes, but I'm not sure how it may be different in other ways.
Cheers,
Ron
___
On 06/20/2015 12:12 PM, Ron Adam wrote:
On 06/20/2015 02:51 AM, Ivan Levkivskyi wrote:
Guido said 13 years ago that this behavior should not be changed:
https://mail.python.org/pipermail/python-dev/2002-April/023428.html,
however, things changed a bit in Python 3.4 with the introduction
ync function, it needs to "await something" with a
yield in it that isn't an async function.
This seems to be a bit counter intuitive to me. Or am I missing something?
Regards,
Ron
___
Python-Dev mailing list
Pyth
use of it. I still don't want spell, or
grammar, checkers to not report my mistakes. And I don't recall ever
making the particular error of using "assret" in place of "assert". I'd be
more likely to mispell it as "assirt" if I wasn't already so
; bad or even that noticeable. But maybe it can be
a motivating factor for not doing similar things in other places.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
auses the
asserts to be removed. So it may require setting a flag on a function if
it's source contained "assert".
With a reliable test for "assert", the check for an naming convention alias
is not needed.
If I've still not quite got the gist of this issue,
eded.
Possibly adding a function, uses_assert(...), to the inspect module would
be good. To allow that to work, may need a flag set on function objects
if they contain assert even if the module is compiled in optimise mode.
(Is it doable? Or maybe there is another way?)
Cheers,
Ron
On 07/19/2015 02:33 PM, Florian Bruhin wrote:
* Ron Adam [2015-07-19 11:17:10 -0400]:
>I had to look at the source to figure out what this thread was really all
>about.
And it seems I don't quite get it still, but I am trying.
>Basically it looks to me the purpose of addi
On 07/20/2015 03:32 AM, Florian Bruhin wrote:
* Ron Adam [2015-07-19 18:06:22 -0400]:
>
>
>On 07/19/2015 02:33 PM, Florian Bruhin wrote:
> >* Ron Adam [2015-07-19 11:17:10 -0400]:
> >>>I had to look at the source to figure out what this thread was really all
&
eded. That can be done
sooner with better a better error message I think.
Using "assret*" in the objects being tested will never shadow a mock
method. So it seems it's a case of catching a mispelling in a test calling
a non-existing method. (But anyother spelling would not be
cores with no GIL.
If the question is...
* What is Python 4?
I think you get much more interesting answers. ;-)
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscri
In this case the context is the loading and unloading of a module. Having
context managers names end with manager helps indicate how it's used.
But other verb+er combinations also work. Taking a hint from the first few
words of the __doc__ string gives us a
ing function arguments to other functions.
Another variation of this is to have a way to forward a functions
"signature name space" to another function directly and bypass the
signature parsing those cases.
Cheers,
Ron
On 06/14/2013 10:36 AM, Guido van Rossum wrote:
Not a bug. The same is done for file input -- CRLF is changed to LF before
tokenizing.
Should this be the same?
python3 -c 'print(bytes("""\r\n""", "utf8"))'
b'\r\n'
>>>
ion then parses the
resulting string object it receives as it's input.
There is no mention of using raw strings in the docs on evel and exec. I
think there should be, because the intention (in most cases) is for eval to
parse the string, and not for it to be parsed or changed before
ome may be
functions with the name ending with eval or exec.
I do think that eval and exec is a similar case to regexps. And possibly
often enough, the string may contain a raw string, regular expression, or a
file/path name.
Only a short note needed in the docs for eval, not
hen a standard string literal used with eval, it's evaluated first to a
string object in the same scope as the eval function is called from, then
the eval function is called with that string object and it's evaluated
again. So it's really being parsed twice. (That's the part
till need to feed the bad strings to eval. If you
don't then you won't get the same output from eval as the compiler does.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
U
Tennessee Leeuwenburg wrote:
Hi all,
I'm continuing to (slowly) work through issues. I have been looking
particularly at a lot of the open issues regarding strftime.
It would be great to put in some of those extra status options that were
discussed recently...
"Open/New"
"Needs hel
P.J. Eby wrote:
Sure. But right now, the return value of a generator function *is the
generator*. And you're free to ignore that, sure.
But this is a "second" return value that only goes to a special place
with special syntax -- without that syntax, you can't access it.
But in the use c
Ron Adam wrote:
P.J. Eby wrote:
Sure. But right now, the return value of a generator function *is the
generator*. And you're free to ignore that, sure.
But this is a "second" return value that only goes to a special place
with special syntax -- without that syntax, you
ts.
We've been using hg to push changesets between each other, but we'll
be committing to the svn sandbox before the week is out. I'm heading
out today, but Paul is sticking around another day.
It's a start,
Ron
>
> --
> Regards,
> Benjamin
__
On Wed, Apr 1, 2009 at 12:50 PM, Ron DuPlain wrote:
> On Mon, Mar 30, 2009 at 9:29 PM, Benjamin Peterson
> wrote:
>> 2009/3/30 Collin Winter :
>>> If anyone is interested in working on this during the PyCon sprints or
>>> otherwise, here are some easy, concre
On Fri, Apr 10, 2009 at 4:38 PM, C. Titus Brown wrote:
> Unquestionably "core" by my criteria above:
>
> 3to2 tool -- 'nuff said.
I worked on the 3to2 tool during the sprint last week at PyCon. I can
chip in for GSoC in the event it does get picked up.
-Ron
PS - I
ary.
Running pydoc with the -g option opens a tkinter search window, that
searches the summery lines. Selecting from that list then opens the
browser to that item.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/m
Guido van Rossum wrote:
Please mail me topics you'd like to hear me talk about in my keynote
at PyCon this year.
How about something on the differences and obstacles of using Python for
developing full distributable applications vs small local scripts.
I'd like to see Python 3+ be more suit
veloper
needs to be aware of such as missing/changed modules and other environment
differences if they intend to give these files to others.
I think what Ron meant was "a way for normal users to install
a python application". That capability doesn't exist in standard
python in a w
ic details for that reason. My apologies for
any confusion.
Regards,
Ron
Ron Adam wrote:
Can I make my efforts in developing a (module, package, script, or
application) a lot easier if I keep certain things in mind? Are there
any best practices I should keep in mind if I intend to dis
arified, and documented better.
Regards,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
es together.
With a single cache directory, we could have an option to force writing
bytecode to a desired location. That might be useful on it's own for
creating runtime bytecode only installations for installers.
Ron
___
Python-Dev
Barry Warsaw wrote:
On Jan 31, 2010, at 01:06 PM, Ron Adam wrote:
With a single cache directory, we could have an option to force writing
bytecode to a desired location. That might be useful on it's own for
creating runtime bytecode only installations for installers.
One important r
ib" directory may be good.
For python programs located and installed elsewhere I think Michaels view
point is applicable. For some files that are not meant to be shared, some
form of discouragement can be a feature.
Ron Adam
___
Pyt
mport (since the stat call
savings don't apply in the latter case).
What if ... a bytecode-only mode is triggered by "__main__" loading from a
bytecode file, otherwise the .py files are needed and are checked to make
sure the bytecode files are current.
Ron
rings help separate the parser from the rest of your program in
a much cleaner way. This can make your programs more modular and easier to
modify and maintain.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
cache__ behavior simply by manually creating a
__pycache__ directory and deleting any byte-code files in the
module/program directory.
I like this, it is easy to understand and can be used without messing with
flags or environment variables.
Ron
___
Barry Warsaw wrote:
On Mar 22, 2010, at 02:02 PM, Ron Adam wrote:
If I understand correctly, we would have the current mode as the default, and
can trigger __pycache__ behavior simply by manually creating a __pycache__
directory and deleting any byte-code files in the module/program
Guido van Rossum wrote:
On Mon, Mar 22, 2010 at 12:20 PM, Barry Warsaw wrote:
On Mar 22, 2010, at 02:02 PM, Ron Adam wrote:
If I understand correctly, we would have the current mode as the default, and
can trigger __pycache__ behavior simply by manually creating a __pycache__
directory and
you move or rename files.
The startup time may just be a tad longer, but probably not enough to be
much of a problem. If it is a problem you can just create the __pycache__
directory, but nothing bad will happen if you don't.
Ron
___
Pytho
Nick Coghlan wrote:
Ron Adam wrote:
I think I misunderstood this at first.
It looks like, while developing a python 3.2+ program, if you don't
create an empty __pycache__ directory, everything will still work, you
just won't get the .pyc files. That can be a good thing during
d
tly help("PACKAGES") == help("import")
It may be enough at this time to add a "PACKAGES" help entry that gives an
overview of packages and hints on installing them. Then "import" can be a
related help topic for "PACKAGES".
Ron
__
me also.
Note that the python interpreter uses -V and --version.
r...@gutsy:~$ python3.1 -V
Python 3.1.2
r...@gutsy:~$ python3.1 --version
Python 3.1.2
And -v is used as follows:
-v : verbose (trace import statements); also PYTHONVERBOSE=x
I agree. Even though it may seem redundant when writing it, it's both clear
and explicit when reading it even if you aren't very familiar with how
argparse works, or have just returned from a really long and fun vacation. ;-)
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
n.
http://bugs.python.org/issue2001
I think the only issues with this patch are what new functions and classes
should be part of the public api.
* BTW... The bug trackers main links to items with patches, and needing
review, does
ge of this sort help make things any easier?
(Note: idle isn't in the lib directory on Ubuntu.)
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailm
On 07/12/2010 01:21 PM, Ian Bicking wrote:
On Sun, Jul 11, 2010 at 3:38 PM, Ron Adam mailto:r...@ronadam.com>> wrote:
There might be another alternative.
Both idle and pydoc are applications (are there others?) that are in
the standard library. As such, they or parts o
if multiple scripts are
being run at the same time.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
n have files in it.
... or a string containing the initials.
It doesn't fall under the single constant rule if done this way.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubsc
On 07/20/2010 11:47 AM, Ron Adam wrote:
On 07/20/2010 10:43 AM, Fred Drake wrote:
On Tue, Jul 20, 2010 at 9:09 AM, Steven D'Aprano
wrote:
It refers to the guideline that you shouldn't have a single function
with two (or more) different behaviour and an argument that does
nothing
On 07/20/2010 12:00 PM, Fred Drake wrote:
On Tue, Jul 20, 2010 at 12:47 PM, Ron Adam wrote:
It doesn't fall under the single constant rule if done this way.
If the value for 'allow' were almost always given as a constant, this
would be an argument for three functions inste
l_text_server, but it may also be useful in non-local cases as well.
The newest patch is...
http://bugs.python.org/file18165/pydoc_server3.diff
Any feedback will be welcome.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.o
and these kind of
situations I'd like to hear about it.
Does this have to be in this particular patch? I don't see any problem
adding better error recovery later. This isn't something new, both the
"-p" and "-g" modes have this issue.
Ron
On 07/24/2010 05:37 AM, Nick Coghlan wrote:
On Sat, Jul 24, 2010 at 10:05 AM, Ron Adam wrote:
I am not sure I like the fact that the browser is started automatically.
Please bring this up on python-dev. This may be an opportunity to
rethink pydoc command line switches. For example, -p and
On 07/24/2010 04:29 PM, Alexander Belopolsky wrote:
On Sat, Jul 24, 2010 at 3:34 PM, Ron Adam wrote:
On 07/24/2010 05:37 AM, Nick Coghlan wrote:
..
- leave the "-g" option alone (including the tk gui), but make sure
other options still work when tk is unavailable
I was hopin
On 07/24/2010 10:38 PM, Nick Coghlan wrote:
On Sun, Jul 25, 2010 at 5:34 AM, Ron Adam wrote:
On 07/24/2010 05:37 AM, Nick Coghlan wrote:
On Sat, Jul 24, 2010 at 10:05 AM, Ron Adamwrote:
I am not sure I like the fact that the browser is started automatically.
Please bring this up on
On 07/25/2010 12:01 PM, Alexander Belopolsky wrote:
On Sun, Jul 25, 2010 at 12:32 PM, Ron Adam wrote: ..
I'd be completely fine with dropping the "Search For" box from the
GUI interface, but the persistent window listing the served port
and providing "Open Browser" a
ven. Sort of like a log. It may be useful to find
problems with what the server is sending and what the browser is requesting.
Should the server have a timeout in case the command window is not
reachable? If so, how long?
cheers,
Ron
___
ing and leaving need to
change a bit, but that isn't hard to do.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pytho
cover the short term cases of no response, but also the
longer term items that slip though the cracks.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman
On 08/02/2010 03:57 AM, Stephen J. Turnbull wrote:
Ron Adam writes:
> Something that may be more useful, is a "no activity" search field
> with choices of day, week, month, year, etc... and make the output
> sortable on time without activity.
That's exactl
yield f(n)
if __name__ == "__main__":
print(factoral(1)) # < extra zero too!
But if I add another zero, it begins to slow to a crawl as it uses swap
space. ;-)
How would a "yield from" version compare?
I'm basically learning this stuff by trying
o
import .dom
shouldn't give you dom, but . (which is nonsensical, of course).
I don't think it would be "import .dom", but...
from . import dom
It would be another module in xml doing the importing, so xml will have
already been imported.
Ron
___
ules can use relative imports as long as they
aren't circular.
* The error message in the case of circular imports could be much better!
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
s needed or item is ok.
Most changes to any of these should also be documented in the discussion
area as well.
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
; or "license" for more information.
>>> help('modules ""')
Here is a list of matching modules. Enter any module name to get more help.
Segmentation fault
Or more directly...
>>> import imp
>>> imp.find_module('test/badsyntax_pep
where the file is,
or set environment variables, or create .bat and/or .sh files, and those
takes a lot more work. So why not just embrace it and move on?
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailma
the distribution.
When it's in the stdlib, the -m option should work just like any other
script run from the stdlib.
What path hacking are you thinking of?
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
the bug tracker, I just need to make some minor
updates to it and it can go in, but I really need some code
organizing/placement review help.
I I'm wonder what you may think. Keep it in pydoc or move it to the HTTP
package? Document it or not?
Ron
On 10/26/2010 05:35 PM, Raymond Hettinger wrote:
On Oct 26, 2010, at 2:54 PM, Ron Adam wrote:
I've worked on pydoc to make it much nicer to use in a browser.
While you're at it. Can you please modernize the html
and create a style sheet? Right now, all of formatting
On 10/26/2010 05:35 PM, Raymond Hettinger wrote:
On Oct 26, 2010, at 2:54 PM, Ron Adam wrote:
I wonder what you may think. Keep it in pydoc or move it to the
HTTP package? Document it or not?
I still would like to know what your thoughts are concerning where to put,
and/or how to
On 10/27/2010 08:51 AM, Nick Coghlan wrote:
On Wed, Oct 27, 2010 at 2:33 PM, Ron Adam wrote:
I still would like to know what your thoughts are concerning where to put,
and/or how to package, the simple threaded text server?
Given the time frame until beta 1, I'd suggest leaving it in
keywords or sub categories of open.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
, not languishing.
--Ron
1 not selected
2491 total "not closed"
19604 closed
2491 not closed
39 pending
-
22134 Total issues
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Uns
hing else. Any thoughts?
I think the main issues Nick is concerned with is the functions and options
used to start pydoc in the interactive mode.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
g if the exception is caught with a try except?
if __name__ == "__main__":
main()
else:
raise ImportWarning("This is utility module and may be changed.")
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://ma
are well aware of the risks if
they do it. (This is just one option and probably one that isn't thought
out very well.)
Brett, I'm sure you can up with a better alternative. ;-)
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
le along with a
pydoc3.py loader module with a basic user api. The number 3, so that it
match's python3.x.
We can then keep the old pydoc.py unchanged and be free to make a lot more
changes to the _pydoc3.py file without having to be even a little parano
On 11/08/2010 07:18 PM, Brett Cannon wrote:
On Mon, Nov 8, 2010 at 16:10, Ron Adam wrote:
def _private_api():
#
# Isn't it a good practice to use comments here?
#
...
That is ugly. I already hate doing that for unittest, I'm not about to
champion that for any
On 11/08/2010 10:26 PM, Nick Coghlan wrote:
On Tue, Nov 9, 2010 at 11:18 AM, Ron Adam wrote:
What do you think about adding a new _pydoc3.py module along with a
pydoc3.py loader module with a basic user api. The number 3, so that it
match's python3.x.
We can then keep the old pyd
at Micheal is trying to say is for us to agree on some things so
we can go forward with a little more clarity.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mai
easier interface with them. There also may be
some performance advantages as well since you can test for multiple flags
with a single comparison.
Sets of strings can also work when you don't need to associate a numeric
value to the constant. ie... the constant is the value. In this case the
set supplies the api.
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Oops.. x**2 should have been 2**x below.
On 11/23/2010 03:03 PM, Ron Adam wrote:
On 11/23/2010 12:07 PM, Antoine Pitrou wrote:
Le mardi 23 novembre 2010 à 12:50 -0500, Isaac Morland a écrit :
Each enumeration is a type (well, OK, not in every language, presumably,
but certainly in many
so you get a different error than if you used import, which uses the parser
module and that does set the filename.
From what I've seen, it would help if the imp module was rewritten to use
parser.c like the import statement does, rather than tokenizer.c directly.
The error handling in parse
BAR: "Hello World!",
BAZ: dict(a=1, b=2, c=3) ):
... return FOO, BAR, BAZ
...
>>> foo(1,2,3)
(1, 2, 3)
>>> foo.__annotations__
{'BAR': 'Hello World!', 'FOO': 1, 'BAZ': {'a': 1, 'c': 3, 'b': 2}}
Cheers,
Ron
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
On 11/29/2010 01:22 PM, Brett Cannon wrote:
On Mon, Nov 29, 2010 at 03:53, Sylvain Thénault
wrote:
On 25 novembre 11:22, Ron Adam wrote:
On 11/25/2010 08:30 AM, Emile Anclin wrote:
hello,
working on Pylint, we have a lot of voluntary corrupted files to test
Pylint behavior; for instance
On 11/28/2010 09:03 PM, Ron Adam wrote:
It does associate additional info to names and creates a nice dictionary to
reference.
>>> def name_values( FOO: 1,
BAR: "Hello World!",
BAZ: dict(a=1, b=2, c=3) ):
... return FOO, BAR, BAZ
...
>>> foo(1,2,3)
(1, 2, 3)
&
On 11/30/2010 01:41 PM, Brett Cannon wrote:
On Mon, Nov 29, 2010 at 12:21, Ron Adam wrote:
On 11/29/2010 01:22 PM, Brett Cannon wrote:
On Mon, Nov 29, 2010 at 03:53, Sylvain Thénault
wrote:
On 25 novembre 11:22, Ron Adam wrote:
On 11/25/2010 08:30 AM, Emile Anclin wrote:
hello
1 - 100 of 285 matches
Mail list logo