| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
happen when you use a non-keyword argument after a keyword argument,
and in this case you also get a syntax error. I fully suspect that
the underflow is caused by the code that stops generating code when it
detects the syntax error, but I can't find the culprit right now. I
know, I know.)
|
| |
|
| |
|
|
|
|
| |
use it in tokenizer.c.
|
|
|
|
| |
Metrowerks specific #ifdef.
|
|
|
|
|
|
| |
The MS compiler doesn't call it 'long long', it uses __int64,
so a new #define, LONG_LONG, has been added and all occurrences
of 'long long' are replaced with it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2-digit years are now converted using rules that are (according to
Fredrik Lundh) recommended by POSIX or X/Open: 0-68 mean 2000-2068,
69-99 mean 1969-1999.
2-digit years are now only accepted if time.accept2dyear is set to a
nonzero integer; if it is zero or not an integer or absent, only year
values >= 1900 are accepted. Year values 100-1899 and negative year
values are never accepted.
The initial value of time.accept2dyear depends on the environment
variable PYTHONY2K: if PYTHONY2K is set and non-empty,
time.accept2dyear is initialized to 0; if PYTHONY2K is empty or not
set, time.accept2dyear is initialized to 0.
|
|
|
|
| |
and x is not an instance of C (nor of a class derived of C).
|
|
|
|
| |
mktime() and such.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sjoerd writes:
This version of freeze creates one file per Python module, instead of
one humongous file for all Python modules.
bkfile: new module to used to write files with backups. No new file
is produced if the new contents is identical to the old.
New option "-x excluded-module" for modulefinder test program.
New option "-i filename" for freeze main program to include a list of
options in place of the -i option.
|
|
|
|
|
|
| |
by the new '-x' arguments, losing the previous items. Thus,
test_support, test_b1 & test_b2 are executed (and warnings issued).
(Discovered by Vladimir Marangozov.)
|
|
|
|
| |
with tags that have - or . in their names.
|
|
|
|
|
|
| |
described that way.
setattr(): Clarify that the attribute doesn't need to exist to be set.
|
| |
|
|
|
|
| |
object whose method this is --> object on which the method operates
|
|
|
|
|
|
| |
This is a patch that Bill Bummgarner did for 1.4 that hasn't made its
way into the distribution yet. This is important if you want to use
the ObjC module.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
method, so .groups() didn't work inside the replacement function
called by re.sub. One-line fix: set self._num_regs inside subn().
|
| |
|
|
|
|
|
|
|
|
| |
shell buffers.
(py-shell): Moved the require of comint to the top level. Also
use-local-map py-shell-map instead of hacking on the comint-mode-map.
This eliminates breakage of other comint-mode buffers (e.g. shell).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interactions with newer Emacsen, I've rewritten the way all the
process filters work in the *Python* buffer. We use more of the
comint infrastructure, specifically the default process filter. This
means that scrolling is now handled by the default comint variables
including comint-scroll-to-bottom-on-output. Note that this is
somewhat experimental change!
(py-comint-output-filter-function): Moved to here from the obsolete
py-process-filter function, the logic to pop and exec the next queued
file waiting to be executed.
(py-execute-file): Don't bind comint-scroll-to-bottom-on-output to t,
and save the excursion when inserting the "working on" message. This
lets the standard comint scrolling variables as set by the user,
continue to work.
(python-mode, py-shell, py-describe-mode): Remove description of
py-scroll-process-buffer. Also in py-shell, make
comint-output-filter-functions buffer-local, and add
py-comint-output-filter-function to this hook (instead of setting the
process filter).
(py-scroll-process-buffer): Deleted this variable. See comint
variables including comint-scroll-to-bottom-on-output.
(py-execute-region): When exec files are being queued, push the next
temp file on the end of the list.
(py-submit-bug-report): Removed reporting of py-scroll-process-buffer.
|
|
|
|
|
| |
As everything is also under CVS this should greatly simplify the work to be done
when a new version of one of the libraries we use is released.
|
| |
|
| |
|
|
|
|
| |
does make the name a bit of a non-sequitur:-)
|
| |
|
| |
|
|
|
|
| |
them under cvs too.
|
|
|
|
|
|
|
|
|
| |
takes too long. This example relies on the fact that raising an
exception in a signal handler causes the exception to be re-raised
when the main line of the program resumes execution. Is this guaranteed
in CPython, or is this something that just happens to work by accident?
Also fixed a typo.
|
|
|
|
|
| |
objects; this makes the emulation of file objects a bit better, and the
exceptions explain things a bit better.
|
| |
|
| |
|
|
|
|
| |
(in AppleSingle format, so should be readable with MacCVS Pro too)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the continuous name conflicts which cause the wrong config.c to be found.
|
| |
|
|
|
|
| |
(Just).
|
|
|
|
|
|
| |
a method definition has args that span multiple lines; be sure to go
to the beginning of the method definition -- but watch out for the
match-data!
|
| |
|
|
|
|
| |
<oli@rhein-zeitung.de>.
|
|
|
|
| |
Lorenzo M. Catucci <lorenzo@argon.roma2.infn.it>.
|
|
|
|
| |
quote, not single quotes. Ugh.
|
|
|
|
| |
Simplify the patterns in the examples for re.split
|